Cursor sessions, in the one strip nothing else is using

Full-screen is the point, and also the problem

People who live in Cursor tend to run it full-screen. That is not an accident: the editor is where the work is, and the fewer things around it the better. But a full-screen editor is also a wall. The agent's session is running somewhere on the other side of it, and the only ways to check are the ones that cost you the thing you set up full-screen to protect - a space switch, a window shuffle, a mission-control detour.

The notch is the exception. It is already there, it is already not part of any window, and nothing else on the display is competing for it. Noveriq draws the session there, which means checking on the agent stops being a context switch and starts being a glance.

What a glance gets you

Every running session has a card: what it is doing right now, how long it has been going, and whether it is waiting on a human. The waiting ones sort to the front. Nothing expands until you want it to, so the resting state costs you nothing but the strip the camera already lives in.

Answer without leaving the editor

When an agent stops for permission, its hook blocks on a local Unix socket while it waits. Noveriq answers over that same socket, so the prompt resolves in place - the terminal never comes forward, your editor never loses focus, and nothing is typed anywhere.

Destructive shell commands are flagged on the card before you press anything. Three ways to say yes: once, for the rest of the session without writing anything to disk, or always, which writes a durable rule into the project's own settings.

When you do want the terminal

Jump focuses the exact window, tab or split pane the session belongs to - not the application, the tab. Terminal, iTerm2, Ghostty, Kitty, Alacritty, WezTerm, Warp and tmux panes are supported out of the box, and a terminal with no built-in support can be taught with a single line containing placeholders.

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

Nothing is installed into your editor

Noveriq is a standalone native macOS app, not an extension. Hooks are configured on first launch and cleaned up when you remove the app; there is no config file to write by hand and nothing left behind afterwards.

It stays on your Mac

Sessions are read from what the agents already write locally. There is no cloud service, no account, no telemetry in the app, and no way to see a session from another machine.

What it does not do

Noveriq does not edit code, does not run agents, and is not a terminal. Its usage meter shows how much of your Claude Code or Codex subscription window is left, and how much context each session has left, but it does not count tokens or report cost in dollars, and it keeps no spending history by day, session or model. For that, ccusage is the tool people use. It watches and answers the sessions you started yourself.

Questions

Does my Mac need a notch?

Noveriq is built around the MacBook notch, which is where the panel lives and why it costs no window space.

Does it steal focus from the editor?

No. The panel is non-activating: it comes forward without taking focus, so your cursor stays where you left it.

Do I have to use the editor's built-in terminal?

No. It makes no difference where the agent runs. Jump lands on the right tab either way, in any of the supported terminals.

Does it work with other agents?

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