Does Noveriq need Claude Code hooks configured by hand?

No. Noveriq writes the hook configuration on first launch and cleans it up when you remove the app. There is no settings file to edit yourself.

Does approving from the notch send keystrokes to my terminal?

No. Claude Code's hook blocks on a local Unix socket while it waits for a decision, and Noveriq answers over that same socket. The prompt resolves in place. There is no synthetic-keystroke path anywhere in the app.

Does Noveriq send my Claude Code sessions anywhere?

No. Everything stays on the Mac. There are no accounts, no cloud sync and no analytics in the app. Transcripts, prompts and diffs never leave the machine.

Does Noveriq show my Claude Code usage?

It shows how much of your subscription window is left: the 5 hour session window and the weekly window, as a percentage used with a countdown to the reset. That reading comes from Anthropic's own usage endpoint using your existing Claude Code login, so it is the provider's own number rather than an estimate parsed from local files. The meter is on by default and can be turned off in settings, and it also shows how much context each session has left. It does not count tokens, report cost in dollars, or keep a spending history by day, session or model. For that, ccusage is the tool most people use.

Works with

Claude Code, from Anthropic

Claude Code in your MacBook notch

Noveriq shows every Claude Code session in the notch, lets you approve or deny its permission requests without touching the terminal, and jumps you to the exact tab that was waiting. Hooks configure themselves on first launch.

macOS 15 or later · $9.99 once, one Mac · no subscription

The problem is the waiting, not the working

Claude Code does most of its work unattended. The part that costs you the day is the pause: it hits a command it needs permission for, stops, and waits in a terminal tab you are not looking at. You find out minutes later, when you go check.

Noveriq turns that pause into something that reaches you. The session's card comes forward in the notch with the exact command on it, and you answer from there.

Approve without touching the terminal

When Claude Code asks to run something, its hook blocks on a local Unix socket while it waits for an answer. Noveriq replies over that same socket, so the prompt resolves in place - your terminal never comes forward and nothing is typed into it.

There is deliberately no synthetic-keystroke path anywhere in the app. Nothing is ever typed into a window on your behalf. When an agent offers no decision channel at all, the only fallback is Jump, which focuses the right terminal and leaves the answering to you.

A destructive shell command is flagged on the card before you press anything, so a fast Allow stays a safe Allow. And there are three ways to say yes: the button allows once, the menu beside it allows for the rest of that session without writing anything to disk, or always - which writes a durable rule into the project's own settings, the same file you would have edited by hand.

Answer its questions and its plans, too

Permission requests are not the only thing Claude Code stops for. When it asks you to choose between options, those options render as buttons and your pick goes back verbatim in the shape Claude Code expects. When it puts up a plan, the steps are on the card and you approve or send it back from there.

A tool with no bespoke card falls back to a generic one carrying the flattened parameter list, so the notch still shows what the call will do and still offers the same answer the terminal offers.

Land on the exact tab

When you do want to be in the terminal, Jump takes you to the precise window, tab or split pane that session belongs to - not the application, the tab. It works in Terminal, iTerm2, Ghostty, Kitty, Alacritty, WezTerm, Warp and tmux panes.

Jump is the one feature that needs macOS Accessibility permission, because focusing another application's window is what that permission governs. Approving from the notch does not need it.

Setup is one launch

Claude Code reads its hooks from its own settings. Noveriq writes that configuration the first time it runs and removes it again when you delete the app - there is no file for you to edit and nothing left behind afterwards.

# nothing to run. Open Noveriq once, then start Claude Code
# the way you always do:
claude

The next time Claude Code stops for you, the card is in the notch.

It stays on your Mac

Sessions are read from what Claude Code already writes locally, and decisions travel over a local socket. There are no accounts, nothing to log into, and no telemetry in the app at all. Transcripts, prompts and diffs never leave the machine.

What it does not do

Noveriq shows how much of your subscription window is left, read from Anthropic's own usage endpoint through your existing Claude Code login, plus how much context each session has left. What it does not do is count tokens or report cost: if what you want is a breakdown of what Claude Code has spent, by day, session or model, that is a different question and a different tool. It is not a terminal, not an IDE, and not a way to run agents - it watches and answers the ones you started yourself.

Questions

Do I have to configure hooks by hand?

No. Noveriq writes them on first launch and cleans them up on removal.

Does approving from the notch type into my terminal?

No. The answer travels back down the socket the hook is already blocking on. Nothing is typed anywhere.

Does it work with more than one session at a time?

Yes. Every running session gets its own card, and the ones waiting on you sort to the front.

Does it work with agents other than Claude Code?

Yes - Codex, Cursor, Gemini CLI, Qwen Code and opencode are all spoken natively. Any other agent CLI is detected while it runs and gets a card you can jump from.

Stop checking terminals

One price, one Mac, no subscription. Download it first - it asks for a key when you are ready.

Get Noveriq for Mac

$9.99 once · macOS 15 or later · 30 days, money back