Answer Claude from the notch
Blocked questions surface as cards with numbered options. Permission prompts show Allow, Always, Deny. Pending plans render as Markdown. One click types the answer into your terminal.
Live sessions, usage limits, and blocked questions in the bar you already ignore. Answer without switching windows.
You kick off three sessions, then spend the next hour tabbing around to see if any of them stalled on a permission prompt. Sessions sit blocked for twenty minutes because a question scrolled past. NotchViber puts every session's state one glance up.
5-hour block26% used, 4h0m to reset
Status dots blue working, cyan waiting, green done
7-day and Fable windows8% and 12% of the week used
Live activitywhat each session is doing right now
Weighted tokensthe math behind the percentages
Blocked questions surface as cards with numbered options. Permission prompts show Allow, Always, Deny. Pending plans render as Markdown. One click types the answer into your terminal.
Type into the prompt bar; NotchViber resumes the session headlessly with a forked transcript.
claude -p --resume --fork-session
Click a row and land in the window that owns it: Ghostty, iTerm2, Warp, kitty, Zed, Cursor, VS Code, and more.
NotchViber reads ~/.claude/projects/**/*.jsonl and nothing else. No network calls, no telemetry, no credentials touched. Unplug your router; everything still works.
NotchViber parses your local transcripts and weights tokens by cost. Usage rolls into 5-hour blocks plus a 7-day window, with message IDs de-duplicated so resumed and compacted sessions never double-count.
An estimate, not Anthropic's ledger. Calibrate once against /usage in Claude Code; if observed usage ever exceeds a configured limit, the limit stretches so the bar never reads past 100%.
26%
of the current 5-hour block, computed from your own transcripts
NotchViber identifies the terminal that owns each session and jumps to that exact window.
NotchViber shows your current 5-hour block percentage and time to reset on the left of the notch, and your 7-day usage on the right. Both are estimated locally from your ~/.claude transcripts. No login, no API key.
Usage accrues in 5-hour blocks that anchor to your first message after the previous block ends, alongside a weekly window. NotchViber computes both locally with ccusage-style weighted tokens and de-duplicated message IDs.
Yes. NotchViber turns the MacBook notch into a Dynamic Island for Claude Code. On Macs without a notch it runs as a floating pill at the top of the screen.
The right wing shows a cyan dot when a session is waiting, and NotchViber plays a soft sound when a session finishes, asks a question, or requests permission. The question itself appears as a clickable card in the island.
Yes. Permission prompts surface as Allow, Always, or Deny cards in the island. Clicking one answers the terminal prompt for you via Accessibility keystrokes.
No. NotchViber reads ~/.claude/projects/**/*.jsonl on your disk and makes zero network calls. No telemetry, no account, and your credentials are never touched.
They use the same weighted-token method as ccusage, computed locally. Anthropic does not publish exact limit math, so treat the numbers as a close estimate, not a contract. Calibrate once against /usage and they track closely.
Ghostty, iTerm2, Terminal, WezTerm, kitty, Alacritty, Warp, Zed, Cursor, and VS Code. Clicking a session jumps to the exact window that owns it. tmux and Zellij sessions are attributed to their server process.
Yes. Free, built by one developer, and it runs entirely on your machine. It needs macOS 14 or later on Apple Silicon.