Keep kcap up to date

kcap update --check          # what would happen, as JSON
kcap update                  # do it

What update does depends on how kcap was installed:

• Script install (curl … | bash or install.ps1): reads the installer’s channel manifest, downloads this platform’s archive, checks its sha256, unpacks it into its own versions/<version> directory and switches the current link. Running processes keep the files they started from; a daemon service installed from a script install follows the link
• npm: npm install -g @kurrent/kcap@<tag>, then a refresh
• Desktop app: the app updates itself and the CLI it bundles
• Homebrew or others: prints the command to run

Every path then runs kcap refresh, which brings the integrations a previous version installed up to this one: skills, each agent’s hooks and MCP entries, the Claude Code plugin, and any daemon service units. Only integrations you installed before are touched. Run kcap refresh yourself if an update reports a failed step, or after an npm install with scripts disabled

Channels and the cap

kcap update --stable         # the default: npm's latest
kcap update --beta           # run ahead of your server

On the stable channel, updates are capped at the version your workspace server runs, so a CLI never gets ahead of the server it talks to; the beta channel is not capped. The cap is also why a fresh install can land on an older version than npm’s newest

After an update

• The daemon: on macOS and Linux it notices the new binary and restarts when idle, resuming hosted agents that were running; on Windows it keeps the old version until you restart it. kcap daemon status shows the running version and any pending restart
• Project-scoped installs (kcap plugin install --project) are not refreshed; re-run them in each repository
• The git hook is repointed, not added. If it was missing, kcap setup or kcap plugin install once adds it
• The local edition: kcap update runs kcap local upgrade afterwards; see Local edition

How you hear about updates

kcap status prints an available version; the web app shows a banner when your CLI is older than the server recommends; the agent gets a one-line note at session start. kcap config set update_check false turns all three off, and --no-update-check skips the lookup for one command

Help me get unstuck

Hooks stopped working after an update. Run kcap refresh; if a step fails, run kcap setup again. Codex re-asks for trust when its hooks file changes

update says a different install method. The binary on your PATH came from somewhere other than the method it expected: for example npm’s binary with a script-install service. kcap daemon service install again binds the service to the binary you are using now

Windows says the executable is locked. npm moved it aside; running processes continue on the old version until restarted