Repository navigation
0.14.1 — install no longer writes a config block that breaks Codex - #13
Merged
Merged
Conversation
0.14.0 wrote an [approval_policy.granular] table with only mcp_elicitations, but that table requires several fields (sandbox_approval, rules, ...) and an incomplete one makes Codex v0.154 fail at config-load — the developer's Codex would not start. install now writes ONLY [mcp_servers.pythia]; elicitations surface under the default interactive approval policy, and the developer's approval policy is theirs to set. Verified against live Codex v0.154: the server connects, the pythia_approve elicitation renders its card with Approve/Reject, and Approve mints a grant (approver=mcp). requirements.toml is no longer written either — the danger-full-access pin became a printed warning, because that file is enterprise-managed and its schema is version-fragile in the same way that just broke config.toml. The server is fail-closed regardless. The pythia_approve success message now tells the agent to run apply --confirm itself on the file it previewed, instead of reading like a command for the developer to type by hand. 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.0's
pythia installwrote a config block that breaks Codex v0.154 at config-load — found the first time 0.14.0 was installed against a real Codex (Error loading config.toml: missing field sandbox_approval in approval_policy). This unbreaks it.Root cause
install wrote:
But on current Codex the
granularapproval policy is a table requiring several fields (sandbox_approval,rules,request_permissions, …). An incomplete one fails config-load, so the developer's Codex would not start at all.Fix
[mcp_servers.pythia]. MCP elicitations surface under Codex's default interactive approval policy without any granular table, and the approval policy is the developer's to set — not pythia's.config.toml. The MCP approver is fail-closed regardless, and the elicitation asks for an explicit Approve.pythia_approvesuccess message now tells the agent to runapply --confirmitself on the file it previewed, instead of handing the developer a command to type.Verified against live Codex v0.154
The rest of 0.14.0 is confirmed working end to end on a real Codex with this fix applied by hand first:
/mcpshowspythia: connected (1 tool); callingpythia_approverenders the elicitation card with Approve/Reject; Approve mints a real grant (.pythia/grants/<token>.json,approver="mcp", unspent). Theelicitation/createmethod name matches — no code change needed there.All suites green locally (phase1/2/3/5 + mcp + install);
test_mcp.pyruns in CI.🤖 Generated with Claude Code