Repository navigation
Use step environments for MCP file uploads - #35878
Merged
copyberry[bot] merged 1 commit intoJul 29, 2026
Merged
copyberry[bot] merged 1 commit into
copyberry[bot] merged 1 commit into
Conversation
## Why An MCP tool call can run after its selected environment becomes ready, while the turn context still contains the earlier starting-state snapshot. File argument rewriting must use the environment available to the current step so it can resolve and upload local files in that case. ## What changed - Pass `StepContext` through MCP file argument rewriting. - Resolve the primary environment from the step snapshot while retaining turn-scoped configuration and metadata. - Add coverage for an environment that transitions from starting to ready during a turn. GitOrigin-RevId: 935bea18ee425aabeacf4505eaff90565f9751e9
copyberry
Bot
force-pushed
the
copyberry/codex-internal-to-codex-oss/935bea18ee425aabeacf4505eaff90565f9751e9
branch
from
July 29, 2026 03:11
33757b0 to
250de82
Compare
copyberry
Bot
deleted the
copyberry/codex-internal-to-codex-oss/935bea18ee425aabeacf4505eaff90565f9751e9
branch
July 29, 2026 03:12
LanCheDeB612
temporarily deployed
to
issue-triage
July 29, 2026 03:44 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
LanCheDeB612
temporarily deployed
to
issue-triage
July 29, 2026 03:44 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
LanCheDeB612
temporarily deployed
to
issue-triage
July 29, 2026 03:44 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
jsfyq917-crypto
temporarily deployed
to
issue-triage
July 29, 2026 03:49 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
jsfyq917-crypto
temporarily deployed
to
issue-triage
July 29, 2026 03:49 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
jsfyq917-crypto
temporarily deployed
to
issue-triage
July 29, 2026 03:49 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
jsfyq917-crypto
temporarily deployed
to
issue-triage
July 29, 2026 03:50 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
This branch was previously 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.
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.
Use step environments for MCP file uploads
Why
An MCP tool call can run after its selected environment becomes ready, while the
turn context still contains the earlier starting-state snapshot. File argument
rewriting must use the environment available to the current step so it can
resolve and upload local files in that case.
What changed
StepContextthrough MCP file argument rewriting.turn-scoped configuration and metadata.
during a turn.