Human handoffPro
A help chat where the bot steps aside for a human: a handover card lists what the agent will be told and how long people usually wait, then a teammate arrives and carries on, with a slim trail of each step.
oxyn add human-handoff- Assistant
- Transferring
- With a person
- Resolved
I was charged twice for my October invoice.
I can see two charges of $49 on November 1 for invoice INV-2291. Refunds need someone from billing, would you like me to bring in a person?
The preview stays free for everyone. Pro opens the code of every Pro component, screen, agent-app template, block and kit, plus the Pro CLI.
Rendered from Rust at build time · goes live when visible
When to use
- Hand a support chat from the AI assistant to a person without making the customer repeat themselves (Arc "Agent handoff"; slug human-handoff because agent-handoff is the agent-to-agent component).
When not to use
- Replays a multi-agent run on one clock: use Agent timeline instead.
- One model at a glance: use Model card instead.
- A small automation on a single rail: use AI workflow instead.
Installation
Human handoff is part of Oxyn Pro; the preview is free. Pro items install with the oxyn CLI once your licence is signed in; until then Pro members copy the code from this page.
oxyn add human-handoffUsage
The preview is free. Pro opens the code of every Pro component, screen and template.
Examples
Assistant
The assistant answers; Talk to a person hands over.
- Assistant
- Transferring
- With a person
- Resolved
I was charged twice for my October invoice.
I can see two charges of $49 on November 1 for invoice INV-2291. Refunds need someone from billing, would you like me to bring in a person?
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
Connected
The person has joined and taken over.
- Assistant
- Transferring
- With a person
- Resolved
I was charged twice for my October invoice.
I can see two charges of $49 on November 1 for invoice INV-2291. Refunds need someone from billing, would you like me to bring in a person?
Hi, I'm Mara. I've read the summary, I can see the duplicate charge and I'm refunding it now. It should be back on your card in 3 to 5 days.
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
Editable summary
Edit the summary before the transfer, with a queue place (Oxyn extra).
- Assistant
- Transferring
- With a person
- Resolved
I was charged twice for my October invoice.
I can see two charges of $49 on November 1 for invoice INV-2291. Refunds need someone from billing, would you like me to bring in a person?
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
Unavailable
Nobody online: try again or keep chatting.
- Assistant
- Unavailable
- With a person
- Resolved
I was charged twice for my October invoice.
I can see two charges of $49 on November 1 for invoice INV-2291. Refunds need someone from billing, would you like me to bring in a person?
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
API reference
HumanHandoff
| Prop | Type | Default | Description |
|---|---|---|---|
nowrequired | ClockMs | — | Host clock. |
scenario | String | "handoff" | `handoff` (starts with the assistant), `connected`, `unavailable` or `resolved`. |
edit_summary | bool | Default::default() | Let the reader edit the summary before transfer (Oxyn extra). |
timeline | bool | true | Show the stage timeline. |
Read from the Rust signature and doc comments.
Keyboard interactions
| Key | Action |
|---|---|
| Tab | Suggested replies, Talk to a person, Cancel transfer, the composer |
| Enter | Send a message |
| EnterorSpace | Activate a button |
Accessibility
- The thread is a log, so new messages are read in order; typing is announced as text, not only dots.
- The stage timeline is an ordered list with aria-current on the current stage.
- The unavailable card uses role alert; every action is said back politely.
- Assistant and person are told apart by name and placement, not colour alone.
From the spec
Messages are a log; stage changes are announced; buttons say what they do (Talk to a person, Cancel, Keep chatting). Every action returns the line the polite live region announces. The focus outline shows only for keyboard focus.
Motion & interaction
A thin timeline marks each stage; the person's typing dots appear before their first message. The summary card can be edited before transfer.
Timing
Everything on screen is derived from the host clock now (no timers in the component), so playback, tests and the GPUI view agree.
| Transition | Duration | Easing |
|---|---|---|
| Transfer | 2600 ms (TRANSFER_MS) | — |
| Typing | 1400 ms (TYPING_MS) | — |
| Assistant reply delay | 600 ms (BOT_MS) | — |
Reduced motion: streamed text and moves appear at their end state; progress still advances, without travel animation.
Responsive behaviour
- The thread has a fixed 300 px height and scrolls inside (thin scrollbar).
- Under 480 px the stage timeline runs across the top instead of down the side.
- Messages wrap long words instead of overflowing.
Edge cases (spec)
Long summaries scroll; the stage timeline wraps labels under 390 px. Cancel transfer returns to the assistant. Checked at 1440, 768 and 390 px in light and dark with no text overlap. Chrome is monochrome grey; colour is semantic only (success, warning, danger, info) plus the providers' coloured brand marks.
Notes for AI
- Import
HumanHandofffromoxyn_dioxusand includeSTATUS_INDICATOR_CSSplus the token stylesheet once. - A GPUI version exists:
AiKitViewinoxyn_gpui. - Props to set first:
now. - It reads a clock (
now) for live timers; pass one clock for the whole page rather than one per component. - Keep its states and timings as they ship; restyle it through the CSS variables rather than by hand.