VCode home

Update the agents automatically

Agents: claude, codex, opencode, cursor, devin, copilot, muse · On: phone, desktop

Turn on a switch per agent, and VCode runs that agent's own update once an hour on that computer. Each computer keeps its own switches. An agent you install from the Agents card has its switch turned on when the install finishes.

Why you would use it

You want the newest Claude Code, Codex, opencode, Cursor, Devin, Copilot or Muse CLI on every computer without typing /update on each one.

How to use it

  1. Tap the cog (#settings-open).
  2. In Agents (#settings-agents), tap the agent's row. With several computers in the app, pick the computer first with the pick at the right of the title (#agents-box).
  3. Turn on Update every hour (#agent-update-<agent>, for example #agent-update-codex).
  4. The update runs at once, then once an hour. The version under the agent's name changes once the new one is installed. A green update mark sits beside the version while the switch is on, so the closed row shows it too.

The Agents card with Codex CLI open: its version with the green update mark beside it, Logged in · ChatGPT with Log in again, and Update every hour on with its last run

What you see

Beside the version on the agent's row, while the switch is on:

Under Update every hour, the agent's last update:

Devin's devin update needs a terminal to report, so VCode reads Devin's version instead: Updated to devin <version> when it changed, or devin <version> is the latest when it matches Devin's newest release.

An agent that is not installed has no switch: its row offers Install instead. A computer on a VCode too old for the setting shows no switch.

An agent installed with npm

VCode does not update an agent that npm installed, for example with sudo npm install -g @openai/codex. Its update runs npm install -g again, which fails where npm's folder needs root and otherwise puts the new copy in whichever Node comes first on that computer. Its switch shows off and greyed, with:

Run it in a terminal on that computer. Then close and reopen the settings: the switch is back, in the state you left it.

VCode also turns off the agent's own update check in its tabs, which fails the same way: Claude Code and opencode installed with npm start without it. Codex needs nothing, since its update check is only in its terminal app.

The Agents card with Codex CLI open: Update every hour off and greyed, the note saying npm installed it, the command to run, and Copy

Options and settings

Switch, per agent Default What it runs
Claude Off; on once installed from the Agents card claude update
Codex Off; on once installed from the Agents card codex update
opencode Off; on once installed from the Agents card opencode upgrade
Cursor Off; on once installed from the Agents card cursor-agent update
Devin Off; on once installed from the Agents card devin update
Copilot Off; on once installed from the Agents card copilot update
Muse Off; on once installed from the Agents card muse --version with MUSE_SYNC_UPDATE=1, which makes Muse check for a new build and wait

The switches stay on each computer. Settings sync does not carry them.

Limits and known gaps