update re-runs the install for every CC Safety Net integration already on your machine, including disabled ones. It never installs a new integration and leaves unconfigured agents unchanged.
u in the interactive install selector. update takes no target flags or arguments, only -h or --help.
Which integrations update refreshes
An integration qualifies when it is installed, even when it is disabled. A few agents have their own rules:update also migrates an install that uses a legacy plugin identifier, such as safety-net@cc-marketplace, to the current one. See Migrate from a legacy plugin identifier.
How update runs each target
update runs the same operation as install for each target, then prints each report as Updated … or … up to date.
When an install runs the agent’s own CLI and that binary is missing, update prints <Agent> not found; skipped, for example Codex not found; skipped, and continues. Antigravity CLI, Cursor, Devin CLI, Factory Droid, Grok Build, and Kimi Code only need a config file, so they always refresh.
Kimi Code through its native plugin and DeepSeek Harness have their own update behavior. See Kimi Code and DeepSeek Harness.
npx cache clearing during update
When any integration that runs throughnpx is present, update clears the npx cache once before it runs the targets. See npx cache clearing for the agents and cache locations. If the clear fails, only the npx targets fail.
bunx cache clearing during update
Everyupdate run clears your cc-safety-net entries from the bunx cache, even when it finds no integrations, so your next bunx cc-safety-net fetches the latest release. If the clear fails, update prints the error and exits 1.
update with no installed integrations
When nothing qualifies,update prints No installed integrations found. Run `cc-safety-net install` to set one up. and exits 0.
Update-available nudge
When the npm registry has a newer release,update ends with this notice:
npx or bunx skip the check, because those runs already fetch the latest release. If the check fails or you are offline, update prints nothing and the exit code does not change.
update exit code
One target’s failure does not stop the run.update prints its error with the same hints as install. update exits 1 if any target failed, if the bunx cache clear failed, or on an unknown option or argument. Otherwise it exits 0.