Skip to content

[Bug]: Antigravity driver drops per-session processEnvironment #39377

Closed as duplicate

Description

@zicochaos

Area

Antigravity provider

Steps to reproduce

  1. Start an Antigravity thread whose start input carries a per-session processEnvironment (for example T3CODE_THREAD_ID).
  2. 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.

Version or commit

v0.1.10 (7d32075e), agy 1.5.12.

Environment

Linux, t3 serve.

Activity

  1. juliusmarminge commented on Nov 19, 2026

    @juliusmarminge
    Member

    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.

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions