Update installed agent CLIs (Codex, Claude Code, ...) from Orca?

[AmethystLiang]

Moved from #24958 to gather input before we commit to anything.

Problem or use case

Agent CLIs (Codex, Claude Code, ...) release often. To update them users have to open a terminal and run each CLI's own update command (codex update, claude update, ...) one by one.

Proposed idea

Let Orca detect when an installed agent CLI has a newer version and offer to update it from the app, either manually (an "Update" action next to the agent in Settings → Agents) or automatically (opt-in setting), on the host that owns the agent (local, WSL, SSH, paired server).

Why we're holding off for now

• Orca's integration depends on CLI behavior. Status detection, hooks, and session resume are tuned to how each CLI behaves. If Orca upgrades a CLI on its own, a new release can break that integration, and some users pin versions on purpose.
• Install methods differ. The same claude or codex can come from an official installer, npm/pnpm, Homebrew, volta/mise/asdf, or nix, each with its own update command and failure modes (sudo, Windows shims, proxies, files locked by running sessions).
• Several CLIs already handle this. Claude Code installed via the official installer auto-updates, and Codex prompts for updates on launch.

What we'd like to hear

• Would a manual "Update" button that runs the CLI's own update command in a visible terminal be enough, or do you want automatic updates?
• Which agents and install methods do you use?

👍 this post if you want it, so we can gauge demand.

[kiendle]

automatic would be nice! maybe have like a CLI versioning page that also has the updates scheduling and rollbacks?