← AI Stopper home

How AI Stopper works

AI Stopper pairs exact macOS process-tree matching with journaled local config snapshots, a restart guard, an optional AI-domain blocker, and a standalone recovery app.

1. Offline discovery of 33 AI tools

When you open AI Stopper, its local engine reads an offline registry covering 33 macOS AI tools across coding agents, desktop assistants, local LLM runners, and voice/image apps. For each tool, it checks:

  • App bundles: Exact .app bundle names in /Applications and ~/Applications, plus child helper processes launched from inside each bundle.
  • CLI executables & scripts: Commands on PATH, Homebrew paths, ~/.local/bin, and exact Node or Python entry-point scripts (such as Claude Code, Codex CLI, Gemini CLI, Aider, OpenCode, and Copilot CLI).
  • Homebrew services: Background daemons such as ollama.
  • Config, auth & MCP paths: Recognized global and project configuration files, plus special Codex features such as computer control and Chrome integration.

2. Exact process pause (full or partial)

You can click Pause All Tools directly from the menu bar, or open the window and toggle a subset of tools. AI Stopper identifies processes by kernel executable path and script entry point—never loose substring matches—so reading a config file with cat ~/.codex/config.toml or less ~/.claude/settings.json is never touched.

Matching processes and their child helpers receive a clean termination signal, and tracked Homebrew services like Ollama are stopped so they do not respawn silently.

3. Atomic local config snapshots

Stopping a process is only half the problem: reopening an IDE or CLI can immediately reconnect to configured MCP servers or stored auth tokens. During a pause, AI Stopper writes a recovery journal under ~/.aistopper/paused.json and moves supported config/auth files into a local snapshot folder under ~/.aistopper/snapshots/.

Every transition is crash-safe. If a pause or restore is interrupted mid-way, AI Stopper detects the unfinished journal phase on next start and recovers cleanly without overwriting files modified during the pause.

4. Restart Guard

While tools are paused, the menu bar chip switches to its ice state and the local Restart Guard monitors for relaunches of paused tools. If a background launcher or stray shortcut tries to restart a paused tool, the guard terminates it until you explicitly click Resume Tools.

5. Optional AI-domain blocker with leak check

Process pausing works independently with no admin privileges. If you want network-level assurance during a full pause, you can install AI Stopper’s optional AI-domain blocker (ru.aistopper.netguard). When full pause runs, it blocks known AI domains on your Mac and runs a connection check shown right in the menu bar:

  • Test endpoints unreachable: Domain blocking is active and verified.
  • Allowed during partial pause: Domains stay reachable when you only pause selected tools.
  • Warning indicator (⚠︎): Alerts you immediately in the menu bar if Restart Guard is offline or a test endpoint is still reachable.

6. Resume Tools & standalone Recovery

When you are ready to work with AI again, click Resume Tools. AI Stopper stops the Restart Guard, lifts full-pause domain blocking, restores every snapshotted config file to its exact original path, and restarts Homebrew services that were running before the pause.

If the main app ever fails to launch, open AI Stopper Recovery in ~/Applications/AIStopper Recovery.app. It bundles its own copy of the restore engine and can also uninstall the optional domain blocker.