Repository navigation
docs(messaging): document Claude Code MCP setup and reply checks - #8949
Conversation
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
|
✅ Deterministic PR hygiene checks passed. |
✅ READY
Review readiness checklist
✅ 4/4 boxes ticked. This pull request has been marked Ready for Review. Hygiene✅ Deterministic PR hygiene checks passed. |
eee57c7 to
25c14a6
Compare
|
@coderabbitai review |
Action performed
|
|
Maintainer integration into
This is maintainer integration, not an independent approval. |
Restore parity with #8949: the Spanish messaging reference carries the same claude mcp add example and external link as English, so the Spanish localization test passes again.
…#9028) * docs(structure): keep error-detail.md within its line budget Join the sentence added by #8980 onto the preceding line of its paragraph; the rendered text is unchanged and the doc returns to 600 lines. * docs(es): translate the Claude Code MCP round-trip section Restore parity with #8949: the Spanish messaging reference carries the same claude mcp add example and external link as English, so the Spanish localization test passes again.
Summary
The messaging reference shows an MCP server entry but leaves readers to figure out where to put it and how to tell whether Codex answered. Document workspace-scoped registration for the Claude Code CLI and the local Code tab in Claude Desktop. Walk through opening an idle Codex test conversation, submitting one message, and using the same receipt to check the final reply without re-sending on timeout or an uncertain result.
Link the Spanish and Turkish references to the walkthrough. The Desktop Chat surface uses separate configuration; this walkthrough covers the CLI and Code tab. Documentation only; the existing tool and permission behavior is unchanged. Follow-up to #7999, #8053, and #8090.
Verification
25c14a68frebased onto upstreamdevd61cca122. The three-file docs patch is unchanged (git range-diff). Revalidated on macOS with Bun 1.4.4.cd docs-site && bun install --frozen-lockfile && bun run build: passed, 820 pages and 126,235 internal links checked.bun test tests/cli/cli-message-mcp.test.ts tests/codex-integration/messaging-mcp-wait.test.ts: 29 passed, 0 failed.bun run typecheck(2,681 files),bun run privacy:scan,bun run structure:check, andgit diff --check origin/dev...HEADpassed.ocx help message mcpshowed the documented flags; the documentedclaude mcp add --scope localinvocation followed byclaude mcp get opencodex-queuereturned Connected in a temporary Claude config. Direct stdio MCPtools/listreturned exactly two default tools and four with--allow-reply-read.c320932c1with Codex CLI 0.166.0 and disposable homes. Each sent once, used the same receipt, and observed the expected stored final answer. The Desktop Chat surface was outside those runs.codex_wait_replyusing the same receipt, and the Codex history contained the correlated input and final text in one completed turn. Desktop Code was verified on merged dev as noted above.25c14a68f. The fork-triggered GitHub CI run returnedaction_requiredbefore any job ran; hosted test results are still pending maintainer approval.Checklist
Review readiness checklist
Summary by CodeRabbit