Setup & agents

Which agents does Muzzle protect?

• Claude Code (Free)
• Codex (Pro)
• git commit checks (Free)

Muzzle does not set up protection for Cursor or Copilot. See system requirements.

Muzzle does not detect my agent

Start Claude Code or Codex once so it creates its ~/.claude or ~/.codex folder, then open Settings in Muzzle again. The tool then shows under Protected tools.

Why does Codex need another setup step?

Codex protection needs Pro. Turn on Codex under Settings → Protected tools, open a fresh terminal, then start Codex and type /hooks to turn hooks on.

Script requests do not show up in Activity

Activity lists only blocked and warned requests. Every site Muzzle sees is listed in Destinations.

If a script’s requests are missing there, check that Claude Code is on under Settings → Protected tools, then start a new Claude Code session. Inspecting script traffic needs Pro.

Will Muzzle work with a VPN, corporate proxy or managed Mac?

Yes. Muzzle keeps your existing proxy in place, but traffic that goes through that proxy is not inspected. On a managed Mac, your IT administrator may need to allow Muzzle’s certificate.

Muzzle asks me to trust a certificate

Muzzle needs its certificate to look inside HTTPS requests. Choose Trust Muzzle’s certificate system-wide in Settings, then restart the affected tool. The button only shows while the certificate is not trusted. On a managed Mac, your IT administrator may have to allow it.

Little Snitch or another firewall asks about Muzzle

Allow Muzzle to connect to 127.0.0.1 (its local proxy, usually port 8899) and to usemuzzle.com.