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
{{ message }}
Repository navigation
[Bug]: Servers panel lists the Antigravity agent's own ports on every thread #38868
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
Start a thread with the Antigravity provider (agy 1.5.11) and send any message.
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:
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.
Activity
t3dotgg commentedon Nov 19, 2026
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.serverthat agy started. An agent launched through a wrapper process still lists its own ports.