npx -y cc-safety-net@latest install --amp. It publishes CC Safety Net as a plugin to your Amp Personal Plugins repository, which Amp hosts for your account. Every Amp session on your account then loads it, including threads on Amp Orbs. You need the amp CLI signed in to your account. After installing, restart Amp or run plugins: reload.
Install CC Safety Net in Amp Code
1
Sign in to the amp CLI
Install the
amp CLI and sign in with amp login. If either is missing, install stops and points you to amp login.2
Run the installer
3
Reload Amp
Restart Amp or run
plugins: reload to load the plugin.4
Confirm the plugin is active
update. doctor never reports version drift for Amp Code, because amp plugins list shows no plugin version.
What the Amp Code install changes
Install commitscc-safety-net/index.ts to your Personal Plugins repository and pushes it. Amp loads that file as the plugin.
Install also removes managed copies that earlier releases left behind, because a local copy hides the personal plugin:
cc-safety-net.tsat the root of the Personal Plugins repository~/.config/amp/plugins/cc-safety-net.ts~/.config/amp/plugins/cc-safety-net/, when it holds nothing but a managedindex.ts
Amp Code policy snapshot
Install embeds a snapshot of your user policy file in the published plugin. When you edit the policy, runinstall --amp or update again to publish the change.
- The snapshot applies only on a machine that has no policy file, such as an Orb’s empty home directory.
- A policy file on the machine always takes precedence over the snapshot, even when the file is invalid.
- If your policy file is absent or cannot be parsed, install publishes the plugin without a snapshot.
- The snapshot does not carry audit retention, user rulebooks, or project-scope policy.
What happens when the Amp Code check fails
If CC Safety Net hits an error while it checks a call, it rejects the call. Amp does not document what happens when a plugin crashes, stalls, or fails to load. Treat a session where the plugin did not load as unprotected, and check withamp plugins list.
Amp Code coverage limits
Amp does not define the order in which several plugins subscribed to the sametool.call event run. CC Safety Net checks the input it receives. If another plugin rewrites the input after CC Safety Net allowed it, CC Safety Net cannot check the rewritten input.
Uninstall CC Safety Net from Amp Code
cc-safety-net/index.ts from your Personal Plugins repository and the managed copies listed under What the Amp Code install changes. Anything else in the cc-safety-net directory stays, and so does any copy CC Safety Net does not manage. Afterwards, restart Amp or run plugins: reload.
Troubleshoot Amp Code
Runamp plugins list and look for a cc-safety-net (User Plugins) row with the status active. With any other status, doctor prints:
plugins: reload in Amp, or run install --amp again. Amp reads plugins at startup, so restart Amp or reload after any change.