FOR CODEX
Codex Desktop and CLI, live in your Mac's notch
NapCat combines local Codex Desktop thread activity with running Codex CLI processes, so the work that needs you is one glance away instead of buried in an app or terminal tab.
Desktop threads and CLI runs in one island
NapCat reads Codex’s local thread activity and your Mac’s process list, read-only. Active Desktop threads and CLI runs appear as rows in a Dynamic Island-style panel with their project and latest available status. There is no Codex plugin or cloud relay.
Return to the exact work
Click a Desktop row to open that exact Codex thread. Click a CLI row to bring its terminal forward in Terminal, iTerm2 or Warp. You stop hunting through windows for the run that finished.
Keep the Mac awake while it works
One shortcut (⌥⌘N) drops a frosted “asleep” screen over your Mac while Codex keeps running underneath. Keep-awake holds off system sleep, display sleep and the lock timer, so an overnight run finishes. See keep your Mac awake while agents run.
Your Codex plan usage, with nothing to sign in to
The island shows how much of your Codex plan window you have used, beside the Claude meter when you run both. It is read from the rollout logs Codex already writes on your Mac, so there is no sign-in, no network call, and nothing to allow. If Codex has run here, the number is already on disk.
A note on what’s Claude-specific
One NapCat feature is still tied to Claude Code: approving permission prompts from the notch. Codex sessions get the live monitoring, the jump-to-tab, plan usage, notifications, and the nap screen. We would rather say so than imply more than the app does.
Questions
Do I need to configure Codex for NapCat to see it?
No. NapCat reads local Codex thread activity and your Mac's process list, read-only. There is no plugin, extension or Codex config file to install.
Can I approve Codex permission prompts from the notch?
Not today. The Allow/Deny approval hook is Claude Code specific. Codex gets live session monitoring, plan usage, exact return to Desktop threads or terminals, and the nap screen.
Is my code sent anywhere?
Your Codex thread content stays on your Mac. If you explicitly enable product analytics, NapCat may send fixed event metadata such as the provider name and delivery result—never prompts, responses, project names, paths, or session IDs.
What does NapCat require?
macOS 13 or newer on an Apple Silicon Mac. It is $7.99 once with a free 2-day trial, keeps session content local, and draws a mock notch on Macs without one.
Related
See everything on the NapCat homepage, compare it in NapCat vs Vibe Island, browse the full list of supported agents, or read about Claude Code and Cursor support.
Keep AI coding sessions in sight from your Mac’s notch - $7.99, once.
Download - free 2-day trial