Changelog

Settings moved to plain row cards for theme, fonts, and task prompts.

The composer gained an environment chip, so you can see and switch where a run executes without leaving the input.

Cloud environments got a dedicated UI, alongside sidebar and settings fixes.

A polish pass over the composer's repository chips, the sidebar and account area, and the settings shell.

The desktop bundle now contains a freshly built web export. The build step bundled whatever export happened to be on disk, so the app could ship an interface older than the code it was built from.

Groundwork for the settings rework that lands across the following releases.

A security and reliability release, and the first one where Stop means stop.

Stop actually cancels

Pressing Stop used to detach the run from the interface while the work carried on underneath — the agent kept writing files and burning tokens with nothing on screen to show it. Cancellation now propagates to the process and the sandbox, local and cloud alike, so the run ends when you say it ends.

Isolation

• File access is confined to the workspace you opened; paths that resolve outside it are refused rather than followed.
• Tenant boundaries are enforced on the cloud side, so one account's runs and credentials cannot be reached from another's.

The editor could pin a CPU core and stay there. Syntax highlighting looped on certain files instead of settling, which showed up as a hot fan and a sluggish window long after you stopped typing.

The highlighter now terminates, and the app recovers on its own from a stuck highlight pass rather than needing a restart.

Cloud runs were a black box: you started one, waited, and eventually got a branch. This release opens them up.

• Full transcript — open any cloud run and read exactly what the agent did, the same view you get locally.
• Live streaming — tool calls and messages arrive as they happen rather than in one lump at the end.
• Stuck runs — several cases where a run appeared to hang forever now either progress or report the failure that actually occurred.

A pass over how the app feels rather than what it does.

• Every button acknowledges your press instead of waiting for the action to finish before reacting.
• Menus grow from the point you clicked, so the thing you opened is where your attention already is.
• Motion follows one rhythm across the app — the same durations and curves everywhere, rather than each surface inventing its own.

All of it respects the system's reduced-motion and reduced-transparency settings; with those on, the app is still and opaque.

Mostly invisible work, and the release the following months of performance fixes were built on.

Accessibility

A full pass over labels and keyboard support: every control reachable without a mouse, and every icon-only button given a name a screen reader can announce.

Structure

The parts of the interface that re-render during streaming were separated from the parts that do not, which is what made the later streaming work possible.