feat(cloud-codex): wire @commonlyai/mcp into codex CLI for kernel tools#388
Open
samxu01 wants to merge 1 commit into
Open
feat(cloud-codex): wire @commonlyai/mcp into codex CLI for kernel tools#388samxu01 wants to merge 1 commit into
samxu01 wants to merge 1 commit into
Conversation
…ernel tools Without an MCP server in codex's config.toml, Cody has no commonly_react_to_message / commonly_post_message_cap / commonly_open_dm tool — when Sam @-mentioned "react 👍", she posted "👍" as a literal message body instead of calling the reaction endpoint. Same for collaborative DMs and other CAP verbs. Install @commonlyai/mcp@0.1.1 globally in the init container alongside codex, then declare it as a stdio MCP server in /state/.codex/config.toml. The mcp binary picks up COMMONLY_AGENT_TOKEN + COMMONLY_API_URL from the container env (already wired). After this lands, Cody can react / post / open-dm via real kernel tool calls, and the autonomous-reaction acceptance test from Gap 4 covers production traffic (not just curl-direct smoke). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
samxu01
added a commit
that referenced
this pull request
May 16, 2026
…ls (#388) Install @commonlyai/mcp in init container, add [mcp_servers.commonly] stdio entry to config.toml. Gives Cody commonly_react_to_message and other kernel tools so she stops emitting emojis as message bodies. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
samxu01
added a commit
that referenced
this pull request
May 16, 2026
…MCP servers Verified empirically 2026-05-15 after merging #388: codex CLI 0.125.0 recognizes [mcp_servers.commonly] in config.toml (`codex mcp list` shows it enabled), but `codex exec` does NOT actually connect to or expose tools from configured MCP servers. The model's tool list stays limited to codex's built-in tools (web, image_gen, exec_command, apply_patch, ...). list_mcp_resources returns empty regardless. Per docs/MCP_INTEGRATION.md, the supported codex pattern is to wrap codex AS an MCP server (codex-as-mcp), not to have codex consume MCP servers. So #388 adds noise without effect. For Cody to actually call commonly_react_to_message autonomously, the real options are: - Switch her adapter from codex → claude-code or another MCP- consuming host (architectural decision). - Add the reaction tool to the openclaw extension's commonly_* block (separate Team-Commonly/openclaw PR; out of the "make-collab-bulletproof" goal's "no openclaw-coupled fixes" constraint). Keeping the four ship-PRs (#379/#380/#381/#382 + #383/#384/#385/#386 follow-ups) in place — they're all correct. Just removing #388. Co-Authored-By: Claude Opus 4.7 (1M context) <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.
Without an MCP server in codex's config.toml, Cody has no `commonly_react_to_message` / `commonly_post_message_cap` / `commonly_open_dm` tool. When Sam @-mentioned "react 👍", she posted "👍" as a literal message body instead of calling the reaction endpoint (verified live in dev pod, 2026-05-15).
This PR:
Test plan
🤖 Generated with Claude Code