# Turn on protection

> With Pro, Excellent's live check runs in 9 agents once you turn it on. What it blocks, what it asks about, what it adds to each agent's settings, and how to take it back out.

> **Pro**
>
> This needs Excellent Pro. Scanning and findings are free. [Free and Pro](https://www.excellent.so/docs/free-and-pro) says what each does.

With Pro, once you turn it on, Excellent checks each action before it runs. It blocks some actions outright and asks
you before others. It's off until you turn it on. If Pro ends, Excellent turns it off cleanly, the same way **Turn
Off** does, so no agent is left blocked.

## Turn it on

Any of these turns it on:

- **Protect My Agents** on the welcome screen. It lists what it will change before it changes anything, and turns on
  the protections you left ticked there: pausing on a rule break and the sandbox.
- **Turn On** in the menu.
- The **Protection** switch on the Overview.
- **Block this from now on** or **Ask me first from now on** on a finding, which turns on that rule too.

## Which agents

The check runs in 9 agents: Claude Code, Codex, Grok Build, Cursor, GitHub Copilot CLI, Gemini CLI, Qwen Code,
Factory Droid and Devin (through Claude Code's hooks). It's added to each one Excellent finds on your Mac.

Codex, Cursor, Devin and Gemini CLI can't pause to ask you. In those, "ask" becomes a refusal that tells the agent to
ask you first.

## What it checks

| Rule | What happens | At first |
| --- | --- | --- |
| Never send your email to websites | Blocked | On |
| Never type API keys into commands | Blocked | On |
| Never delete protected folders | Blocked | On |
| Ask before writing over never-delete files | Asks you | On |
| Ask before overwriting history on main | Asks you | On |
| Ask before skipping git hooks | Asks you | On |
| Ask before typing your email into web forms | Asks you | On |
| Ask before reading keys and .env files | Asks you | Off |
| Follow the rules in your CLAUDE.md and AGENTS.md | Asks you | Off |
| Publishing and deploys | Recorded in your findings | On |

Each rule can be turned on or off on the Protection page. When the check blocks or asks, you get a notification:
**Excellent blocked it** or **Excellent asked first**, with the agent and what it tried.

The agent gets the reason too, in plain words, so it can find another way. That reason becomes part of the agent's
conversation, which goes to its provider like the rest of it.

## What it changes

Turning protection on:

- adds one Excellent entry to each agent's own hook settings, such as `~/.claude/settings.json` and
  `~/.codex/hooks.json`, and those of Cursor, Gemini CLI, Qwen Code, Copilot CLI, Factory Droid and Grok Build when
  they're installed;
- copies each of those files into Excellent's data folder before changing it;
- puts a copy of Excellent's engine in its data folder for those entries to run;
- tells Codex to trust Excellent's entry;
- on the welcome screen, adds Excellent to your login items and asks macOS to let it send notifications.

## Turn it off

**Turn Off** in the menu takes its check back out of each agent's settings, and changes nothing else. Codex's trust
setting, shared rules, a sandbox and commit watching stay until you undo each one.

## What it can't do

- The check reads what a command says. An agent set on getting around it sometimes can. For files and folders, the
  [sandbox](https://www.excellent.so/docs/sandbox) holds however a command is written.
- Commands sent to a Codex shell that was already running aren't checked. The Protection page explains this under
  **Codex shell coverage**.
- It asks before `--no-verify`, but only your git server can stop a skipped check for good. See
  [Git protection](https://www.excellent.so/docs/git).
- It isn't a wall around your Mac. It's one check, added to each agent's own settings, that the agent runs before
  each action.

Source: https://www.excellent.so/docs/turn-on-protection
