CLI versions and one-click updates
Pin the version of Claude Code, Codex and OpenCode your boxes run, and move every box to a new one with one button, without interrupting anybody.
- Reading time
- 2 min read
- Who
- Owner
How it works
Left alone, every box updates its agent CLI on its own schedule, boxes drift apart, and the screen DevBench reads changes under it. Settings → AI has, under Coding agents, a tile for Claude Code and one for Codex: the version your organization is pinned to, the newest release, how many boxes run which version, and a link to the changelog.
Update all boxes moves every running box of that agent to the version in the field, the newest release unless you type another, without interrupting anybody:
- Installed beside the running session. A running agent keeps the program it started with, so nothing changes under someone mid-task.
- Restarted only when idle. No turn running, nothing typed in the composer, no scheduled run using the box, no question waiting for an answer. A busy box is marked restarts when idle and picks up the new version at its next quiet moment. The restart resumes the conversation.
- Checked afterwards. A box that does not come back usable is put back on the version it had, and its row says why.
The first box goes alone, as a canary: the least recently used running box. If it fails, the update stops there, no other box is touched and the pin does not move. Roll back puts every box back on the version before the last update, the same careful way.
Once a version is pinned, boxes stop updating themselves. A stopped box is not started for an update; it installs the pinned version when it next starts. The pin belongs to your organization, so another organization on the same DevBench keeps its own.
Steps
Open Settings → AI and find the Claude Code and Codex tiles under Coding agents.
On the boxes shows how many run which version.
Read the Changelog for the version you are about to install.
Leave the version field on the newest release, or type the version you want.
Press Update all boxes.
The first box updates alone. Each box lists every box as it goes: updated, restarts when idle, rolled back or failed.
If the new version misbehaves, press Roll back to the previous version.
Every box goes back the same way: installed first, restarted when idle.
Worth knowing
Restarts when idle is a success, not a failure: the new version is installed and the session moves to it at its next idle moment, not in the middle of somebody's work.
Until the first update, a tile says Not pinned, boxes update themselves. That is the old behaviour, and the reason to pin.
If the canary fails, nothing else changes and the pin stays where it was. Its row in Each box says why.
Everyone in the organization can see the tiles; only an owner can update or roll back, because an update restarts sessions.