Ask AI in your terminal.
curl -fsSL https://testrelic.ai/install.sh | shEvery test run becomes shared context for Cursor, Claude Code, Copilot, and Codex — over MCP. So your whole team ships at senior-IC speed, not just the engineer who's been here longest.
✻TestRelic CLI v0.49.2 (BETA)
agentic testing, in your terminal
backend platform.testrelic.ai (session)
account sarah@acme.com · Growth
repo shop-e2e · 214 specs · 30 runs indexed
tips: /help for commands · @ add context · esc interrupts · ctrl+c twice exits
> Ask about your tests, runs, flakes… (@ context · /commands)

Install in under a minute
One line and you're talking to your tests
Linux / macOS
Installs the testrelic binary — plus the tr and ask-ai shortcuts — to ~/.testrelic/bin and adds it to your PATH.
curl -fsSL https://testrelic.ai/install.sh | sh$ curl -fsSL https://testrelic.ai/install.sh | sh
resolving latest release…
✓ testrelic → ~/.testrelic/bin
aliases · tr · ask-ai
PATH · updated
$ testrelic login
Windows
The same install via PowerShell. Built for Windows Terminal; legacy conhost falls back to an ASCII glyph set.
irm https://testrelic.ai/install.ps1 | iex$ irm https://testrelic.ai/install.ps1 | iex
resolving latest release…
✓ testrelic installed
Windows Terminal · full glyph set
legacy conhost · ASCII fallback
$ testrelic login
Then sign in and ask
Run testrelic login and start asking. The CLI defaults to production — point it elsewhere with testrelic config set baseUrl.
Install guide$ testrelic login
✓ signed in · session persists
$ testrelic
▌why is checkout flaky?
✻ TestRelic
reading run #4821…
point elsewhere · config set baseUrl
Everything the web Ask AI does — in your shell
A real agent, not a chat box.
Built for the terminal from the ground up — streaming, tools, confirmations, and artifacts, with the keybindings you already know.
Artifacts render in your terminal
New Relic-grade dashboards with KPI billboards, sparklines and braille charts, plus reports, test plans, navigation paths, and heat-colored tables — drawn directly into scrollback, streaming as they generate.
❯ show nightly health
◫ dashboard · nightly health
94.2% pass · 6 flaky · 4.2h mttr
pass rate ▁▂▃▅▆▇▆▅▄▃▅▆▇ 30d
p75 dur ⣀⣄⣤⣦⣶⣷⣿⣷⣶⣤⣀ 3.2s
top offender checkout.spec.ts
owner @sarah
✓ artifact saved · /artifacts to browse
A full MCP host
Add local MCP servers (stdio or HTTP, Claude-Code-compatible .mcp.json). Their tools are advertised to the cloud agent per request and executed locally when it calls them.
$ testrelic mcp add fs -- npx …everything
✓ fs connected · 4 tools advertised
$ testrelic mcp list
reading ./.mcp.json
fs stdio ✓ 4 tools
playwright stdio ✓ 21 tools
grafana http ✓ 6 tools
✓ 31 local tools advertised per request
@-context and ! shell mode
Type @ to attach repos, runs, branches, test cases, environments, suites, or tags as context chips. Type ! to run a local command — its output attaches to your next message.
❯ @checkout-repo @run:4891 summarize
⧉ repo shop-e2e ⧉ run #4891
! git log --oneline -5
a1c9f2e fix(checkout): rename pay-now
7d40b81 chore: bump playwright to 1.49
4be0c13 test(cart): drop waitForTimeout
…2 more
⧉ shell output attached (5 lines)
Slash commands
/resume past conversations, /artifacts to browse and view any artifact, /export to markdown, plus /doctor, /repos, /memory, /usage, /tools, /mcp, /theme, and more.
❯ /
/artifacts browse and view artifacts
/export save this session to md
/resume reopen a past conversation
/doctor check auth, config, MCP
/repos switch the active repo
/memory /usage /tools /mcp /theme
↑↓ to move · enter to run
Claude Code-parity input
Ctrl+R reverse history search that persists across sessions, message queueing while a turn streams, kill-ring editing, draft stashing, and an optional vim mode with motions and dot-repeat.
bck-i-search: night▮
↳ why did the nightly regress?
↳ compare nightly to the last green run
↳ /export nightly-triage.md
ctrl-r again · esc to cancel
queued · 2 messages send after this turn
history · 1,284 entries across sessions
-- NORMAL -- vim mode · dot-repeat on
Headless print mode
Pipe-friendly output for scripts and CI: -p with --output-format text, json, or stream-json. Artifacts render ANSI on a tty and plain when piped. --resume and --continue keep context.
$ tr -p "why did the nightly regress?" \
--output-format json
{
"answer": "checkout.spec.ts broke on a…
"artifacts": [{ "type": "dashboard" }],
"session_id": "01JQ8F3K", "turns": 1
}
$ tr -p "list failing specs" --continue
checkout.spec.ts cart.spec.ts login.test.js
Two modes · one binary
Drive it by hand or wire it into CI
The same testrelic binary — also available as tr and ask-ai.
Interactive
An inline terminal UI that scrolls into native scrollback — no alt-screen. Streamed markdown, live tool activity, inline approve/reject, @-context chips, ! shell mode, slash commands, themes and vim mode.
▌@checkout.spec.ts why does this fail?
✻ TestRelic
● tr_diagnose_run(#4821)
scrollback · native — no alt-screen
Print (headless)
Pipes welcome. One-shot answers for scripts and CI with --output-format text, json or stream-json, plus --resume and --continue. Artifacts render ANSI on a tty and plain when piped.
$ testrelic -p "flake rate?" --output-format json
{
"flake_rate": 0.133,
"spec": "checkout.spec.ts"
}
--resume <id> · --continue / -c
Two ways to sign in
testrelic login for the encrypted email/password challenge flow, with cookies that persist and auto-refresh. Or a personal access token — the same convention as @testrelic/mcp, ideal for headless and CI.
Auth docssession login
$ testrelic login
encrypted challenge flow · email + password
cookies · persist · auto-refresh
personal access token
$ testrelic login --token tr_mcp_••••
TESTRELIC_MCP_TOKEN · headless + CI
Built for the terminal
One fast binary. Runs anywhere.
One native binary
Written in Rust, with no Node, Python or other runtime to install. Prebuilt for Linux, macOS and Windows on both x86_64 and arm64.
Read the docsbuilt in · Rust
runtime required · none
no Node · no Python · no JVM
linux · x86_64 · arm64
macOS · x86_64 · arm64
windows · x86_64 · arm64
prebuilt targets · 6
The agent runs in the cloud
The CLI streams it to your terminal and hosts your local MCP tools, so local tools stay local. Cloud mode shares memory; Local mode uploads nothing and gates every mutation.
agent runs in the TestRelic cloud
CLI · streams it to your terminal
CLI · hosts your local MCP tools
so local tools stay local
Cloud mode · uploads · shared memory
Local mode · nothing uploaded
every mutation · approval-gated in Local
Shares config with @testrelic/mcp
The ~/.testrelic config and token are the same ones the MCP server uses — one login covers both surfaces.
Connect an agentconfig.json · shared
token · tr_mcp_••••
the same convention as @testrelic/mcp
so one login covers both
bin/testrelic · · tr · ask-ai
baseUrl · config set baseUrl …
Your tests, one prompt away
Bring Ask AI to your terminal.
Install in one line, run testrelic login, and start asking your test data anything — interactively or piped into CI.
testrelic · tr · ask-ai · docs.testrelic.ai/cli