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
Start an Antigravity thread whose start input carries a per-session processEnvironment (for example T3CODE_THREAD_ID).
Read that variable in a stdio MCP server or tool started by agy.
Expected behavior
The per-session environment reaches the agy process, as it does for the Kiro provider (packages/provider-kiro/src/server/adapter.ts around lines 542-546).
Actual behavior
AntigravityDriver.ts (around lines 275-282 at v0.1.10) builds the spawn environment from the instance-level environment only. input.processEnvironment arrives through ...input and is then ignored. agy 1.5.12 forwards T3CODE_THREAD_ID to stdio MCP servers when it is set, so the value is lost only in T3.
Related, same provider: the t3-code MCP server is added to every ACP session (provider-acp/src/server/adapter.ts around lines 916-933) and cannot be turned off per instance, and disabledTools is sent only for agy 1.4.2 to 1.4.5, so tools such as swarm and schedule cannot be restricted on 1.5.x.
Impact
MCP servers cannot scope calls to a thread on Antigravity, and an instance cannot be limited to a fixed tool set.
Activity
juliusmarminge commentedon Nov 19, 2026
This is the same problem as #36495, so I'm closing it in favour of that one. If it is different, say how and it will be reopened.