Advertise MCP App UI support to Codex Apps#31435
Closed
martinauyeung-oai wants to merge 5 commits into
Closed
Conversation
Contributor
Author
|
duplicate |
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
1 participant
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.
Work hosts that can render MCP App WebViews now advertise the trusted io.modelcontextprotocol/ui capability during Codex Apps initialize and every codex_apps tools/call. The capability is parsed from app-server initialize, scoped to trusted widget-capable hosts, stripped/replaced when callers spoof reserved metadata, and carried request-scoped through turns, reviews, direct MCP calls, and realtime handoffs so mixed clients cannot cross-contaminate runtime selection. Tests cover parsing/spoof stripping, downstream metadata, runtime rebuild/isolation, and realtime routing.