Headless Interrupts
Resolve agent interrupts from any UI, without a useInterrupt render slot.
What is this?
Sometimes the agent's question belongs outside the chat, in a dashboard, a side panel, or a modal. A headless interrupt lets any component show the question and resume the run with the answer. No chat needs to be mounted.
This page shows how to resolve an interrupt without the chat. You build the
resolver from the same hooks that useInterrupt uses. It can be a button
grid, a form, a modal, or a keyboard shortcut.
For promise-based agent frameworks there is no native interrupt primitive,
so the headless variant uses useFrontendTool with a Promise-based
handler. The handler exposes its pending payload via React state, so
a separate "app surface" can render the picker outside the chat. It
resolves the Promise once the user interacts. Same UX, different
mechanism.
When should I use this?
- Testing / Playwright fixtures: a deterministic, chat-less button grid is easier to drive than a chat surface where the picker only appears after an LLM call.
- Non-chat UIs: dashboards, side panels, inspector surfaces, or any place where you want the agent's interrupt without the chat transcript.
- Custom flow control: when you need to know exactly when the interrupt arrived (e.g. to gate other UI) and when it was resolved.
- Research / debugging: when you want to observe the raw AG-UI custom events without the abstraction layer.
If you just want "a picker in chat", just use
useInterrupt. For pauses that the model decides on, use
useHumanInTheLoop.
The primitives
The render callback intentionally returns null. The picker UI lives
in the app surface, not in the chat transcript. The handler's pending
state drives whether the picker is shown:
Missing snippet
headless-promise-primitives not found in claude-sdk-typescript::interrupt-headless. Tag the source lines with // @region[headless-promise-primitives] / // @endregion[headless-promise-primitives].Available: headless-useinterrupt-primitives, frontend-tools-setup, a2ui-backend-tool, agent-context-setup, a2ui-fixed-schema-tool-execution, shared-state-set-notes-handler, backend-tool-execution, claude-agent-sdk-agent-loop-dispatch, state-streaming-delta-emission, shared-state-read-write-route, shared-state-streaming-route, a2ui-fixed-schema-routeA few things this pattern is careful about:
- The handler stages its
resolvecallback in a ref keyed by tool-call id, so concurrent tool calls don't trample each other's resolvers. setPendingis called from inside the handler so the app surface re-renders the picker as soon as the agent calls the tool, and again withnullafter the user interacts so the picker disappears.render: () => nullkeeps the chat transcript clean. The headless variant deliberately bypasses inline rendering.
How is this guide?