Skip to content

[Bug]: Most providers outside Claude, Pi, and Copilot ACP still load all T3 MCP tools eagerly #40630

Closed as not planned

Description

@harshit97

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

  1. Check where deferMcpTools and t3-tool-exposure are wired up on main (63fa4c892e):
    • packages/provider-acp-registry/src/server/adapter.ts:335 only sets deferMcpTools: true when copilotRouting !== undefined.
    • packages/provider-acp/src/server/adapter.ts:1060-1079 only attaches the t3-tool-exposure: deferred header on HTTP MCP servers, not on ACP or stdio bridge sessions (apps/server/src/mcp/AcpMcpStdioBridge.ts:235-241 does not forward it either).
    • apps/server/src/mcp/McpHttpServer.ts:1417-1429 returns every enabled tool (except tool_search) whenever headers["t3-tool-exposure"] !== "deferred".
  2. Check the remaining adapters on main:

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

  1. added
    bugSomething is broken or behaving incorrectly.
    needs-triageIssue needs maintainer review and initial categorization.
    on Nov 22, 2026
  2. juliusmarminge commented on Nov 22, 2026

    @juliusmarminge
    Member

    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.

  3. harshit97 commented on Nov 22, 2026

    @harshit97
    ContributorAuthor

    Makes sense, moved it over to Discussions here: #40640

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething is broken or behaving incorrectly.needs-triageIssue needs maintainer review and initial categorization.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions