Pause AI tools for client NDA & confidential work
Switching from your own AI-assisted projects to a strict no-AI client repository should not require uninstalling Cursor, wiping MCP configs, or guessing whether a background agent is still alive.
The 4 things people forget before opening an NDA repo
- Background CLI & desktop helpers: Closing a Cursor or Claude window often leaves helper processes, terminal tabs, or voice-dictation listeners running.
- Global MCP servers & auth files: Files like
~/.cursor/mcp.json,~/.claude.json, and~/.codex/auth.jsonstay active across repositories unless moved or disabled. - Silent auto-restarts: Launch agents, Homebrew services (
ollama), or accidental shortcuts can bring an assistant back mid-session. - Outbound AI API calls: Even when main apps are closed, secondary tools or extensions may attempt requests unless AI domains are blocked.
Your 60-second zero-AI routine on Mac
- Save and close active personal sessions in Claude Code, Codex, Cursor, and Windsurf.
- Review what is running in AI Stopper’s window—check detected tools, recognized MCP config counts, and special Codex features like computer control or Chrome integration.
- Trigger a Full Pause from the menu bar: AI Stopper stops all matching process trees across 33 supported tools, snapshots supported config/auth files locally under
~/.aistopper/, enables Restart Guard, and—if installed—activates the optional AI-domain blocker. - Verify the menu bar state: Confirm the ice chip is active, Restart guard is active, and (if using domain blocking) AI domains: test endpoints unreachable.
- Restore when you finish: Close the NDA repo, click Resume Tools, and every snapshotted MCP config, auth file, and Homebrew service returns cleanly.
Check browser tabs & remote boxes too: AI Stopper controls your local Mac environment. Close cloud AI web tabs and pause any remote CI or server agents separately.