[reason-machines]

Why

Command Code's documented stdio MCP and hook support provides a direct integration path. This adds Command Code as a connected Reason Network agent rather than instructions for a hosted MCP connection. The MCP docs and Hooks docs define the config locations and hook contracts used here.

What changed

• Register a user-scoped stdio server and the documented SessionStart, PostToolUse, and Stop hooks.
• Map Command Code client names and link its MCP server to the session registered by its hooks.
• Preserve unrelated MCP and hook settings, and remove only Reason Network's entries.

Scope

• Covers only the Command Code integration. The Linux desktop app and pt-BR translation remain out of scope.
• The Command Code CLI is not installed in this environment. Setup tests use a fake cmd executable, and behavioral tests run the actual Reason Network stdio server against documented client and hook payloads.
• No screenshots apply to this CLI and configuration change.

Blast Radius

The changes add a cmd path to agent registration, session identification, and hook output. The existing adapters remain unchanged and pass the same suite.

Verification

• cargo fmt --all --check with the isolated stable toolchain on PATH. Passed.
• cargo clippy --all-targets --locked -- -D warnings. Passed.
• cargo test --locked. 256 tests passed.
• cargo build --locked && TMPDIR=/tmp python3 tests/e2e/hooks.py. All 82 hook checks passed, including Command Code setup, removal, discovery, MCP session linking, Stop, and PostToolUse.
• python3 -m py_compile tests/e2e/hooks.py and git diff --check. Passed.
• Independent read-only review of the exact PR head: no blocking findings.

—
Feedback resolver

[svemyh]

Security review of 9fdb584: no new attack surface. Setup writes only Reason Network's entries into ~/.commandcode/{mcp,settings}.json, preserves the rest, hook command uses the existing shell_cmd quoting, and message delivery follows the Codex/Gemini adapter path. Non-blocking: on Unix, if Command Code's process comm is literally cmd, hook_agent_pid skips it as a shell and keys the session link to the terminal/tmux ancestor (two Command Code sessions there could swap mail); find_bin("cmd") is a generic name. Untested against the real CLI.