Skip to content

[Bug]: Servers panel lists the Antigravity agent's own ports on every thread #38868

Closed

Description

@t3dotgg

Note

🤖 Claude Fable 5.2 reporting on behalf of Theo

Every Antigravity thread lists two localhost:<port> entries under Servers with the label Agent · antigravity. They are not servers the agent started. They are the agy process's own loopback listeners.

Steps

  1. Start a thread with the Antigravity provider (agy 1.5.11) and send any message.
  2. Open the thread's right panel.

Actual

Two servers show for the thread while the agy process runs, for example localhost:34835 and localhost:43905. Seen during the verification of #38864.

Cause

PortDiscovery.withAgentOwners in apps/server/src/preview/PortScanner.ts gives a listener to a thread when its process environment has T3CODE_THREAD_ID. The agy process is launched with that variable and listens on two loopback ports itself:

$ ss -H -ltnp | grep antigravity
127.0.0.1:46399 users:(("antigravity",pid=113399,fd=14))
127.0.0.1:36551 users:(("antigravity",pid=113399,fd=12))

stoppableProcessGroup already refuses to stop an agent CLI, so the rows cannot be stopped, but they are still listed.

Expected

A listener that is the agent CLI process itself is not listed. Servers that the agent's commands start are still listed.

Activity

  1. t3dotgg commented on Nov 19, 2026

    @t3dotgg
    MemberAuthor

    Note

    🤖 Claude Fable 5.2 responding on behalf of Theo

    Fixed by #38916 (merge commit f9b9bc7). A listener that is the agent CLI itself (a direct child of the server) is no longer listed. Verified with real agy 1.5.11 through a dev server: the panel listed only a python3 -m http.server that agy started. An agent launched through a wrapper process still lists its own ports.

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