How to pause ChatGPT / Codex on Mac
OpenAI’s Mac footprint can include ChatGPT.app, Codex.app, the codex CLI, MCP servers in config.toml, auth tokens, and optional computer control or Chrome integration. Here is how to control all of them.
What AI Stopper detects for ChatGPT / Codex
- macOS app bundles:
ChatGPT.appandCodex.appin/Applicationsor~/Applications - CLI & Node script:
codexbinary,bin/codex, andnode_modules/@openai/codex/bin/codex.js - Snapshotted config & auth:
~/.codex/config.tomland~/.codex/auth.json - Detected optional features: computer control (
~/.codex/computer-use) and Chrome integration (~/.codex/plugins/cache/openai-bundled/chrome)
How to stop ChatGPT / Codex manually on macOS
- Finish or interrupt any running Codex CLI task with Control + C, then exit the terminal session.
- Quit
ChatGPT.appandCodex.appwith Command + Q (and check the menu bar companion icon if enabled). - Inspect configured MCP servers and auth files before opening confidential repos or sharing your screen.
Check for running processes in Terminal (read-only):
ps -eo pid,ppid,comm,args | grep -Ei "ChatGPT.app|Codex.app|/codex($| )" | grep -v grep
Check config / MCP entries:
codex mcp list
Why manual quitting misses edge cases: ChatGPT’s companion bar stays active in the macOS menu bar even when no chat window is open, and Codex CLI keeps credentials in ~/.codex/auth.json and MCP entries in ~/.codex/config.toml across all directories.
What happens when you pause ChatGPT / Codex with AI Stopper
- Detects ChatGPT.app, Codex.app, and Codex CLI together under one entry—and flags computer control or Chrome integration if present on disk.
- Snapshots
~/.codex/config.tomland~/.codex/auth.jsonlocally during pause without touching unrelated commands reading those files. - Blocks accidental relaunches via Restart Guard and optionally blocks AI domains during a full pause.