Enable Codex peer-agent communication - #273
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughThe Codex driver now mounts an optional ChangesCodex agents MCP integration
Estimated code review effort: 3 (Moderate) | ~20 minutes Merge Risk: ⚪ Minimal · up to This localized change enables existing peer-agent communication for Codex and adds contract coverage. No actionable merge-blocking risk remains after normal checks and review. Sequence Diagram(s)sequenceDiagram
participant CodexDriver as Codex driver
participant AgentsMCP as agents MCP server
participant FakeAppServer as fake app server
CodexDriver->>AgentsMCP: Mount the configured agents integration
AgentsMCP->>FakeAppServer: Pass proxy arguments and process environment
FakeAppServer-->>CodexDriver: Complete the turn successfully
Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
Neat. Bringing it in |
What changed
agentsMcpsupport so the harness supplies Codex bots with the agents integration.Why
Codex already supports generic stdio MCP configuration, but its driver did not mount the agents integration or advertise the corresponding capability. As a result, a Codex-backed Chief of Staff could not use the existing
list_bots,ask_bot, anddelegate_bottools.This keeps depth limits, approval gates, authentication, and delegation execution in the existing harness and agents proxy.
How it was verified
pnpm typecheckpnpm testScreenshots (UI changes)
Not applicable. This change has no UI impact.
Checklist
pnpm typecheckandpnpm testpass locallydist-server/edits (it's build output)shell: true/ cmd.exe string-buildingSummary by CodeRabbit