You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Rich async decision cards for every provider: pictures, prototypes and external actions
#40236
T3's async question card (Codex's request_user_input_async) is close to what I want for decisions an agent can't make on its own. Two gaps keep me running a separate tool beside T3 for them:
No rich visual options inside the card. Codex's async adapter only accepts text options, and while the shared question UI can render optional Markdown previews, options can't carry native images, before/after diffs or an interactive html_render prototype inside the card. Today the agent renders a page with html_render, then asks a separate question about it.
There's also a third kind of decision with no card at all: "go and confirm this somewhere else". For example, approve a change in a billing portal before it expires. The agent has no way to hand me that as a tracked item and hear back when I've done it.
Rich options. Each option can carry an image, a before/after pair or an html_render page, shown inside the card. Files the agent attaches open beside it.
External action cards. A card with a link, the exact click ("Open and confirm in the portal"), an optional expiry, and Done / Not yet buttons. Done arrives as a turn so the agent can check the result at the source.
One native card type would cover every provider and retire the side tool. It also keeps decisions in the thread that needs them, where T3's pending indicators and notifications already work.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Problem
T3's async question card (Codex's
request_user_input_async) is close to what I want for decisions an agent can't make on its own. Two gaps keep me running a separate tool beside T3 for them:AskUserQuestion([Feature]: Async question tool for Claude threads, like Codex's request_user_input_async #33175), and Pi and ACP threads have no async card either.html_renderprototype inside the card. Today the agent renders a page withhtml_render, then asks a separate question about it.There's also a third kind of decision with no card at all: "go and confirm this somewhere else". For example, approve a change in a billing portal before it expires. The agent has no way to hand me that as a tracked item and hear back when I've done it.
Proposal
html_renderpage, shown inside the card. Files the agent attaches open beside it.Why
One native card type would cover every provider and retire the side tool. It also keeps decisions in the thread that needs them, where T3's pending indicators and notifications already work.
Related: #33175, #34445, #20049, #24914.
All reactions