Configure the CLI's backend URL, theme, statusline, and keybindings, and learn where session cookies, tokens, and MCP config files live on disk.

`config` command

testrelic config set baseUrl <your-backend-url>      # write a value
testrelic config get baseUrl                          # read a value
testrelic config list                                 # show all settings
testrelic config path                                 # print the config file location
testrelic config set statusLine "<your-statusline-command>"

File locations

Path	Purpose
`~/.testrelic/cookies.json`	Persisted session cookies (from `testrelic login`).
`~/.testrelic/token`	Personal access token, if you store it on disk.
`~/.testrelic/mcp.json`	Global MCP server config.
`./.mcp.json`	Project MCP server config (wins on name collisions).

The ~/.testrelic/ directory and its mcp.json + token are shared with @testrelic/mcp, so a token you already use for MCP works here too.

Backend URL

The CLI defaults to production. Override it three ways — see Authentication:

testrelic config set baseUrl https://your-host.example.com/api/v1   # persisted
testrelic --base-url https://your-host.example.com/api/v1           # per-invocation
export TESTRELIC_CLOUD_URL=https://your-host.example.com/api/v1     # environment