Changelog

Ask AI's Remote tab no longer only follows Studio and CLI conversations: you can now take part in them from the web. The device still runs every turn itself, with its own tools and permission rules.

• Reply or queue a message. A message sent while a turn is running waits in a queue, and you can send a held one with Send now or remove it.
• Answer approvals. An approval the session is waiting on can be answered from the web with Allow once, Deny, or Deny and say what instead. "Don't ask again" and Full autopilot stay on the device.
• Stop a turn. Stop interrupts the device's current turn; the session stays open.
• Start a chat on your own computer. New remote session lists the Studio apps you're signed in to under Your devices. Pick a recent folder, say what the agent should do, and the chat opens and runs in Studio there.
• Control stays with you in Studio. Each chat has a Web control on / Web control off switch in its header, and messages from the web carry a From the web label. Under TestRelic web app in Settings → Chat, Web control in new chats sets the default and Start chats from the web decides whether the web may open chats here. Both are on by default.
• In the CLI, turn web control off with --no-remote-control, the remoteControl config key or TESTRELIC_REMOTE_CONTROL, or mid-session with /remote off. The web can still watch.

Replying from the web needs Studio or the CLI 1.2.1 or later. Older versions can still be watched, and the session asks you to update.

Released as testrelic-cli 1.2.1.

On a computer with both Studio and the CLI, signing in to one used to revoke the other's token, so its next request failed with "Authentication required". Each now keeps its own.

• Separate tokens per app. Studio's sign-in token is now named TestRelic Studio (<computer name>) in Settings → MCP Tokens, and the CLI's stays TestRelic CLI (<computer name>). Signing in again replaces only the same app's earlier token on that computer.
• Mind the 10-token limit. A computer that uses both apps holds two tokens, and each user can hold 10. If you're at the limit, delete an unused token in Settings → MCP Tokens before signing in.
• A clearer MCP error. A revoked or expired token on the MCP endpoints now answers "Bearer token is invalid, expired, or revoked. Mint a new MCP PAT at /settings/mcp-tokens."
• Ask AI usage counts each model call once. A reply that both reasoned and called a tool was counted two or three times against your token meters.

Until a computer's next Studio sign-in, its existing Studio token can still be listed as TestRelic CLI (<computer name>).

Ask AI conversations running in Studio or the CLI now show up in Ask AI on the web, where you can follow them as they happen.

• A Chats / Remote switcher heads the Ask AI sidebar. Chats holds your web conversations, as before. Remote lists conversations from Studio and the CLI: live ones under Live now, ended ones under Archived. Search works inside whichever list you're on.
• Watch a turn as it streams, including the artifacts it produces along the way, rather than after it finishes.
• Each session shows where it came from, Studio or the CLI, and what state it's in.

Nothing to set up: conversations from Studio and the CLI appear on their own.

Also in this release, signed-in browser sessions are protected against cross-site request forgery. API keys, the CLI, the SDKs and webhooks work exactly as before.

Ask AI has a model picker in the composer, and a second provider alongside Anthropic.

• Five choices: Auto, DeepSeek V4 Pro, DeepSeek Flash, Sonnet 4.6 and Sonnet 5. Your choice is saved.
• Auto starts on DeepSeek Flash and uses Sonnet 4.6 when a turn needs it: turns with images or web search go to Sonnet, and if DeepSeek fails before an answer starts, including when it can't be reached, the turn switches to Sonnet once.
• Every answer names the model that wrote it, and says when Auto switched.
• Admins can set one engine for everyone. In Organization settings, Ask AI engine is either Members choose or one engine for the whole organization. Pinning an engine turns off the automatic switch, so if that engine is down, turns fail rather than moving to another one. Turns with images or web search still go to Sonnet, because DeepSeek can't read images or search the web.
• Where each runs: DeepSeek models run on DeepSeek's servers and cost substantially less; Sonnet runs on Anthropic's. An organization that wants every turn on Anthropic can pin a Sonnet engine.

See Ask AI.

Test cases your team writes by hand now have a home next to the results your automated runs report. A repository's Test Cases tab has three views: Results, Library and Coverage.

• Library lists your written cases. Search by key, title or the text of a step, open a case to see its steps, and create or edit cases in place.
• Import from TestRail, Xray, Zephyr or a plain CSV. TestRail and CSV imports take a CSV export with title, steps and expected-result columns; Xray and Zephyr take a JSON export. Before anything is written, the import shows what will happen to each case: new, an update, a new version of a case you already have, or a suspected duplicate, which you can choose to import as a separate case.
• Coverage lines written cases up against the automated tests that ran: which are automated, which are manual only, and which tests ran without a written case, with when each was last executed.

API change: POST /repos/:repoId/test-cases with a title that's already taken now returns 409 CASE_NAME_COLLISION when the steps differ, and 200 with the existing case when they're identical. It used to create a new case (201) every time, so a script that saves cases by title should handle the 409.

Rows, cards and list entries across the platform are now real links, so the browser's own navigation works on them.

• Open in a new tab. Right-click a repository, run, test case, session, evaluation or alert and the browser offers Open link in new tab. Ctrl/Cmd+click and middle click do the same, so you can fan several runs out across tabs instead of navigating back and forth.
• Copy a link to anything you can see. Right-click gives Copy link address, and the link carries the full deep link, including the run, test and filter it was showing.
• The rest is unchanged. A plain click still opens the item in place, and buttons and menus inside a row still do their own job.
• Opening a chat in a new tab leaves this one alone. Ctrl/Cmd+clicking to start a new Ask AI chat in another tab used to reset the conversation in the tab you were in.

This covers Repositories, Test Runs and run detail, test cases and sessions, Evaluations and Augur, alerts, monitoring lists, search results, the Ask AI sidebar and artifacts, the API request tree, and the integration consoles.

Renaming a test or moving it to another file used to leave its old entry behind as a test that never ran again, and a test rewritten under the same name looked like the same test with the same history. TestRelic now tracks which test is which, separately from its name and its steps.

• A rename or a move is recognised. When a test's title changes but its steps don't, or it moves to another file with the same title and steps, TestRelic treats it as the same test. The old name is tucked behind an "N superseded names hidden" note in the Test Cases list, with a Show button, instead of sitting there as a test that stopped running.
• A rewrite is a new version. When a test's steps change under the same name, TestRelic records a new version. A rename is recorded as a version too, so it shows up on the test's very next run.
• Version history for every test. Open it from the test's row in the Test Cases list: each version, newest first, with what changed (the steps, the title or the suite) and the run it first appeared in, then every name the test has had.
• Tests that share a name are called out. A banner above the Test Cases list counts the names held by more than one test, and says when one row is blending several tests, so its pass rate and flakiness aren't any single test's history. Review duplicate names opens the groups, where you can merge two entries that are really one test or keep both. A merge can be split again, and TestRelic never merges tests on its own.
• Search for them. The Test Cases search understands duplicate:true, and version: with a number: version:3, version:>=2 for tests that have changed, or version:none for tests not versioned yet.

Versions and rename tracking come from the steps a test reports, so they apply to frameworks that report steps, such as Playwright. Nothing to set up. See Repositories for the Test Cases tab.

If your CLI or Studio is running a version too old to update itself, TestRelic now says so the next time you use Ask AI — on the one channel a stuck install can still reach — with the single command that fixes it.

• The notice reaches both the terminal CLI and Studio's agent chat, since Studio drives the same CLI underneath.
• It's shown once, not on every turn, and it names the exact reinstall command for your platform.
• It moves with each release on its own. A client merely a version behind — one whose updater still works — gets a quieter "a new version is available" note instead of the reinstall prompt.

No action needed if you're current; you'll never see it. Shipped on the Cloud Platform.