Antigravity Link is a VS Code extension for Google Antigravity IDE, positioned as a mobile companion. When users need to leave their computer but still want to keep following an AI session that is being generated, they can scan a QR code to turn their mobile browser into a real-time mirror of the current chat window, completing reading and interaction within the local network.
Main capabilities
- Real-time mirroring of the current Antigravity chat: read streaming output and interact with it on your phone.
- Upload files to the current Antigravity chat.
- Mobile voice-to-text input (HTTPS is required to obtain microphone permission).
- Stop generation from your phone via a dedicated stop button.
- Support for switching the active instance between multiple Antigravity windows.
- Provides a local HTTP API for automation and integration.
- Provides an MCP server for integration with AI assistants, with 9 built-in MCP tools.
- A local-only server with token authentication.
- The interface supports 16 languages, with automatic detection and support for RTL (right-to-left) rendering.
How to use Installation: Search for "Antigravity Link" in the Antigravity extension marketplace, or install it directly from Open VSX. Requirements: Antigravity IDE is installed and running; the phone and computer are on the same Wi-Fi network; Antigravity must be launched with the remote debugging flag, otherwise the extension cannot discover and connect to sessions; multiple Antigravity sessions all need to be launched with this command. Quick start: In VS Code, run "Antigravity Link: Start Server", then run "Antigravity Link: Show QR Code", and scan the QR code with your phone to open the mobile interface. Because a self-signed certificate is used, the phone may warn that the connection is not secure; this is expected behavior for local HTTPS, and you can continue accessing it through options such as "Advanced" in the browser. Automation integration: Start the extension server and copy the token from the QR code URL (?token=...), then use MCP tools (mcp-server.mjs) or directly access the https://localhost:3000 Initiate HTTP calls; you can use /snapshot, /send, and /stop to verify the control flow. The project also provides an OpenAPI example and an MCP client configuration example.
How it works (high level) The extension starts a local server (HTTP or HTTPS); discovers Antigravity targets through the Chrome DevTools Protocol (CDP); the phone connects to the mobile UI and sends upload/command requests; the extension injects into the selected chat target and saves files to the uploads/ directory. The extension connects to the debugging port exposed by Antigravity on the local machine, which is the same CDP protocol used by VS Code's built-in debugger and browser developer tools. It reads the local UI and simulates keystrokes and clicks, as if the user were sitting at the keyboard operating it.
Security and privacy All network activity is local: the extension only communicates with the phone on the local network (through the HTTPS server it starts), the Antigravity IDE CDP port on localhost:9000, and the Antigravity language server process on 127.0.0.1 (used for RPC to stop generation). Apart from data sent by Antigravity itself, no data is sent to Google servers or any external service. The extension does not inject into Antigravity's network traffic, does not intercept or modify API calls; it does not modify any Antigravity files, with no patches, hooks, or binary changes; the server runs entirely on the local machine. Unless the user actively exposes the server externally, prompts, chat history, and files will not leave the local network; the extension does not send data to third-party services. The source code is under the MIT license and is fully auditable.
Local HTTP API The extension provides a local https://localhost:3000(或用户配置的端口)暴露本地 HTTP API. Except for /ping, all endpoints require an Authorization: Bearer <token> header. The token is the value after ?token= in the QR code URL. See openapi.yaml for the full schema.
MCP server Antigravity Link comes with an MCP (Model Context Protocol) server that lets AI assistants directly drive Antigravity sessions. The corresponding configuration must be added to the MCP client configuration (such as claude_desktop_config.json); the token is likewise taken from the value after ?token= in the QR code URL. Before the MCP client connects, the extension server must already be running. The materials list a total of 9 available tools.
Use cases
- Continue viewing and controlling Antigravity's AI sessions on your phone when away from your workstation.
- Upload files, use voice input, or stop generation from mobile.
- Switch between multiple Antigravity windows.
- Implement automated integration through the local HTTP API or MCP server, letting agents or external tools drive sessions programmatically.
Limitations and notes
- By default, access is limited to the local network only; for remote access, exposure is required through a tunnel such as ngrok or wireguard, with token authentication and HTTPS remaining unchanged.
- Antigravity must be started with the remote debugging flag, otherwise it cannot be discovered.
- A self-signed certificate will trigger a browser warning; this is expected.
- If an uploaded file is saved but does not appear in the chat, you need to switch to the correct active instance in the mobile UI.
- Being stuck at "Initializing…" means the server is reachable but the chat interface has not yet been captured; wait a few seconds for the CDP connection to initialize.
- Regarding whether iOS and Android are supported: yes, the mobile UI can run in any modern mobile browser.
- The extension is self-contained, with its own public/ assets and uploads/ folder; if public/ or uploads/ also exists in the workspace, the extension will prefer the workspace path, so behavior may differ across workspaces.
- Supports English, Japanese, Simplified Chinese, Traditional Chinese, Korean, German, French, Spanish, Portuguese, Russian, Italian, Polish, Turkish,16 languages including Vietnamese, Indonesian, and Arabic; Arabic is automatically rendered from right to left, language detection uses navigator.language, and no configuration is required. The interface uses semantic HTML, ARIA roles, an aria-live region for connection status, keyboard navigation, and screen reader-compatible labels.
Version update (v1.0.20) Security improvements: child_process dependency completely removed; debug endpoints now require authentication; localhost protection added to all LS RPC calls.