Changelog

In Ask AI → Remote, code folds into compact cards, and opening one shows the code and its changes in the Artifact pane. Web chats are unchanged.

• Long code folds into a card. A code block of more than three lines becomes a one-line card with its language or file name and line count, and Open shows it in the pane. Shorter blocks stay in the chat with line numbers, Wrap and Copy, plus, on a test file, Save & run, which writes that request into the composer.
• A card for every file the agent touched. Each file it saved or deleted on the device gets a card with its path, lines added and removed, and a create, update or delete badge. A git diff it ran gets a card too, without a badge.
• Code and Changes. The pane shows the code with syntax highlighting, and what changed as a diff with old and new line numbers. A save is compared with the last copy of that file the chat saw. When there isn't one, for example because the chat never read the file or the read stopped at Studio's 64 KB limit, the pane opens on the code and says why.
• Step through the chat's code with the previous and next arrows, and copy or download it. Ask about this code puts a question about it in the composer.
• Review a save before you approve it. When the device asks before saving a file, Review changes on the approval card opens the diff in the pane, where you can answer Yes, run it or No, skip this. To tell it what to do instead, answer on the card.

Studio and the CLI need no update. See Ask AI.

A round of platform fixes.

• Sign-in, sign-up and password-reset pages work better with screen readers. Each page declares its language and has a real page heading, and links inside text are underlined instead of marked by colour alone.
• Large runs upload. A run of about 2,850 tests or more, such as a large CTRF report, failed to upload, and from about 2,600 tests the repo's list of tests stopped updating. k6 and JMeter uploads from CLI 0.100.0 to 0.109.0 (testrelic upload k6, testrelic upload jmeter) failed too. All of these work now.
• Signing in a device at the token limit. Each user can hold 10 MCP tokens. Signing in Studio or the CLI with all 10 in use could be refused. Now the sign-in revokes the least recently used token that Studio, the CLI or onboarding created for a machine, and that machine has to sign in again. Tokens you created and named yourself under Settings → MCP Tokens are never revoked. If only those are left, the device says the limit was reached and asks you to revoke one. Expired tokens no longer count towards the limit.
• Steps no longer appear twice in runs uploaded with the upload strategy set to both.
• Ask AI: Branch from here and feedback on an answer work as soon as it finishes, without reloading the page.
• Amplitude: errors include Amplitude's own reason instead of a bare "400", and keys Amplitude rejects now show the integration as not valid.
• API: a malformed ID in a /repos/:repoId/… or Ask AI conversation path returns 404 instead of a server error. Repo routes that answered 400 VALIDATION_ERROR for a malformed repo ID now answer 404 REPO_NOT_FOUND, the same as for an unknown one.
• Ask AI apps: connecting an app that isn't in the catalog now returns an error instead of creating a connection.

Ask AI → Remote now reads like Studio's own chat, and its composer has Studio's options. Web chats are unchanged.

• New Session takes New Chat's place on the Remote tab and opens the start-a-session dialog. The Chats tab keeps New Chat, and the collapsed sidebar's + follows the tab you're on.
• Only what was typed. A message sent from Studio or the CLI shows the person's own words. The instructions those apps add to it, such as the reply language, the project rules from TESTRELIC.md and Studio's notes, are hidden. Attached files and recorded steps show as chips under the message.
• Studio's layout. The header says where the agent works (for example "runs and edits on device in repo"). Each answer is headed TestRelic with how long it worked, and consecutive tool calls fold into one "N actions · click to expand" line.
• Approvals as in Studio: Yes, run it, No, skip this or No — tell it what to do instead, with the keys 1–3, y and n, the arrow keys, Enter and Esc once the card has focus.
• Plan first. The permission pill switches between the device's own approvals (for example "Studio's setting") and ⏸ Plan first: click it, press Shift+Tab or type /permission. Under Plan first, that turn gets only the device's read-only tools (reading files and folders, the docs, and git status, diff, log and branches), so it plans and changes nothing. Write tests freely and Full autopilot are still chosen on the device.
• The + menu attaches text files, up to 12,000 characters each, or references a test or run with @. / lists /permission, /model, /effort and /memory, plus report, dashboard, plan, deck, compare and alert prompts.
• Chat settings choose the model and reasoning effort for the messages you send, and Memory marks one message to be remembered. Remote sessions always answer with TestRelic Cloud.

Studio and the CLI need no update. See Ask AI.

A Remote session, the Studio, CLI or runner conversation you follow in Ask AI → Remote, can now be shared with other members of your workspace.

• Share from the session header. The session's owner gets Share, next to the people who have access and who's watching now.
• Two levels of access. Add members by name or email and give each Can view or Can collaborate, or open the session to Everyone in your workspace, who can view it. Copy link gives a link that opens only for members with access.
• Viewers see the live session, its transcript and its artifacts. They can Request to collaborate, and the owner can Allow or Dismiss the request in the Share dialog.
• Collaborators can send messages. A collaborator's message runs on the owner's device with the owner's tools and permissions, and the transcript shows who sent it ("Sent by … from the web"). Collaborators can change only their own queued messages.
• What stays with the owner: approvals, Stop this turn, End session, and changes to the conversation itself, such as renaming or deleting it.
• Finding what's shared with you. A notification appears when someone shares a session with you, and the Remote tab has a Shared with me section. Ended shared sessions move to Archived. Remove from my list hides one without changing anyone's access. If you haven't seen a share in the app within 5 minutes, you get one email about it.
• Workspace members only. Only members of the same workspace can be given access, and someone who leaves the workspace loses it.

Studio and the CLI need no update. See Ask AI.

The default template Ask AI starts each artifact from is now designed for every width, from a share page to the side panel and a phone. Test videos and screenshots embedded in artifacts fit the space they're given.

• A template for every width. In the default template, stat tiles sit four to a row, two in the side panel and one on a phone, and larger cards take the full width. Charts scale with their card, and wide tables scroll inside their own box with the first column kept in view. Slide decks scale rather than reflow.
• Long names wrap. Long test names and URLs wrap in every artifact instead of running past the edge.
• Video fills its frame. An embedded test video takes its height from its width at 16:9, and screenshots at 4:3, instead of sitting in a fixed-height box.
• Screenshots show one at a time, fitted whole, with Previous screenshot and Next screenshot buttons and a counter. Before, the first image was often cropped.
• Embeds keep what the artifact asked for: the right test's recording in a run with several, the moment the video should open at, and any step, log level or search narrowing.
• Cleaner captions. Screenshot captions drop a "Step N:" prefix that never matched the step, and Playwright's failure screenshot reads "At the failure".

See AI Insights & Artifacts.

Settings → Billing has a way to reach the billing team without leaving the page. Any member can use it.

• Billing help in the page header (during a trial, the header shows the trial instead), or Contact billing at the foot of every tab, opens a short form:
  • pick a topic, such as Payment failed, Refund or Tax or billing details;
  • choose the invoice it's about, if it's about one;
  • write your message, and optionally copy someone else.
• Your account details go with it. Sent with your request lists exactly what's included: the workspace, plan, next invoice, billing details, your three most recent invoice numbers, and who sent it from which tab. Your payment method isn't included.
• You get a reference (BH-…) and an email copy. Replies come to your email address. The form says to expect them usually within one business day.

Also in this release, the country and state lists in Billing details open next to their fields again. They had been opening at the top-left corner of the page.

A repository's Overview tab is redesigned around one question: can this repo ship, and what stands in the way.

• A readiness verdict opens the page. Ship-ready, Hold or Blocked, with a score out of 100 (ship-ready is 85), a summary written from your measured results, and the latest run. What moves the score lists the work items that would raise it and the score each would reach. Below, the score's four parts (pass rate, stability, critical paths and the share of tests grouped in a module) are drawn against the same line. Ask AI for a fix plan opens Ask AI with a plan request for this repo.
• Key numbers in one row: pass rate, failing tests, flaky tests with the flake rate, time to feedback (median run time, with p95), time to recover, and runs.
• Time to feedback measures whole runs. It and the Delivery view's median run had shown a per-test median, such as "2s" for a suite whose runs take minutes.
• New widgets. Since the last run shows new failures, fixed tests, tests still failing and new tests, against the previous run on the same branch. Work to green ranks what stands between the repo and a green release, with each test's recent runs and the readiness points fixing it would add. Where the time goes shows each suite's share of test time.
• Pass rate trend shows every day in the window, with days that had no runs left as gaps rather than 0%, plus a target line.
• Renamed widgets: AI defects is now Root causes, and Most affected pages is now Where failures land.
• A quieter toolbar. The filters sit behind Filter, and each applied filter shows as a chip you can remove. Customize shows the controls to drag cards, change their width and remove them, and holds Add a widget.
• Quality and Delivery read as scorecards, with each metric against its target, its trend and a reading.

See Repositories.

The Overview's Configure drawer is replaced by an Overview settings page, and the readiness check now reads every suite you've marked as a critical path.

• Ways in: Overview settings in the Overview's ⋯ menu, Choose critical paths (or Review critical paths) on the readiness band, and Edit targets on the Quality and Delivery scorecards. The page has its own link, and Back to Overview returns you.
• Sections: Critical user paths, Targets, Scorecard display, Blocking lanes, Data sources (GitHub Actions, Jira, Amplitude and BrowserStack, each with Connect or Manage) and Scheduled reports.
• See the effect before you save. A preview re-scores readiness and re-grades both scorecards against your draft. Nothing is stored until Save changes, and leaving with unsaved changes asks first.
• Critical user paths lists every suite with its test count, its pass rate and its latest results, with search and All, Chosen and Failing or flaky filters. Any failing or flaky test in a chosen suite turns the verdict to Blocked. A chosen suite that no test in the window carries is flagged, with Remove.
• Targets show the current value beside each field.
• Fixed on large repositories. The readiness check read only the first 100 tests, so with more tests it could say critical paths were "not set" while suites were chosen, and leave those suites' tests out of the score. It now loads every chosen suite's tests. A chosen suite with no tests in the window reads "no tests here".
• Removed, because they never did anything: the weekly digest and Slack switches (send the Overview with Scheduled reports instead), and CircleCI, Jenkins and LinearB under data sources. Scorecard rows that can't be measured read Not measured yet.

See Repositories.