Qwen Code in your MacBook notch

Three agents, one place to look

Running Qwen Code usually means running it next to something else - one agent on the refactor, another on the tests, a third on whatever you fired off and forgot. Each of them has its own terminal, its own prompt style, and its own way of going quiet.

That is the case Noveriq was built for. Every running session, from every agent, is one card in one strip. The waiting ones come first. There is no per-agent window to arrange and no rotation to keep up.

Knowing which one stopped

With one agent, "something is waiting" is enough information. With four, it is not. Each card carries its agent, what that session is doing, and how long it has been going, so you know what you are answering before you answer it - and Jump takes you to the exact window, tab or split pane that session belongs to, not merely to the terminal application it happens to be in.

Answer in place

When an agent stops for a decision, its hook blocks on a local Unix socket. Noveriq answers over that same socket, so the prompt resolves where it is: no terminal comes forward, nothing is typed. There is deliberately no synthetic-keystroke path in the app, which is what makes answering four sessions in a row safe to do quickly.

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

Even the agent you added yesterday

Any agent CLI Noveriq has no built-in profile for is still detected while it runs and still gets a card you can jump from. You lose the decision channel, not the visibility - so adding a new tool to the mix does not put a blind spot in the row.

Terminals it lands in

Terminal, iTerm2, Ghostty, Kitty, Alacritty, WezTerm, Warp and tmux panes, down to the pane. A terminal with no built-in support can be taught with one line containing placeholders, and a custom rule always beats the built-in one. Jump is the one feature that needs macOS Accessibility permission; answering from the notch does not.

Setup is one launch

Hooks are configured on first launch, for every supported agent at once, and cleaned up when you remove the app.

It stays on your Mac

Sessions are read from what the agents already write locally and decisions travel over a local socket. No accounts, no cloud, no analytics in the app, and no session visible from another machine.

What it does not do

Noveriq's 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, not a cloud dashboard, and not a way to run agents. It watches and answers the ones you started yourself.

Questions

Is there a limit on how many sessions it shows?

Every running session gets a card, and the ones waiting on a human sort to the front so the row stays useful when there are many.

Does answering one session disturb the others?

No. Each answer goes back over that session's own socket connection. Nothing is focused and nothing is typed.

Do I need a separate setup per agent?

No. First launch handles the supported agents together.

Which other agents are spoken natively?

Claude Code, Codex, Cursor, Gemini CLI and opencode.