Skip to content

Global options

Terminal window
tari [GLOBAL_OPTIONS] <COMMAND> [COMMAND_OPTIONS]
OptionDescriptionDefault
-b, --base-dir <PATH>Base directory for CLI data~/.local/share/tari_cli
-c, --config-file-path <PATH>Config file location~/.config/tari_cli/tari.config.toml
-e, --config-overrides <KEY=VALUE>Config overrides, e.g. networks.esmeralda.wallet-daemon-url=… (global config)None
-n, --network <NETWORK>Active network: esmeralda, localnet, igor, nextnet, stagenet, mainnet. Overrides the project and global default-networkProject / global default
--api-key <API_KEY>Wallet daemon API key, sent as a bearer token. Also read from TARI_WALLET_DAEMON_API_KEY$TARI_WALLET_DAEMON_API_KEY
--skillPrint a Markdown guide teaching a coding agent how to use the CLI, then exit

tari --skill prints a Markdown guide — commands, the non-interactive flags an agent needs, the authentication model and common failure modes — in the skill format agents load from a SKILL.md. Write it wherever your agent looks for skills:

Terminal window
mkdir -p .claude/skills/tari && tari --skill > .claude/skills/tari/SKILL.md

It only writes to stdout: no config, directories or network access are touched.

Commands that talk to the wallet daemon — publish, template publish and metadata publish --signed — authenticate with an API key issued by the wallet daemon. The key is sent as an Authorization: Bearer token on every JSON-RPC request; there is no interactive login.

Provide it with the --api-key flag or the TARI_WALLET_DAEMON_API_KEY environment variable — the flag takes precedence:

Terminal window
export TARI_WALLET_DAEMON_API_KEY="<your-api-key>"
tari publish -a myaccount
# or per-invocation
tari publish -a myaccount --api-key "<your-api-key>"

For security, the API key is never read from or written to a config file.

The key must be minted with at least these permissions:

PermissionUsed for
templates:readReading template state
templates:createPublishing templates and signing metadata
accounts:readResolving the fee account and checking its balance
transactions:readWaiting on the publish transaction result to confirm it

If the wallet daemon has authentication disabled, the API key can be omitted.

Running tari with no command launches an interactive setup wizard that walks you through:

  1. Creating or detecting a template crate
  2. Setting up the project configuration (tari.config.toml)
  3. Initialising the template metadata