opencode in your MacBook notch

If you chose an open agent, you probably care where the data goes

People who run a community-built, open-source agent tend to have opinions about what runs on their machine and what phones home. It seems fair to answer that first, before any feature.

Noveriq is not a cloud service. There is no account, nothing to log into, and no session is visible from another machine. It reads what opencode already writes locally, and every decision travels over a Unix socket on your own Mac. The app contains no analytics at all; the marketing website counts visitors, the app does not. Transcripts, prompts and diffs go nowhere.

What it shows

Every running session gets a card in the notch: what it is doing, how long it has been going, and whether it is waiting on a human. The waiting ones sort to the front, so a glance replaces the habit of cycling through terminal windows.

Tool inputs are parsed once as they arrive and rendered as a typed card rather than raw JSON. A tool with no bespoke card falls back to a generic one carrying the flattened parameter list, so an unfamiliar call still shows what it will do.

Answering over the socket

The agent'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: no terminal is focused, nothing is typed. There is deliberately no synthetic-keystroke path anywhere in the app.

What Noveriq can do for a given session depends on what that agent exposes. opencode is spoken to natively, with full status and decision support where the agent offers the channel for it - but a visible session does not by itself mean every prompt can be answered from the notch. Where no decision channel exists, the fallback is Jump.

Destructive shell commands are flagged on the card before you press anything, and there are 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.

Jump, and the terminal you actually use

Jump focuses the exact window, tab or split pane a session belongs to in Terminal, iTerm2, Ghostty, Kitty, Alacritty, WezTerm, Warp and tmux panes. If yours is not on that list, one line containing placeholders teaches it, and a custom rule always beats the built-in one.

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

Setup, and undoing it

Hooks are configured the first time Noveriq runs; there is no config file to write by hand. Delete the app and the configuration is cleaned up again, which is the part worth knowing if you are careful about what other software leaves in your dotfiles.

What it does not do

Noveriq is a status and decision surface. 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 - ccusage is the tool for that. It is not a terminal emulator, not an IDE, and not a way to run agents. It watches and answers the ones you started yourself.

Questions

Is there a subscription?

No. $9.99 once for one Mac, updates included with no upgrade fee, 30 days money back.

Is there a trial?

There is no time-limited trial. Download the app and use it; it asks for a license key when you are ready to buy.

Does it need network access to work?

The session watching and the decision path are entirely local. Nothing about your sessions is sent anywhere.

Which other agents are spoken natively?

Claude Code, Codex, Cursor, Gemini CLI and Qwen Code. Any other agent CLI is detected while it runs and gets a card you can jump from.