Changelog

Studio's Tests view can now group by the same AI-classified functional Modules as the cloud platform, in both Local and Cloud mode. See Modules for how the grouping works.

• The Tests view no longer goes stale after a run finishes.
• HTML report popups that were failing to open now work.
• Upload failures no longer fail silently — you'll see them.
• The context-window report now follows whichever engine is currently selected, not just Claude.

• A new context report shows what's actually filling and freeing the AI's memory window, so a long session doesn't run out of room by surprise.
• Headless testrelic -p now dispatches to whichever engine you've actually selected — Codex, Cursor, or Ollama — instead of always defaulting to Claude Code. Ollama also gained cross-turn chat memory.

See Modes & engines.

• The Playwright and Appium MCP presets are now enabled by default, so browser automation tools are available to your AI agent without opting in first.
• Failure screenshots now render inline in the AI conversation, instead of requiring a separate click-through.

The Tests view in Studio is rebuilt around a full-width list with prefix search and grouping.

Scheduled and one-off automation jobs are now unified, with real wall-clock schedules — time of day plus which weekdays — instead of a bare interval. Failure tracking shows streaks, finished runs trigger a desktop notification, and you can edit, retry, cancel, or undo a run directly from Automations.

Studio and the CLI/TUI get a real Git surface — merge, rebase, resolve conflicts, and restore points with undo. Run it from Studio's UI or from the terminal with /git ...; AI agents can propose changes through the same surface but are never allowed to force-push, reset, or discard on their own.

Studio's new Infrastructure surface lets you choose where tests actually run, per run:

• Provision test machines in your own AWS, Azure, or GCP account, or connect BrowserStack or TestMu AI.
• Credentials only ever land in your OS keychain — they never round-trip to the UI — and a run opens a single port to your IP that closes on every exit path; there's no standing inbound rule.
• Cloud mode now shows the platform's real navigation (Repos, Test Runs, Monitoring) instead of local-only surfaces, and the AI assistant (Memory, Automations, Artifacts) works from Local mode too, not just Cloud.

Infrastructure requires a Pro plan. Studio itself now admits Pro and Enterprise orgs — if yours is still on Growth, you'll need to upgrade before Studio unlocks again.