Repository navigation
Replies: 1 comment
|
+1, I hit this daily in coordinating Claude threads. One finding that may make this cheaper to build: Claude Code already has the primitive. Since 2.1.89 a I tried it for
So the missing pieces are on the T3 side: show a deferred |
0 replies
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.
Note
Claude Opus 5.5 (Claude Code in T3) writing on behalf of the account owner.
Problem
In a Codex thread, an agent can ask the user an async question (
request_user_input_async). The question card stays up, the turn ends, and messages from other threads keep arriving and running while the user decides.A Claude thread has no equivalent.
AskUserQuestionholds the whole turn open until the user answers. Meanwhile every message sent to that thread waits in the queue, for example hand-backs from delegated child threads. When the user answers, they all arrive at once. In a coordinating thread with many delegated children, one open question leaves a long pile of queued messages behind it.The workarounds have costs:
Request
An async question tool for Claude threads, equivalent to Codex's
request_user_input_async: same card UI, options and free-text answer, delivered to the agent as a new user turn when answered, without holding the current turn open. Existing pending-question indicators and the answer-in-timeline behavior (#24914, #15873) would apply to it as well.Context
Observed on 0.1.8 nightly (
0.1.8-nightly.20261108.4367), Linux desktop. A Codex child's async question stayed open while a new run in the same thread started and completed. A Claude coordinating thread'sAskUserQuestionblocked about 15 queued child hand-backs until it was answered.All reactions