Agent Inbox

status='ready' — 7 requests, 4 of them waiting. Triage order is waiting before settled, urgency descending, then OLDEST first, so the 41-minute critical deploy leads and is flagged past the 30-minute stale line. Approve / Deny answer a row without leaving the queue; A and D do the same from the keyboard, arrows move between rows and into the buttons. Clicking a row opens the detail slot.

4 waiting1 over 30m

Denied

Approved

Expired

↑↓ move between requests · ←→ reach the quick actions · A approve · D deny

no callback fired yet

defaultGroupBy='agent' with density='compact' and no detail slot — the row is still a real button, it just hands the id to onOpen so your router can take over. billing-agent holds three of the seven requests and the group header counts how many of them still need a person; the header control regroups the same array without refetching anything.

By agent

4 waiting1 over 30m

release-bot1 of 1 waiting

code-review-agent1 of 1 waiting

billing-agent2 of 3 waiting

Expired

cleanup-agent0 of 1 waiting

Denied

ops-agent0 of 1 waiting

Approved

↑↓ move between requests · ←→ reach the quick actions · A approve · D deny

onOpen has not fired yet

The one-shot lock, shown by a consumer that never confirms: click Approve five times as fast as you can and the counter still reads 1. The question row below it offers no Approve at all — an empty yes sent back to an agent that asked which account to use is worse than making you open it — and with no onOpen or renderDetail wired it honestly shows nothing but its waiting state.

Awaiting confirmation

2 waiting1 over 30m

Ship hotfix 4.2.1 to productionrelease-botApprovalwaiting 41mCriticalThe rollback plan is a single command, but the diff touches checkout.Deploys 3 commits to prod and restarts 12 containers in eu-west-1.

Which Stripe account should the 14 refunds be issued from?billing-agentQuestion12mHighTwo accounts match Acme EU. The customer paid through the legacy one in 2024.

Waiting

↑↓ move between requests · ←→ reach the quick actions · A approve · D deny

onDecide fired 0 times

A write that fails. onDecide returns a promise that rejects after 900 ms, the way a 409 from your API would: the row reads 'Approving…', then rolls back to Approve / Deny, and the live region says the decision did not go through. The lock is cleared with it, so you can try again.

Write rejected

1 waiting1 over 30m

Ship hotfix 4.2.1 to productionrelease-botApprovalwaiting 41mCriticalThe rollback plan is a single command, but the diff touches checkout.Deploys 3 commits to prod and restarts 12 containers in eu-west-1.

↑↓ move between requests · ←→ reach the quick actions · A approve · D deny

no write has failed yet

Edge payloads in a read-only tile (showControls={false}): a 96-character ask, a 63-character MCP agent name with no spaces in it, a four-sentence preview and a request that has been waiting three days. wrap-anywhere + min-w-0 keep all of them inside the panel instead of widening it, and the impact line survives on the critical row.

Escalations

2 waiting2 over 30m

Answered

↑↓ move between requests · ←→ reach the quick actions · A approve · D deny

onOpen has not fired yet

status='loading' — the queue itself has not arrived. Skeleton rows, aria-busy and one sr-only status line; every pulse stops under prefers-reduced-motion.

status='empty' — nothing is parked on you. The copy says what will land here instead of just 'no data'.

Nothing is waiting for you

Your agents will park approvals, questions and reviews here when they need a person.

status='error' — the queue failed to load, which is NOT a request being denied. role='alert', a retry, and a line that says the requests are still queued agent-side so nobody assumes they were answered. Pressing retry swaps in the ready payload.

This inbox failed to load

The inbox stream closed before the queue arrived. request-id: 7f2c-9ad1

Requests are still queued on the agent side — nothing here was approved or denied.