Stay in flow while Claude Code and Cursor keep working. Monitor sessions, approve permissions, and reply right from the notch.
Claude Code (the CLI, in any terminal) and Cursor's agent. Both appear in one unified panel, so you can run them side by side and watch every session at a glance.
Yes. When Claude Code requests a tool permission, the notch expands with Allow and Deny buttons, and the same works for questions where you click an option directly. For Cursor, shell and MCP commands are gated with Allow, Deny, or Ask-in-Cursor.
When a Claude Code session finishes or is waiting on you, its card shows a reply field. Whatever you type is sent straight into that session's Terminal.app tab, so the agent picks up your next prompt without you leaving your current window.
No. All communication between Notchy and your CLI tools happens locally over a Unix domain socket. No data is sent anywhere, and session content, tool names, and terminal metadata never leave your Mac.
On launch, Notchy installs small forwarder hooks into your Claude and Cursor config files, backing them up first. Your own hooks are never touched, and ours can be removed any time from Settings.
Yes. On a Mac with a built-in notch the panel sits in the notch; otherwise it appears as a compact bar at the top center of the screen. One island per display.
No. It's a native Swift app for Apple Silicon, typically under 50 MB of RAM and near-zero CPU when idle. The panel is a non-activating overlay, so it never steals focus.