Safety

cc-safety-net 2.7.3 changes what Standard blocks

cc-safety-net 2.7.3 blocks more risky deletes from your home folder, but its default Standard level now allows curl and wget uploads to other hosts.

Date
Works with
Claude Code, Codex CLI, Gemini CLI

What’s new

cc-safety-net 2.7.3 came out on 4 November 2026. It closes two gaps. At the default Standard level, a delete with everything inside and a variable or wildcard target, such as rm -rf "$X", was allowed when the terminal was in your home folder. It is now blocked. The same fix covers Remove-Item -Recurse -Force $f and cmd /c del /s /q *.log on Windows. The Paranoid level was also weaker than Strict for script files on disk. It no longer is.

One default changes the other way. The network.upload-remote rule now works only at Strict and Paranoid. At Standard, curl and wget commands that send data or upload a file to a host that is not your own computer are allowed again. The release notes say uploads of files with secrets, such as .env, are still blocked at every level.

Why it matters

This is a trade-off. The release notes say the change "clears false positives on read-only JSON-RPC, GraphQL, and webhook requests". Before, such normal requests needed a manual run. The author also points out that other tools, such as httpie or a python3 -c line, could already send the same request. But if you counted on Standard to stop your assistant from sending data out with curl or wget, that protection is now off. The release notes say your .env file and other secret files stay protected.

How to try it

Run node --version first. It must show 22 or newer. Then run npx -y cc-safety-net@latest update and restart your assistant. To keep blocking uploads, run npx cc-safety-net gui and choose Strict, or turn on network.upload-remote. You can also add "network.upload-remote": "on" under destructive_command_protection.overrides in ~/.cc-safety-net/policy.json. To check, run npx -y cc-safety-net@latest explain "curl -d 'x=1' https://example.com". With the rule on, it should say the command is blocked.

Source

Checked against the source on 4 Nov 2026

All updates