fix(harness-codex): improve Codex prompt framing and avoid placing relay shim file in session workdir - #16485
Merged
Merged
Conversation
felixarntz
marked this pull request as ready for review
June 29, 2026 20:00
lgrammel
approved these changes
Jun 30, 2026
Contributor
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.
Background
The Codex harness was formatting its custom instructions for the CLI relay shim inconsistently, using Markdown heading instead of
<tag>boundaries. It was also passing those instructions on every single turn rather than only on the very first turn, which was wasteful.And despite #16441, it was sometimes still stopping after a single turn. Chatting to the model, it explained that it should not have sent the message in the
finalchannel when it hadn't yet addressed the request. This underlying terminology probably makes sense to patch into the custom instructions for Codex.Additionally, it placed the CLI relay shim file in the session workdir, which was problematic if the session workdir was being used for actual work where that file could pollute the workspace (e.g. a git repo checkout).
Summary
.agent-runssession-specific infrastructure directory rather than the session workdir.Manual Verification
Run the
http://localhost:3000/harness/codex/*interactive examples.Checklist
pnpm changesetin the project root)