Repository navigation
Description
Before submitting
- 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
- Check where
deferMcpToolsandt3-tool-exposureare wired up onmain(63fa4c892e):packages/provider-acp-registry/src/server/adapter.ts:335only setsdeferMcpTools: truewhencopilotRouting !== undefined.packages/provider-acp/src/server/adapter.ts:1060-1079only attaches thet3-tool-exposure: deferredheader on HTTP MCP servers, not on ACP or stdio bridge sessions (apps/server/src/mcp/AcpMcpStdioBridge.ts:235-241does not forward it either).apps/server/src/mcp/McpHttpServer.ts:1417-1429returns every enabled tool (excepttool_search) wheneverheaders["t3-tool-exposure"] !== "deferred".
- Check the remaining adapters on
main:- ACP adapters without
deferMcpTools: Grok, Kiro,fx, Antigravity (apps/server/src/orchestration-v2/Adapters/AntigravityAdapterV2.ts:218-225, tracked in [Bug]: Antigravity ACP drops the 8 T3 MCP tools >1,280B (incl. delegate_task & t3_thread_launch) without call_mcp_tool or T3_ACP_MCP_NODE fallback #38123 and fix(antigravity): defer optional T3 MCP tools via tool_call proxy #39362), and all non-Copilot ACP Registry agents (Devin, Kimi, Droid, GLM, Mistral Vibe, Hermes,claude-acp, etc.). - Direct HTTP MCP adapters that never send
t3-tool-exposure: deferred: OpenCode v1/v2 (packages/provider-opencode/src/server/v2/adapter.ts:4405-4415), Cursor (packages/provider-cursor/src/server/adapter.ts:223), and Muse Code (packages/provider-muse/src/server/adapter.ts:1943).
- ACP adapters without
Expected behavior
Providers that do not defer MCP tools on their own should be able to use server-side deferral (t3-tool-exposure: deferred + tool_search, or a proxy fallback when a harness freezes its tool list per turn) instead of loading the entire t3-code tool catalog upfront on every turn.
Actual behavior
Only Claude (client-side ToolSearch), Pi (extension deferral), and Copilot ACP (#34245) defer T3's built-in MCP tools (plus Codex splitting t3-code and t3-code-direct). Every other ACP adapter, plus OpenCode, Cursor, and Muse Code, gets all ~75-90 t3-code tools loaded eagerly on every session.
That burns roughly 15k-25k tokens of context window before the conversation even starts (similar to what #34233 measured for Copilot before #34245), even on normal coding turns that never touch browser preview, device, scheduling, or PR guide tools. It is pretty annoying to pay that context tax on every turn when the server-side visibility gate from #34245 already exists, and the stdio/ACP bridges do not even forward t3-tool-exposure yet.
Antigravity is already covered by #38123 and #39362, so this is for the rest of the providers and the missing header forwarding in the stdio/ACP bridges.
Impact
Major degradation or frequent failure
Version or commit
0.1.11 / main @ 63fa4c8
Environment
macOS arm64, T3 Code (Beta) 0.1.11, checked against pingdotgg/t3code main (63fa4c892e)
Workaround
None if you still want T3's orchestration tools available on those providers.
Activity
juliusmarminge commentedon Nov 22, 2026
Thanks for writing this up. It asks for new behaviour rather than reporting a defect, so it does not belong in the bug tracker and I'm closing it as not planned here. Feature ideas are discussed in Discussions: please post it there.
harshit97 commentedon Nov 22, 2026
Makes sense, moved it over to Discussions here: #40640