Keep the CLI up to date — CodeAgent Mobile Wiki
The CodeAgent Mobile Wiki

Every feature, explained — organized by the path you actually take: set up, launch a session, supervise the run, ship the PR.

Free

Keep the CLI up to date

When your paired CLI is out of date, update it in one tap from the app — no terminal needed.

01 · DETECTUpdate available
Out-of-date CLI
  • e.g. v2.61.18 → v2.61.22
02 · ONE TAPUpdating
Update now
  • The CLI self-updates + relaunches
03 · DONEReady
Back online
  • Latest version, same session

The CLI ships fixes and new features often. When a paired session is running an older codeam-cli, the app surfaces a CLI update available banner with the exact version jump — so you never silently sit on a stale version.

Detected automatically

The app notices when a paired session's CLI is behind and shows the current → latest version.

One-tap "Update now"

Tap Update now and the CLI updates itself on your machine and relaunches — you never leave the app or touch a terminal.

Live progress

The update streams its progress back (updating → relaunching), and tells you if anything went wrong.

Or copy the command

Prefer to do it by hand? Copy npm i -g codeam-cli@latest and run it in your terminal.

The CLI update available banner showing v2.61.18 → v2.61.22, an Update now button, and the npm install command with a Copy button
The update banner: one-tap update, or copy the command.
  1. 1
    Spot the banner

    When a paired CLI is out of date, the "CLI update available" banner appears with the version jump.

  2. 2
    Tap "Update now"

    The app asks your machine to self-update the CLI and relaunch the session.

  3. 3
    Watch it update

    Progress streams back in real time; the session reconnects on the new version automatically.

  4. 4
    Or update manually

    Copy npm i -g codeam-cli@latest, run it in your terminal, and the banner clears on the next heartbeat.

TIP

Staying current matters: some features (like Environment Variables or the Session Baton) require a minimum CLI version, so an out-of-date CLI is the usual reason a newer feature "isn't available" on a session.

FAQ

Related

Ready to try it?