Question card

UsageCopy Anchor Link

import { QuestionCard } from '@commenda/pathfinder/question-card';

<QuestionCard
  key={request.id}
  title="Which entity should I set up first?"
  options={entities.map((entity) => ({ id: entity.id, label: entity.name }))}
  writeInConfig={{}}
  onSubmit={async (answer) => {
    const receipt = await saveAnswer(request.id, answer);
    return receipt.ok
      ? { status: 'accepted', recap: receipt.recap }
      : { status: 'failed', message: receipt.message };
  }}
  onDismiss={() => temporarilyHide(request.id)}
/>;

Multiple answersCopy Anchor Link

More options and searchCopy Anchor Link

Inline placementCopy Anchor Link

Failed submission and retryCopy Anchor Link

LoadingCopy Anchor Link

Reset restores the example. Simulate failure retains the card for retry; no backend request is made.

API referenceCopy Anchor Link

Shared request propsCopy Anchor Link

RequestHandler<T> returns { status: 'accepted', recap: ResponseRecapProps } or { status: 'failed', message: string }, directly or as a Promise. A thrown error shows a retry message and preserves the draft. The host persists accepted responses; the component displays the returned receipt. state={{ status: 'resolved', recap }} restores history. Use a stable request ID as the React key, and change the key when the request changes. External pending is a rendering state; authorization and idempotency remain server responsibilities.

REQUEST-01: Docked tray uses pearl100, a raised shadow, radius16 and a white radius10 inset with 16px padding. Header40, footer at least44; controls wrap on narrow screens.

REQUEST-02: The parent places the request 12px above Composer at the same width. Inline requests are flat and fill their message column. Escape only temporarily dismisses; no global listener is installed.

REQUEST-03: Reading content does not animate. Existing Button and Popover motion respects reduced motion. Pending retains the draft and exposes a polite status. Acceptance never precedes the host result.

Design rulesCopy Anchor Link

• QUESTION-01: Single pointer/Space/Enter or number activation submits; arrow keys only move selection. Multiple choices and written answers require Continue (Enter also submits written text outside IME composition).
• QUESTION-02: Up to four options remain inline. Five or more show the first three and More options; eight or more enable search. Selected overflow labels remain visible outside the popup. Only the selected number lead turns blue.
• QUESTION-03: Number shortcuts operate only inside this card, never inside text fields or the overflow dialog. They cannot approve an action. Escape dismisses the popup first, then the request on a subsequent Escape.
• QUESTION-04: Failures retain the answer, pending blocks duplicate submission, and acceptance renders the supplied ResponseRecap.

Use unique IDs rather than labels as values. Keep the option set stable for a request. RadioGroup primitives provide single-choice arrow navigation; Checkbox provides multiple-choice semantics. The overflow uses a Popover instead of an action-only Dropdown so choices retain radio/checkbox semantics.

Integration and accessibilityCopy Anchor Link

Buttons have explicit names and keyboard focus. No network transport or AI SDK provider is required. Requests, tool execution, permission checks, durable outcomes and composer coordination stay in the application. See AI content integration for migration mappings; application migration is outside this build.