Repository navigation
Retain and revise asynchronous human questions until explicitly resolved #34445
park9140-glowforge
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
T3 already renders native asynchronous user questions. A pending human decision can outlive the agent run that asked it. I propose preserving those message-backed questions until answered or explicitly cancelled, and allowing the asking thread to amend the same card with an expected revision.
An amendment would atomically change the text and increment its revision. Stale answers would be rejected. Reconnection would retain the same pending request. Command approvals, permission modes, secrets and provider callbacks would keep their existing contracts. An answered request would remain distinct from completion of the requested operation.
A local prototype reuses the existing native question cards, event/projection store and restart recovery. New version-one questions accept legacy answers without a revision; amended questions require their current revision. Pending questions block settlement and remain pending when a delegated task is cancelled. A later answer can start another child run.
Focused backend and client checks passed, including a real Chromium card/hook fixture, desktop and narrow-web captures, and a temporary SQLite close/reopen retaining a legacy pending request. No real-provider paid eval, native mobile, installed-app upgrade or full old/new server RPC qualification has been performed. Nothing has been published or deployed.
Would maintainers support this behavior and bounded direction before any upstream implementation PR is proposed? If so, which lifecycle or compatibility constraints should the contribution preserve?
All reactions