fix(desktop): wire MCP server for Claude Code agents - #6658
Conversation
6411422 to
61b3502
Compare
|
Rebased onto the latest No review comments on this PR. CI will verify the build and test gate. |
61b3502 to
77a237e
Compare
🔐 Codex Security Review
|
|
Rebased onto the latest Still-needed assessment: No upstream commits in the 62-commit window address the same issue. This PR remains needed. Review requests: |
77a237e to
2aa4708
Compare
|
Rebased onto current Still needed: Checked all 38 new upstream commits for overlap with this PR's topic. None of the upstream changes address the issue this PR fixes. The PR remains relevant. Verification:
|
2aa4708 to
2bda390
Compare
Rebase and review — 2026-09-03Base commit: Accuracy review: The bug is still present on main — Claude's entry in |
2bda390 to
3427a23
Compare
Rebase and review update — Sep 3, 2026Rebased onto latest main ( Accuracy review: Main does not wire an MCP server for Claude Code agents. The config bridge has test coverage for Mergeable status: Confirmed MERGEABLE on GitHub after force-push. |
Claude Code's entry in KNOWN_ACP_RUNTIMES had mcp_command: None, so
Desktop set BUZZ_ACP_MCP_COMMAND="" and the harness never spawned a
MCP server for Claude agents. Goose avoided this because it loads MCP
servers from its own config.yaml (supports_acp_native_config: true),
but Claude has no native config support — the only way it receives
MCP servers is through the session/new mcpServers field, which stays
empty when BUZZ_ACP_MCP_COMMAND is blank.
Set Claude's mcp_command to Some("buzz-dev-mcp"), matching Codex and
Buzz Agent. Added a test asserting Claude has the MCP command wired.
Closes block#6593
Co-authored-by: Brad Groux <brad@digitalmeld.com>
Signed-off-by: Brad Groux <brad@digitalmeld.com>
Signed-off-by: Brad Groux <bradgroux@hotmail.com>
Signed-off-by: Brad Groux <3053586+BradGroux@users.noreply.github.com>
3427a23 to
f8a5881
Compare
Rebase pass — Sep 5, 2025Rebased onto current upstream main ( Rebase resultConflict resolved in desktop/src-tauri/src/managed_agents/discovery.rs (upstream extracted KNOWN_ACP_RUNTIMES to catalog.rs submodule via #4625, PR's commit changed Claude's mcp_command from None to Some("buzz-dev-mcp") in the old inline array. Resolution dropped the PR's duplicate array definition — the fix applies in the extracted catalog.rs. The PR's test assertion was preserved. Note: upstream #4625 extracted the runtime catalog but kept Claude's mcp_command as None — this PR's fix is still needed. Still-needed assessmentChecked all 62 new main commits for overlap with this PR's topic. None obsoleted:
Verification
|
Summary
Claude Code agents get no MCP server from Buzz because the Claude entry in
KNOWN_ACP_RUNTIMEShasmcp_command: None. Desktop setsBUZZ_ACP_MCP_COMMAND="", and the harness'sbuild_mcp_serversreturns an empty list — the session/newmcpServersfield stays empty.Goose avoids this because it loads MCP servers from its own
config.yaml(supports_acp_native_config: true). Claude has no native config support — the only way it receives MCP servers is through the session/newmcpServersfield, which stays empty whenBUZZ_ACP_MCP_COMMANDis blank.Set Claude's
mcp_commandtoSome("buzz-dev-mcp"), matching Codex and Buzz Agent.Related issue
Closes #6593
Testing
New unit test
claude_has_mcp_commandinruntime/tests.rsasserts thatknown_acp_runtime("claude-agent-acp")resolves withmcp_command: Some("buzz-dev-mcp"). The existingcodex_has_mcp_commandandgoose_has_no_mcp_hookstests are unchanged, confirming Goose still uses its native config path and Codex still has its MCP command.Cannot run the full
cargo testsuite from this host (no Rust toolchain). The build and test gate will be verified on CI.