Studio's agent runs your tests from the chat, on the run target you pick
Ask the agent in a Studio chat to run your tests and it does, after asking, on this computer or on the run target you've chosen.
- In the Cloud view too. An Agent session on your project can now run your tests and the scripts it needs, and edit files, asking first. An Ask AI chat (Chat) still only answers. Before, chats in the Cloud view couldn't run anything.
- Claude Code asks instead of refusing. With Claude Code as the engine, a test command shows an approval card, such as "Run "npx playwright test" in your project?", instead of failing with "This command requires approval", from the first message of a new chat. Your approval mode and "don't ask again" choices apply, and a force-push is still refused.
- Runs follow your run target. Each test run the agent starts goes to the Default run target in the composer's session settings or on the Run targets page, the same way a run from Tests does. A target that can't take the run refuses it and says why; the run never moves to this computer instead.
- Claude Code, Codex and Cursor run tests in their own shell, on this computer. When another target is picked, the picker says so.
- Run cards match the run. A card opens for Claude Code's PowerShell runs on Windows and shows only this run's results, never an earlier report. When the engine cut the output short, the card reads "Saw N of M · output cut short" rather than guessing at the rest.
Released as testrelic-cli 1.8.1.