mvp / three recipes

MVP / recipes

Choose the state you need.

Each recipe is a complete, copyable agentic moment. The HTML remains useful without JavaScript; the small host-owned script only demonstrates state changes in the docs.

3 recipespre-rendered + enhancedno external assets

Start with a complete flow

Use the starter for a broad first screen. Use a focused recipe when you need to model one state family precisely.

01chat streamingShow a response moving from running to success, error, or cancellation without losing the conversation.J-F4 02tool approvalExpose exact arguments, an immutable action ID, and a human decision before the host executes anything.J-F4 03question resumePause a plan for one native answer, then make the resumed state explicit and auditable.J-F1 ↗complete runSee all three moments composed in one release-notes flow with a decision panel.OVERVIEW

The recipe rule

State stays local to the object it describes.

Streaming belongs to the message, tool status belongs to the tool call, and approval belongs to the immutable action. A host can replace the demo script with server-rendered HTML or its own event layer.

Compose before inventing

Judgement pause = approval-gate + ask-user-question.

Policy or support-style “paused for review” screens are compositions of existing primitives, documented on the tool approval recipe. Synthesis and verdict layouts compose thinking-steps, tool-call, and card. Message footers (copy, regenerate) are host button slots on chat-message.