You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Command Code ACP threads get no T3 MCP tools on Windows (stdio bridge exits with code 1) #34010
I searched existing issues and did not find a duplicate.
I included enough detail to reproduce or investigate the problem.
Area
apps/server
Steps to reproduce
On Windows, add Command Code as an ACP provider using a local command (node .../command-code/dist/index.mjs acp, or the cmdc binary).
Start a thread on that provider.
Ask it to use any T3 tool, or inspect its tool list at session start.
Expected behavior
The agent has T3's MCP tools (t3_thread_list, link_pull_request, ...) available for the whole thread.
Actual behavior
No T3 MCP tools reach the agent. Only the acp-mcp-call terminal fallback works, so the agent shells out for every T3 tool. The agent's stderr reports:
[acp] mcp t3-code (editor): error, MCP server exited with code 1
Running the same bridge command directly shows why:
'C:\Users\<user>\AppData\Local\Programs\t3code\T3' is not recognized as an internal or external command
Diagnosis
T3 injects the stdio bridge as { name: "t3-code", command: <T3 executable>, args: [<entrypoint>, "acp-mcp-bridge"], env: [...] }, where command is .../t3code/T3 Code (Beta).exe.
Command Code builds stdio MCP clients with shell: "win32" === process.platform, so Node hands the command line to cmd.exe, which splits the unquoted path at the space in T3 Code (Beta).exe and exits with code 1.
Verified against the shipped Command Code ACP agent (1.88.2): the same spawn with shell: false starts and stays alive; with shell: true it exits with code 1.
Command Code does handle ACP HTTP MCP servers correctly: it advertises mcpCapabilities.http: true, and when the same endpoint was offered as { type: "http", url, headers } it connected with all 71 tools ([acp] mcp t3-code (editor): 71 tools).
mcpOverHttp is already the per-flavor opt-in for this situation (codex-acp 1.2.0 and pi-acp drop injected HTTP servers, so it cannot be enabled for every agent), but today only Copilot sets it.
Command Code 1.88.2 (T3-managed install under ~/.t3/bin/cmdcode)
Additional context
Fix proposed in #34004: detect local Command Code installs in provider-acp-registry and set mcpOverHttp for them, so the session is created with the HTTP MCP server instead of the stdio bridge.
Activity