Seven terminals, one brain.
You alt-tab between terminals trying to find the agent that needs you. By the time you do, you forgot what you were doing in your editor.
Every Claude Code session on your Mac, surfaced inside your MacBook's notch. Approve permissions, read replies, glance at status — without ever leaving your editor.
Claude Code, Cursor, Codex — they all want your attention. You either babysit them across five terminals or miss the critical questions.
You alt-tab between terminals trying to find the agent that needs you. By the time you do, you forgot what you were doing in your editor.
Every Edit this file? steals thirty seconds of focus, triggers a context
switch, and breaks flow. Forty prompts a day is twenty minutes of pure tax.
A background Claude session hits a permission gate, sits idle for an hour, and you realize at standup. Compute wasted. Momentum gone.
Never. NotchPilot runs entirely on your machine, talks to
Claude Code over a local UNIX socket, and has no analytics, no telemetry,
no "anonymized" pings. Your license is validated once at install; after that,
zero network calls. lsof it yourself — we dare you.
Yes. On notchless Macs, NotchPilot renders as a floating menu-bar pill — same interactions, same shortcuts, just attached to your menu bar instead of a physical notch.
Only in one place: ~/.claude/settings.json, to register three
hooks (pre_tool, post_tool, on_stop). One
command — notchpilot uninstall — reverts everything and leaves your
settings.json byte-identical to the backup we took.
No. 9,99€ once — lifetime updates, no recurring billing, ever. A 7-day free trial is available (no credit card required), so you only pay if you decide to keep using it. Teams tier lands later; individual pricing stays at 9,99€. Full refund policy here.
Hooks fail open. Your agents keep working without interruption — they just stop
surfacing events in the notch until NotchPilot restarts (which it does automatically
within two seconds via launchd).