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
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.
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
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
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?
This page is the canonical destination for these components. All ship in the single Kansho pack.
components/control-plane/stuck-needs-input-card.tsxcomponents/control-plane/stuck-needs-input-card.tsxExplains why an agent is blocked and offers concrete answer choices or a thread handoff.
Use when a run cannot proceed without a human decision or more context.
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.
Reasons are needs-input, blocked, permission, tool-failure, and ambiguous; options, context, mission, wait time, and thread action are optional.
StuckNeedsInputCard accepts id, reason, question, context, options, agent, mission, waitedFor, staticPreview, onAnswer, onOpenThread, and className.
Direct imports are React, Lucide icons, AgentDot, Button, ApprovalActions, and cn.
Reason, question, context, options, and wait time are visible text; answer choices are native buttons and static-preview choices are disabled.
It does not submit answers, resume a run, open a thread, enforce permissions, or show pending/error feedback after host callbacks.
Source: components/control-plane/stuck-needs-input-card.tsx.
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.