Cloud Mode Becomes a Control Room
TestRelic Team
Cloud mode and Local mode were never meant to be the same thing wearing different badges — Local is where nothing leaves your machine and every mutation is approval-gated; Cloud is where your team's telemetry actually lives. Until this release, though, Cloud mode mostly looked like Local mode with a cloud icon. Now it looks like what it actually is: a control room.
Nine surfaces, one telemetry model
Cloud mode now has dedicated views for Mission Control, Runs, Signals, Alerts, Insights, Reports, Telemetry, Lanes & Gates, and Connections — replacing a handful of screens that tried to do all of it at once. Each one answers a narrower question well instead of one screen answering all of them poorly.
This pairs with the same week's work on the platform side — the Monitoring tab split by lane, and per-repo telemetry collection settings — so the signals you see in the CLI and the signals you see on the web dashboard come from the same rebuilt pipeline.
Why this matters for the CLI specifically
Mode and Engine are orthogonal in the CLI: Mode (Cloud/Local) is the data boundary, Engine (Claude Code, Codex, Ollama, and others) is which agent backend runs the turn. A telemetry-first Cloud mode means switching into it isn't just a permissions change — it's a genuinely different, more capable surface, not a locked-down version of the same one.
Get started
Switch modes from the CLI or Studio's mode switcher. See Modes & engines for how Mode and Engine compose.