Repository navigation
Preserve tool metadata for OpenAI provider endpoint overrides - #48344
Merged
copyberry[bot] merged 1 commit intoSep 26, 2026
Conversation
## Why Destination-only filtering stripped raw tool result metadata and MCP attribution when the built-in OpenAI provider used a custom endpoint. ## What changed Add a runtime-only `include_internal_metadata` grant to `ModelProviderInfo` and enable it for the built-in OpenAI provider. Apply the provider grant or the existing first-party HTTPS destination check to both HTTP and WebSocket Responses requests. Keep the grant out of serialized configuration and schemas, and default it to false for providers received through remote configuration. Providers without the grant retain the existing destination filtering. ## Testing Update HTTP and WebSocket tests to expect metadata at overridden OpenAI endpoints. Cover provider grants, destination filtering, MCP attribution on requests, and the grant's exclusion from TOML serialization and configuration. GitOrigin-RevId: 53aad6fb4d52cdfa9c79c6d92fe87383e1d0d1ef
copyberry
Bot
force-pushed
the
copyberry/codex-internal-to-codex-oss/53aad6fb4d52cdfa9c79c6d92fe87383e1d0d1ef
branch
from
September 26, 2026 03:49
9464c7b to
c9e2520
Compare
Contributor
|
I have read the CLA Document and I hereby sign the CLA You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot. |
copyberry
Bot
deleted the
copyberry/codex-internal-to-codex-oss/53aad6fb4d52cdfa9c79c6d92fe87383e1d0d1ef
branch
September 26, 2026 03:49
junhyeokchoi-prothentia
deployed
to
issue-triage
September 26, 2026 04:06 — with 
GitHub Actions
Active
GitHub Actions
Active
junhyeokchoi-prothentia
deployed
to
issue-triage
September 26, 2026 04:06 — with
GitHub Actions
Active
GitHub Actions
Active
junhyeokchoi-prothentia
deployed
to
issue-triage
September 26, 2026 04:06 — with
GitHub Actions
Active
GitHub Actions
Active
junhyeokchoi-prothentia
deployed
to
issue-triage
September 26, 2026 04:07 — with
GitHub Actions
Active
GitHub Actions
Active
This branch was successfully 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
6 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.
Preserve tool metadata for OpenAI provider endpoint overrides
Why
Destination-only filtering stripped raw tool result metadata and MCP attribution when the built-in OpenAI provider used a custom endpoint.
What changed
Add a runtime-only
include_internal_metadatagrant toModelProviderInfoand enable it for the built-in OpenAI provider. Apply the provider grant or the existing first-party HTTPS destination check to both HTTP and WebSocket Responses requests.Keep the grant out of serialized configuration and schemas, and default it to false for providers received through remote configuration. Providers without the grant retain the existing destination filtering.
Testing
Update HTTP and WebSocket tests to expect metadata at overridden OpenAI endpoints. Cover provider grants, destination filtering, MCP attribution on requests, and the grant's exclusion from TOML serialization and configuration.