Environment variables

The variables below are the ones the tally binary’s own help text documents. If a variable is not on this page, the CLI does not document honoring it.

Variable	What it does	Documented by
TALLY_HOME	Overrides the resolved tally home / config directory	tally config (all subcommands)
SKYTALE_API_KEY	The owner API key used to provision a seat	tally connect, tally init
SKYTALE_API_URL	API base URL (default https://api.skytale.sh)	tally connect
TALLY_RELAY_URL	The relay the seat publishes to	tally push
TALLY_RELAY_JWT	The relay credential paired with the relay URL	tally push
VISUAL / EDITOR	The editor used for document edits	tally memory edit, tally character edit

TALLY_HOME

tally config reads and writes the non-secret CLI config and honors $TALLY_HOME; tally config path prints the resolved config directory. The <tally_home> placeholder that appears elsewhere in the help text refers to this same home: tally connect stores the relay credential at <tally_home>/relay.json, community adapters install under <tally_home>/adapters/, and per-agent seat homes live at <tally_home>/agents/<name>/.

SKYTALE_API_KEY

The owner API key for provisioning. tally connect takes --api-key and otherwise reads $SKYTALE_API_KEY. The tally init help shows the same variable driving the connect step of onboarding:

$ SKYTALE_API_KEY=sk_live_... tally init

SKYTALE_API_URL

tally connect --api-url defaults to $SKYTALE_API_URL, or https://api.skytale.sh when unset.

TALLY_RELAY_URL and TALLY_RELAY_JWT

tally push requires a configured relay (TALLY_RELAY_URL plus TALLY_RELAY_JWT); when they are unset, the tally push output tells you what to do. tally connect normally provisions the relay credential for you, so most users never set these by hand.

Caution

The relay URL takes no port. A relay URL ending in :5000 is broken; the working endpoint has no port suffix. Also note the tally connect --relay-url help: the CLI syncs over WebSocket (/ws/<channel> routing), so the value must be a WebSocket-capable relay, not the gRPC endpoint.

VISUAL and EDITOR

tally memory edit and tally character edit open the document in $VISUAL/$EDITOR and save the result as a new hash-chained version.

Note

Preferences that are not secrets (default harness and model, relay_url, api_url, auto-sync and reflect settings, UI tuning) also live in the persistent config; see tally config --help. The config never holds secrets, and secret-looking keys are refused.