Command Line Interface

bugwarrior pull

Pull down tasks from forges and add them to your taskwarrior tasks.

Relies on configuration in bugwarriorrc

bugwarrior pull [OPTIONS]


--flavor <flavor>

The flavor to use


Do not use multiprocessing (which breaks pdb).


Set logging level to WARNING.

bugwarrior uda

List bugwarrior-managed uda’s.

Most services define a set of UDAs in which bugwarrior store extra information about the incoming ticket. Usually, this includes things like the title of the ticket and its URL, but some services provide an extensive amount of metadata. See each service’s documentation for more information.

For using this data in reports, it is recommended that you add these UDA definitions to your taskrc file. You can add the output of this command verbatim to your taskrc file if you would like Taskwarrior to know the human-readable name and data type for the defined UDAs.


Not adding those lines to your taskrc file will have no negative effects aside from Taskwarrior not knowing the human-readable name for the field, but depending on what version of Taskwarrior you are using, it may prevent you from changing the values of those fields or using them in filter expressions.

bugwarrior uda [OPTIONS]


--flavor <flavor>

The flavor to use

bugwarrior vault

Password/keyring management for bugwarrior.

If you use the keyring password oracle in your bugwarrior config, this tool can be used to manage your keyring.

bugwarrior vault [OPTIONS] COMMAND [ARGS]...


bugwarrior vault clear [OPTIONS] TARGET USERNAME



Required argument


Required argument


bugwarrior vault list [OPTIONS]


bugwarrior vault set [OPTIONS] TARGET USERNAME



Required argument


Required argument

Configuration files

Bugwarrior will look at the following paths and read its configuration from the first existing file in this order:

  • ~/.config/bugwarrior/bugwarriorrc

  • ~/.bugwarriorrc

  • /etc/xdg/bugwarrior/bugwarriorrc

The default paths can be altered using the environment variables below.

Environment Variables


This overrides the default RC file.


By default, bugwarrior looks for a configuration file named $XDG_CONFIG_HOME/bugwarrior/bugwarriorrc. If $XDG_CONFIG_HOME is either not set or empty, a default equal to $HOME/.config is used.


If it can’t find a user-specific configuration file (either $XDG_CONFIG_HOME/bugwarrior/bugwarriorrc or $HOME/.bugwarriorrc), bugwarrior looks through the directories in $XDG_CONFIG_DIRS for a configuration file named bugwarrior/bugwarriorrc. The directories in $XDG_CONFIG_DIRS should be separated with a colon ‘:’. If $XDG_CONFIG_DIRS is either not set or empty, a value equal to /etc/xdg is used.

See Also