Inside Claude Code and Codex
Commands and files are checked before they run or get written.
Muzzle stops Claude Code, Codex and Cursor from sending out your email, keys and secrets, and catches pages and files that try to take them over.
Free · Apple Silicon · macOS 12 or later
Stopped going out
Stopped coming in
Commands and files are checked before they run or get written.
A commit that would leak doesn't go through.
A local proxy checks the requests your scripts actually make.
At setup, a scan of your code shows what already leaks.
Pushing to GitHub, deploying to Vercel or publishing to npm goes through as usual.
A Stripe key going to Stripe passes. The same key going anywhere else is blocked.
sk_live_…api.stripe.comAllowedsk_live_…webhook.siteBlockedEvery level can be changed. For the first week Muzzle only watches, then shows you what it would have blocked.
Pro
Crawlers, APIs and push keys often want a contact email. Muzzle gives you a personal address that forwards to you, and when it blocks your real email it tells the AI to use this one.
Macs that contribute to the Threat Feed report what they block. It becomes a signed rules list that every Muzzle install downloads daily.
Seen on
3Macs
Flagged on all
Cleared on
10Macs
Warns instead of blocks
Trusted on
25Macs
Suggested to you
Claude Code and git on Free. Pro adds Codex, Cursor and any script or program that sends requests through the local proxy.
The email, phone number and name you enter at setup, plus API keys and tokens from Stripe, AWS, GitHub, OpenAI, Anthropic, Slack, Google, Supabase and others, and private keys.
The checks run on your Mac, and traffic to your trusted platforms passes straight through.
The checks run on your Mac and the app needs no account. The contact address needs your real email to forward mail to, and the Threat Feed collects only what's listed below.