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>"

Secret values are never printed: config get and config list show claudeApiKey only as set when it has a value. Inside the interactive CLI, /config shows the same settings.

Terminal~/checkout

$ testrelic config path

/home/sam/.testrelic/cli-config.json

$ testrelic config set baseUrl https://platform.testrelic.ai/api/v1

baseUrl = https://platform.testrelic.ai/api/v1

$ testrelic config get theme

dark

$ testrelic config get statusLine

(unset)

$ testrelic config set theme neon

expected auto, dark, light, or ascii

$ testrelic config set statusLine ~/.testrelic/statusline.sh

statusLine = ~/.testrelic/statusline.sh

File locations

Path	Purpose
`~/.testrelic/cli-config.json`	CLI settings written by `testrelic config set` (`testrelic config path` prints it).
`~/.testrelic/token`	The CLI's token, saved by `testrelic login` or `testrelic login --token`.
`~/.testrelic/cookies.json`	Persisted session cookies.
`~/.testrelic/studio-token`	TestRelic Studio's own sign-in, kept separate from the CLI's. See Authentication.
`~/.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

Web control (Ask AI Remote sessions)

From CLI 1.2.1, an interactive CLI session shows up under Remote in Ask AI on the web when it runs on the TestRelic Cloud agent and the CLI is signed in with testrelic login. With web control on, which is the default, the web app can send messages to the session, answer its approval prompts and stop a turn. With it off, the web app can still watch the session but can't drive it.

Setting	Effect
`testrelic config set remoteControl false`	Web control off for every session (`true` turns it back on).
`TESTRELIC_REMOTE_CONTROL`	Overrides the config for sessions started from this environment. Takes `on`/`off`, `true`/`false`, `1`/`0` or `yes`/`no`.
`testrelic --no-remote-control`	Off for this session, whatever the config or environment says.
`/remote on` · `/remote off`	Switches it mid-session. `/remote` (or `/remote status`) shows the setting, what turned it off, and whether the web app can see this session.