npx -y cc-safety-net@latest install and pick your coding agents from the list. The installer adds CC Safety Net to each agent you pick as a plugin, extension, or hook. Some agents then need a restart or a trust confirmation. Run npx cc-safety-net doctor to confirm that protection is active.
Before you install
- Install Node.js 22 or later. The commands on this page use
npx. Node.js 18 and 20 have reached end of life, and CC Safety Net no longer supports them. - Check that your platform is supported for your agent:
Amp’s own manual documents macOS, Linux, and WSL rather than native Windows.
Install with the interactive picker
1
Start the installer
2
Select your agents
Press
Space to select an agent and Enter to confirm. Target selector keys lists the other keys.3
Finish the agent's own step
If your agent needs a restart or a trust confirmation before the hook runs, do that now. The “Extra step” column in Install for one agent lists these steps.
4
Confirm protection is active
doctor checks every supported agent and tells you how to fix anything that fails.
Keep @latest in the install command. npx keeps downloaded packages in a cache, and a bare cc-safety-net can re-run an older copy from that cache instead of the current release.
Install for one agent
To install for one agent, for example from a script, pass that agent’s target flag from the table below. Each agent’s page covers what the install changes, what the agent’s hook checks, and how to remove it.
You can run an install command again safely. On an agent that is already configured, it leaves a single managed entry.
Update CC Safety Net
update refreshes every integration already installed on your machine and never installs a new one. See update for what it does per agent.
Upgrade from v1 or from 2.2 and earlier
- From v1. Run
updateto move every installed integration to the current release. If you defined custom rules in v1’s inline configuration, complete the legacy migration. Then confirm the runtime isreadywithnpx cc-safety-net doctor. - From 2.2 or earlier, with rulebooks from GitHub. After upgrading, run
rule synconce per scope. Add--globalfor user-scope sources. Until you run it, those rules are inactive, andstatusanddoctorreport the degraded sources.
Uninstall CC Safety Net
Run the installer’s uninstall picker, or pass one target flag:Install the CLI globally
If you run the CLI often, install it globally. The global install addsccsn, a shorter alias for the same commands:
npx runs use the full cc-safety-net name.
Migrate from a legacy plugin identifier
In older releases, Claude Code and Codex used the plugin identifiersafety-net@cc-marketplace, and GitHub Copilot CLI used copilot-safety-net. The normal install command for the agent removes the old plugin, so you do not need to remove it by hand. Use the current identifier, cc-safety-net@cc-marketplace, in new configuration.