[codex] Publish Codeck v0.4.4 with Gemini 3.8 - #5
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5ea1207d3a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| let run; | ||
| try { | ||
| run = await routeTask(input, { caller: 'mcp', allowOverBudget: Boolean(fullContext) }); | ||
| run = await routeTask(input, { cwd, caller: 'mcp', allowOverBudget: Boolean(fullContext) }); |
There was a problem hiding this comment.
When one long-lived MCP server routes project A and then project B, passing each requested cwd into routeTask causes loadConfig to load both projects in the same process, but loadDotenv writes A's values into global process.env and refuses to overwrite existing keys (src/config.ts:339-360). Consequently, B's .env/.codeck/.env credentials are ignored and its API request can be sent using A's key, leaking credentials and billing across projects; load project-specific variables without mutating shared process state, or restore them after each call.
Useful? React with 👍 / 👎.
1 participant
What changed
This publishes the pending Codeck 0.4.4/plugin overhaul and updates the maintained Google/Agy default to
gemini-3.8-flash-high.projectPathand a user-named executor, while adding focused host briefs and an opt-in repository context boundary.--modelwith plan/sandbox read-only execution and inline task context.User impact and root cause
The previous package assumed a shared process working directory, allowed MCP calls to rely on implicit routing, and used a file-backed Agy context handoff that could require an extra file-read grant. That made Codex/plugin calls fragile across projects and blurred the boundary between a named external specialist and automatic routing.
The fix moves the project path and executor identity into the MCP contract, validates every project-scoped file at the boundary, packages the selected context inline for Agy, and preserves Codex as the host and final decision-maker. The default Agy model now follows the locally available Gemini 3.8 model.
Validation
npm test— 17/17 passing.npm run test:gemini-image— passing.npm cion Node 22 — completed successfully.agy modelsconfirmedgemini-3.8-flash-highis available.git diff --checkpassed for source and non-bundled generated files.Known follow-up
npm audit --omit=devreports two existing production dependency advisories:qs(moderate) andsmol-toml(high). Dependency upgrades were intentionally not mixed into this release; they should be handled in a focused follow-up after compatibility review.