Kanshō/Stuck / needs-input card

Stuck / needs-input card

A focused card that surfaces when an agent has hit a question only the operator can answer. Distinct from paused: the agent is alive, waiting, and has a concrete decision to offer.

Included in the single kansho full pack. Components are not offered as separate installs.

Needs input — with answer choices

Needs inputSI-118M-2014 · Compact audit log payloads above 4KBwaiting 3m 48s
Plan & dispatchclaude-opus-4-7

Staging row delta is 0.83% — above the 0.5% drift threshold. Should I cut over to production anyway, abort, or hold for review?

psql: SELECT COUNT(*) FROM audit.chunks → 144,019 / src expected 145,225

Demo answer: waiting

Blocked — tool failure

Tool failureSI-119M-2011 · Coalesce alertswaiting 38s
Slack notifierclaude-haiku-4-5

Slack chat.postMessage returned 503 on three consecutive retries. I'm pausing notifications. Retry, queue locally, or abandon?

slack.com/api/chat.postMessage → 503 Service Unavailable (x3)

Demo answer: waiting

Ambiguous request — no options

AmbiguousSI-120
Audit writerclaude-sonnet-4-6

The postmortem template references both 'incident commander' and 'oncall lead' — should I treat these as the same role for INC-218, or as distinct fields?

Included components

This page is the canonical destination for these components. All ship in the single Kansho pack.

Stuck needs input card

components/control-plane/stuck-needs-input-card.tsx

Component documentation

Stuck needs input card

components/control-plane/stuck-needs-input-card.tsx

Purpose

Explains why an agent is blocked and offers concrete answer choices or a thread handoff.

Appropriate use

Use when a run cannot proceed without a human decision or more context.

Example

components/control-plane/stuck-needs-input-card.tsx has a representative live example in the "Needs input — with answer choices" section on /components/stuck-needs-input.

States

Reasons are needs-input, blocked, permission, tool-failure, and ambiguous; options, context, mission, wait time, and thread action are optional.

API and props

StuckNeedsInputCard accepts id, reason, question, context, options, agent, mission, waitedFor, staticPreview, onAnswer, onOpenThread, and className.

Dependencies

Direct imports are React, Lucide icons, AgentDot, Button, ApprovalActions, and cn.

Accessibility

Reason, question, context, options, and wait time are visible text; answer choices are native buttons and static-preview choices are disabled.

Limitations

It does not submit answers, resume a run, open a thread, enforce permissions, or show pending/error feedback after host callbacks.

Source

Source: components/control-plane/stuck-needs-input-card.tsx.

Full pack

components/control-plane/stuck-needs-input-card.tsx is documented at /components/stuck-needs-input and installs only through the single Kansho full pack; no individual component install is offered.