Repository navigation
0.14.2 — route the Codex agent to the pythia_approve tool - #14
Merged
Merged
Conversation
On Codex the agent ran `pythia apply`, printed the token, and stopped — the
preview's follow-up and the skill only named AskUserQuestion (Claude) and the
console, neither of which is the Codex door, so the agent never called the
pythia_approve MCP tool. Now the apply preview names the tool ("on Codex: the
agent calls the pythia_approve MCP tool with token ..."), the AGENTS.md
harness block says the approval door IS that tool and that the agent then runs
--confirm itself, and pythia-apply's step 3 says the same. The mechanism was
already proven on live Codex v0.154; this is the routing that gets the agent
to use it.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
0.14.1 shipped the working MCP approver, but a field test on live Codex v0.154 showed the agent running
pythia apply, printing the token, and stopping — it never called thepythia_approvetool. The preview follow-up and the pythia-apply skill only namedAskUserQuestion(Claude, absent on Codex) and the console, so nothing routed the Codex agent to its actual approval door.Fix (guidance/routing only — the mechanism was already proven)
pythia applypreview now prints an on Codex line naming thepythia_approveMCP tool with the token.pythia_approvetool, that the agent calls it after the preview, and that the agent then runsapply --confirmitself — not stop at the preview or hand the developer a command to type.Verified
On live Codex v0.154, after updating the AGENTS.md block: the agent calls
pythia_approveafter the preview, Codex prompts to allow the tool, and the developer gets the Approve select prompt. All suites green locally (phase1/2/3/5 + mcp + install).🤖 Generated with Claude Code