Approvals, questions and plans on the HUD
When an agent asks to run a tool, asks you a question or presents a plan, the request waits on the HUD and you answer it there. Agent HUD never decides for you: a request you leave goes back to the agent after 10 minutes.
Updated 2026-10-29
What you can answer
| Request | Your answers |
|---|---|
| Tool call | Allow once or Deny, with the command, file or change in view. Always allow appears when the agent offers a lasting rule, as Claude Code and the Qoder builds do. |
| Question | One option or several, your own words, or skip a question. Questions Claude asks in its desktop app reach the HUD too. |
| Plan | Claude Code's plan, in full: Approve, Approve, accept edits, or Keep planning with a note for Claude. |
On the HUD or in the agent
Several requests form a queue, and each shows how long it has waited. You can still answer in the agent's own window; when you answer in Claude Code or a Qoder build, its card leaves the HUD by itself. A question or plan the HUD cannot answer shows with a note to answer it in the agent.
Which agents send requests to the HUD
| Agent | Tool calls | Questions | Plans |
|---|---|---|---|
| Claude Code | ✓ | ✓ | ✓ |
| Codex | ✓ | ✓ | |
| DeepSeek Harness | ✓ | ✓ | |
| Antigravity | ✓ | ✓ | |
| ZCode | ✓ | ✓ | |
| CodeBuddy, WorkBuddy | ✓ | ||
| Qwen Code | ✓ | ||
| Devin CLI | ✓ | ||
| Qoder, Qoder CN, QoderWork | ✓ |
If nobody answers
A request waits 10 minutes unless you choose another wait, from 1 minute to an hour. Then it goes back to the agent, which asks in its own window. Nothing is answered for you.
When Agent HUD is not running, each agent asks in its own window as usual.
What Agent HUD writes into your agents' settings
Requests reach the HUD through small hooks in each agent's own settings. Agent HUD writes them only while client hooks are on, adds its entry beside any hooks you already have, and removes only its own when you turn client hooks off.
- A few more additions come only when you ask for them in Agent HUD: its plugins for Claude Code and DeepSeek Harness, its MCP server in an agent's configuration, and a quota callback beside Antigravity CLI's status line.
| Agent | What is added | What it brings |
|---|---|---|
| Claude Code | A hook | Tool calls, questions and plans; a session's waiting state |
| Codex | A hook, run once you trust it | Tool calls. Codex Desktop's own questions and app approvals come from Codex Desktop, with nothing written |
| Qoder, Qoder CN, QoderWork | A hook | Tool calls |
| CodeBuddy, Qwen Code, Devin CLI | A hook | Tool calls and replies |
| WorkBuddy | A hook | Tool calls |
| ZCode | A hook | Tool calls and questions |
| Antigravity | A hook | Replies. Tool calls and questions come from Antigravity's own local channel |
| Cursor, GitHub Copilot CLI | A hook | Replies |
| Pi | An extension | Running status and replies |
| OpenCode | A plugin | Replies |
| DeepSeek Harness | Agent HUD's plugin, when you add it | Tool calls and questions |
Turning client hooks off
- Requests go back to each agent's own window.
- Replies from the agents that report them through a hook, extension or plugin stop.
- Tokens, quotas, sessions and their history stay as they were.
- The hooks stay in your agents' settings until client hooks are turned off. Deleting the app alone leaves them in place, pointing at an app that is gone.
Release and source build
Client hooks come from the release installed in Applications. A build from the GitHub source does not install them yet, so its requests stay in each agent's own window.
Answers to the questions Claude asks in its desktop app go back through Agent HUD's plugin for Claude Code, which has a switch of its own.
Answering away from your Mac
With Agent HUD Remote, the same tool calls, questions and plans reach your iPhone and Apple Watch, with the context to decide. While Remote sessions are on, the release also adds one hook to Claude Code and Codex, which brings their prompts and replies to the conversation on your phone.
Questions
Does a request leave my Mac?
Not unless you use Agent HUD Remote. A request is read on your Mac to draw its card, your answer goes straight back to the agent, and request bodies are not kept as history. With Remote, a request also reaches your iPhone and Apple Watch through your own iCloud.
Will Agent HUD change the hooks I already have?
No. It adds its own entry beside them and removes only its own.
Can Agent HUD approve requests by itself?
No. Every answer is yours. A request nobody answers goes back to the agent.
Why does a Codex request not appear on the HUD?
Codex runs Agent HUD's hook only once you trust it in Codex, and hands over only the requests you review yourself. Requests its automatic reviewer handles stay in Codex.