TestRelic Studio
The native desktop GUI companion to the CLI — the same Ask AI agent and local test data, in a graphical workspace instead of a terminal.
TestRelic Studio is a native desktop app that pairs with the CLI —
the same Ask AI agent and local test data, in a graphical workspace instead of a terminal.
It's built on the CLI itself: its chat pane runs tr as a persistent local session, so it
honors the same Modes & engines and reuses your CLI login.
Studio needs a Pro plan or above
Studio is the one product the CLI's own plan doesn't cover: it needs a cloud subscription on Pro or above, in either the active or an unexpired trial state. An active 14-day trial unlocks Studio whatever tier it sits on — but when the trial ends, Growth keeps the CLI and loses Studio. See Plans & Billing.
Fix the flaky login test
✻ TestRelic
Found the flaky step — a race on the toast dismiss. Applying a fix and re-running…
⏺ 3 tools · ctrl+o
A hand-recreated slice of the real app — click through the workspace tabs (Live Browser, Tests, Runs, Pipelines, Traces) shown here alongside chat. See Workspace for the full tour, including the session sidebar and the Routines & Dispatch multi-session workbench this compact view leaves out.
Launch it
testrelic studio # open Studio on the current directory
testrelic studio --path ./repo # open Studio on a specific repoOr from the CLI's interactive UI:
❯ /studioIf nothing is installed yet, the first launch fetches and installs Studio for you — see Installation. The install is automatic; the entitlement is not, so sort the plan out first.
$ testrelic studio
# open Studio on the current directory
❯ /studio
Opening TestRelic Studio (installed app) on this repo…
Opens automatically after a local /init
Running testrelic init (or /init) in Local mode sets up
your project, runs the suite once, and then opens Studio on the repo automatically — no extra
step needed.
Zero-friction start
No repo yet? Once Studio is entitled, it doesn't make you pick or create one first — it stands up a ready-to-use workspace pointed at a public demo app so you land straight in chat. The demo workspace is a shortcut past repo setup, not past the Pro requirement above.
Where to go next
Installation
Get Studio installed and see the --path / --stop command reference.
Planner
Plan what a release promises, build tests from it, run them, prove it, and share the result.
Live Browser
Watch an AI agent drive a real, visible browser — the same one its Playwright MCP controls.
Live Device
One-click Android onboarding — no JDK, no Android Studio — then watch a live, screen-mirrored emulator.
Evals
DeepEval metrics, category health, and pass-rate trends, read straight off your repo's run JSON.
Augur
Embedded evidence reports, one-click demo runs, and in-pane reference approval for text-to-image evals.
Workspace
Explorer, Command Center, a multi-session workbench (Routines & Dispatch), Test Paths, run visualization, issue detection, and fix & re-run.
Pipelines
Connect CI, view runs and logs, trigger or cancel a run, and publish a starter workflow.
Relationship to the CLI
Studio is a GUI shell around the same tr CLI: chat runs tr -p --input-format stream-json --output-format stream-json as a persistent session, so it shares your login and the same
Modes & engines as the terminal. Fix flows can also drive your
locally installed claude CLI directly, scoped to the repo.
Next steps
TestRelic CLI configuration
Configure the CLI's backend URL, theme, statusline, and keybindings, and learn where session cookies, tokens, and MCP config files live on disk.
Installing & launching Studio
Get TestRelic Studio installed on Windows, Linux, or macOS, keep it in lockstep with the CLI, and the full testrelic studio command reference.