Requests
Answer agents' permission requests, questions and Claude Code plans on the HUD. A request you leave goes back to the agent after 10 minutes.
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, which asks in its own window.
Client hooks first
Requests reach the HUD once Client hooks is on in Settings → General, in the Agent HUD installed in Applications. See Install on Mac.
Tool calls
The card shows the agent, the session's folder and the command, file or change it wants to run. A file edit shows its change under Edit preview.
| Answer | What happens |
|---|---|
| Allow once | The agent runs this call. |
| Deny | The agent does not run it. |
| Always allow | The agent runs it and keeps the rule shown under Always allow adds. It appears only when the agent offers a lasting rule, as Claude Code and the Qoder builds do. |
Questions
- Pick an option, or several where the card says Choose any.
- Write your own answer under Other.
- With several questions, Back and Next move between them, Skip leaves one unanswered, and Submit sends your answers.
Questions Claude asks in its desktop app reach the HUD too. Their answers go back through Agent HUD's plugin for Claude Code, in Settings → Agent plugins.
Plans
A Claude Code plan shows in full.
| Answer | What happens |
|---|---|
| Approve | Claude starts on the plan. |
| Approve, accept edits | Claude starts on the plan and accepts its file edits without asking. |
| Keep planning | Write what should change under Plan feedback and Send it. Claude keeps planning. |
Requests the HUD cannot answer
Some questions and plans can only be answered in the agent, such as another agent's plan. Their card says Answer in or Review this plan in the agent, and sometimes names a step that would let Agent HUD answer it, with a button such as Open Agent plugins. Dismiss puts the card away; the agent still asks in its own window.
Several requests
- Requests line up under Waiting, with their count. Each shows how long it has waited; click one to open it.
- A request stays until it is answered or goes back to the agent. It never closes by itself after a few seconds, as a reminder does.
- You can still answer in the agent's own window. When you answer in Claude Code, a Qoder build or DeepSeek Harness, the card leaves the HUD by itself.
- If an answer does not reach the agent, the card says so. Check the agent's own window then.
If nobody answers
A request waits on the HUD for the time set in Settings → General → Wait for an answer: 1, 3, 5, 10, 30 or 60 minutes, 10 by default. 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.
Which agents send requests
| Agent | Tool calls | Questions | Plans |
|---|---|---|---|
| Claude Code | ✓ | ✓ | ✓ |
| Codex | ✓ | ✓ | |
| DeepSeek Harness | ✓ | ✓ | |
| Antigravity | ✓ | ✓ | |
| ZCode | ✓ | ✓ | |
| CodeBuddy, WorkBuddy | ✓ | ||
| Qwen Code | ✓ | ||
| Devin CLI | ✓ | ||
| Qoder, Qoder CN, QoderWork | ✓ |
- Codex runs Agent HUD's hook only after you trust it in Codex, and sends only the turns that ask for your review. Requests Codex's automatic reviewer handles stay in Codex. The Codex app's own questions and approvals come from the app itself.
- DeepSeek Harness sends its requests through Agent HUD's plugin for Harness, added in Settings → Agent plugins.
What Agent HUD writes into each agent's settings, and what turning client hooks off changes: Client hooks.
Away from your Mac
With Agent HUD Remote, the same tool calls, questions and plans also reach your iPhone and Apple Watch. See Remote.
Last updated