Support MCP form input in full-access user threads - #37864
Merged
copyberry[bot] merged 1 commit intoAug 10, 2026
Merged
Conversation
## Why Standard MCP forms can require user-entered values even when tool permissions are otherwise auto-approved in full-access sessions. ## What changed - Recognize the `openai/standard-form-input` client extension and surface non-approval forms in full-access, user-initiated root threads. - Keep approval forms, automation and subagent threads, headless sessions, and clients without the capability on their existing decline or review paths. - Treat the capability as client-only so it is not advertised to MCP servers, and enable it after session startup so required servers cannot block startup waiting for form input. ## Testing Add unit and app-server coverage for accepted form round trips, declined cases, approval metadata safeguards, resumed threads, and extension filtering. GitOrigin-RevId: 053bfe397a5c79eceef90a81d13e2aca6353af43
copyberry
Bot
force-pushed
the
copyberry/codex-internal-to-codex-oss/053bfe397a5c79eceef90a81d13e2aca6353af43
branch
from
August 10, 2026 18:20
a9de0e2 to
4b0e2a0
Compare
copyberry
Bot
deleted the
copyberry/codex-internal-to-codex-oss/053bfe397a5c79eceef90a81d13e2aca6353af43
branch
August 10, 2026 18:21
omarpinarecords
temporarily deployed
to
issue-triage
August 10, 2026 18:27 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
omarpinarecords
temporarily deployed
to
issue-triage
August 10, 2026 18:27 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
omarpinarecords
temporarily deployed
to
issue-triage
August 10, 2026 18:27 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Support MCP form input in full-access user threads
Why
Standard MCP forms can require user-entered values even when tool permissions are
otherwise auto-approved in full-access sessions.
What changed
openai/standard-form-inputclient extension and surfacenon-approval forms in full-access, user-initiated root threads.
clients without the capability on their existing decline or review paths.
and enable it after session startup so required servers cannot block startup
waiting for form input.
Testing
Add unit and app-server coverage for accepted form round trips, declined cases,
approval metadata safeguards, resumed threads, and extension filtering.