fix(cloud-codex): bump codex 0.125→0.133 + correct MCP-surfacing docs (env-table-gated)#476
Merged
Conversation
Bumps cloud-codex (Cody) codex CLI default 0.125.0 -> 0.133.0 (agents.cloudCodex.codexVersion + the template default). 0.133 is the version verified end-to-end this session (model-request payload capture + a live two-tool shared-memory proof against the published @commonlyai/mcp). This is hygiene, not a fix: 0.125 already surfaced MCP tools in-cluster. Corrects the codex MCP-surfacing docs (CLAUDE.md + MCP_INTEGRATION.md), which PR #475 mis-framed as "codex 0.133 fixes a version gap." The real gate is the [mcp_servers.commonly] env table (PR #398) — codex doesn't pass parent env to the MCP subprocess it spawns, so the block must declare COMMONLY_API_URL + COMMONLY_AGENT_TOKEN or the server crashes at boot and the model sees no commonly_* tools. With it present, surfacing works on 0.116/0.125 (verified live 2026-05-17) and 0.133 (re-verified 2026-06-09). The 2026-05-16 "no tools on 0.125" finding was the pre-#398 env omission, mis-attributed to the codex version. Docs now say: check the env table first, not the version. 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.
Bump
cloud-codex (Cody) codex CLI default
0.125.0→0.133.0(agents.cloudCodex.codexVersion+ template default). 0.133 is the version verified end-to-end this session — model-request payload capture and a live two-tool shared-memory proof against the published@commonlyai/mcp. Hygiene, not a fix: 0.125 already surfaced MCP tools in-cluster.Doc correction (the important part)
PR #475 mis-framed codex MCP surfacing as "broken on 0.125, fixed in 0.133 — a version gap." That's wrong. The real gate is the
[mcp_servers.commonly]env table (PR #398): codex doesn't pass parent env to the MCP subprocess it spawns, so the block must declareCOMMONLY_API_URL+COMMONLY_AGENT_TOKENor the server crashes at boot and the model sees nocommonly_*tools.With the env table present (it is, in the cloud-codex template), surfacing works on 0.116/0.125 (verified live 2026-05-17, per the in-repo cloud-codex comments) and 0.133 (re-verified 2026-06-09 via payload capture). The 2026-05-16 "no tools on 0.125" finding was the pre-#398 env omission, mis-attributed to the codex version.
CLAUDE.md+MCP_INTEGRATION.mdnow say: if tools stop surfacing, check the env table first, not the version.Apply
The codex version is consumed by the cloud-codex init container at pod boot, so this lands when the cloud-codex deployment next rolls (Deploy Dev / helm upgrade). No urgency — Cody on 0.125 already works.
🤖 Generated with Claude Code