Skip to content

Updates

Caffold

When a new version is out, a dot appears on Settings. To look for one right away, choose Check for Updates in Settings → About Caffold. Update Caffold one of these ways:

  • In Caffold: choose Update Caffold in Settings → About Caffold, from any device.
  • In the menu bar, on a Mac: choose Update to Caffold X… in the menu-bar app.
  • From a terminal: on a Mac, run brew upgrade --cask panarch/tap/caffold, then quit and reopen Caffold Server. On Linux, run the install script again.

All but brew upgrade put the current version back if the new one does not start.

Update Caffold starts a Task in which an agent runs the update and stays with it. Choose the mode that allows everything, Full access or Allow all, if the agent should recover Caffold even when the restore fails. Other modes can stop at the update command, and while Caffold restarts no one can answer approvals.

If an update is rolled back, each browser says so once, the menu-bar app says so if you started it there, and Settings → About Caffold shows it under Last update. The dot stays, and you can try again.

Open windows keep the version they loaded. When a new version is ready, a Caffold update ready dialog offers Reload or Later. Until you reload, the dot stays on Settings and Settings → About Caffold keeps a Reload to update action.

Running work during an update

An update restarts the Caffold server, not the agents:

  • Codex and Grok turns keep running, and Caffold reconnects to them when it is back.
  • Claude Code and Antigravity sessions keep running if the new server is back within ten minutes. Otherwise they stop, and each conversation resumes from its agent's own history when you open its Task again.
  • Open terminals close.

Codex

Caffold does not update Codex in the background. Settings → Codex shows the running App-server version, a different installed App-server version, the newest release, and whether Codex's own automatic updates are on. The CLI version is reference information; it can differ without requiring an App-server update.

Update Codex asks for confirmation, runs Codex's own App-server updater once, and reports what Codex did, including whether its runtime restarted. Restart runtime restarts that runtime without updating it. Every Codex Task, and any other app connected to Codex, shares that runtime, so both can interrupt running work and neither runs without your confirmation.

Claude Code and Grok

Caffold does not update Claude Code or the Grok CLI; update them with their own tools.

Restart runtime in Settings → Claude stops Caffold's runner and every Claude session it holds, then starts a fresh runner with the installed claude. Use it after updating Claude Code. Each conversation resumes from Claude's own history when you open its Task again.

Settings → Grok shows the build of Caffold's Grok leader next to the installed version, so you can see when they differ.

Antigravity

After replacing Caffold, Settings → Antigravity → Restart runtime loads the installed runner binary. It asks for confirmation before ending Antigravity turns. See Antigravity settings for the runtime report and preserved sign-in and conversations.