Keep Codex user questions answerable - #4044
Open
maheen-ejaz wants to merge 2 commits into
Open
maheen-ejaz wants to merge 2 commits into
maheen-ejaz wants to merge 2 commits into
Conversation
maheen-ejaz
force-pushed
the
codex/askuserquestion-persistence
branch
from
September 22, 2026 02:45
5174967 to
db87310
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Human comments
What was wrong
Codex app-server item/tool/requestUserInput was not recognized by the Codex provider bridge, so Codex was forced onto the fallback plugin path. The durable pending-interaction lifecycle already supports thread-scoped questions, but native Codex requests could not reach it and stale submissions had no clear recovery action.
What changed
No daemon wire protocol fields changed.
How you verified
Fixes #