v0.15.0

The workspace image moves to Debian 13, the file list keeps up with the agent on its own, and the settings behind AI assistance now have a tab of their own. The new base image also moves Python from 3.11 to 3.13 — see Upgrade notes.

New

• The file list refreshes itself. FILES updates when a session goes back to waiting for input, keeps up at a low rate while one is running, and refreshes when you return to the tab; rows that appeared since you last looked are marked. The refresh button is still there.
• The command palette opens on your sessions. Ctrl/⌘+P lists them first, ordered by which ones want attention, with the repository, the worktree and the state on each row.
• AI assistance has a settings tab of its own. Titles, reply suggestions, branch names and file-edit proposals are configured in one place, with their own CLI order and models, rather than sharing the assistant’s settings; branch-name and file-edit suggestions can now be turned off. Read-aloud has its own language instead of following the answer language.
• Node can be installed from Settings > Toolchains, as the JDK already could. A version that is not on disk now offers an Install button; until now choosing one did nothing until the workspace was restarted, and said nothing either.

Improved

• The workspace image is built on Debian 13 (trixie), with a newer Chromium, and it now includes git-delta.
• Changing a workspace’s architecture puts back what you installed yourself. pip --user packages, uv tools and globally installed npm packages are reinstalled for the new architecture at start-up; what cannot be repaired — build output under ~/repos, your own binaries in ~/.local/bin — is named in the notification centre instead of turning up later as Exec format error.
• The Codex and OpenCode background servers no longer start unless that agent is signed in, and they stop when nothing has asked for them for a couple of minutes, giving a few hundred MB back to the workspace.
• The first prompt you type in “Start work” survives closing the dialog. It is kept per repository and cleared only once a session has actually started.
• Sign-in errors from an agent follow the Console’s language; an English Console showed them in Japanese.
• Worktree rows name their directory in the tooltip, and the right-click menu no longer repeats the launch entries the button already offers.
• “Changed files” is gone from the session ⋯ menu; the list itself stays in the mirror’s header band and in the command palette.

Fixed

• A Claude session could fail to start a turn while peer messaging was enabled — the tools were advertised with an incomplete schema, and the request was rejected before the turn began.
• Attachments no longer disappear. Pasted or dropped images survive closing the launch dialog, switching sessions and a refused send, instead of leaving the text behind with no image.
• The file viewer keeps your reading position when you switch to another tab and back, and the bare terminal no longer shows for a frame before the mirror appears.
• Cancelling a question card could leave the composer unable to send, asking you to answer a card that was no longer anywhere on screen.
• On a phone, pinch-zooming an image and moving it switched to another session.
• On ECS every deployment path had stopped: cfn/30-ingress.yaml had grown past CloudFormation’s 51,200-byte limit, so both standing a deployment up and updating one failed. The template is back inside the limit, and the scripts fall back to S3 for one that exceeds it.
• The admin entries disappeared from the account menu while the backend was failing and stayed gone until the page was reloaded.
• A managed session that could not start because the agent was not signed in said “wait a moment and try again”; it now says what is actually wrong.
• Selecting text across a line break offered no highlight picker.
• A notification whose conversation had been deleted was a dead end; it now takes you to the session that reported, and says why.
• Importing memory showed a failed secret scan as though nothing had been found.
• Codex-generated images can be opened from a shared file preview.
• Operator odds and ends: teardown says why it could not empty a bucket, the stand-up preflight checks a captured environment against the current templates, and a capture keeps values that exist only as stack outputs, so a re-created deployment no longer strands its Elastic IP.

Upgrade notes

Python moves from 3.11 to 3.13, and anything you installed with pip install --user or uv tool install has to be installed again. Nothing is deleted — the old files stay in ~/.local/lib/python3.11/site-packages — but 3.13 does not look there, so a launcher in ~/.local/bin still starts and then fails with ModuleNotFoundError. The workspace’s start-up log lists the affected packages and the exact command to reinstall them. Every workspace goes through this once, on the first start on the new image; it is unrelated to changing architecture, which repairs itself.

Agent CLI pins: Claude Code 2.1.261, Codex 0.153.4, OpenCode 1.18.29, Copilot 1.0.83, Antigravity 1.1.26, Cursor 2026.09.02, Kiro 2.21.1. Also Go 1.26.8, gh 2.100.0, AWS CLI 2.36.40 and Chromium 152.