Summary
It would be great if Antigravity could natively support connecting to GitHub Codespaces (and other remote development environments), similar to how VS Code handles remote connections via the bottom-left corner button.
Problem / Use Case
Many developers use GitHub Codespaces or other cloud-based development environments for their projects. Currently, Antigravity operates only on the local file system, which means users who develop in Codespaces cannot leverage Antigravity’s powerful agentic AI coding capabilities directly in their remote environments.
For example, I’m running OpenClaw (an open-source AI assistant) in a GitHub Codespace, but I have to use VS Code Desktop to connect to the Codespace and then use separate AI tools. It would be much more seamless if Antigravity itself could connect directly to the Codespace.
Proposed Solution
Add a Remote Development feature to Antigravity that allows users to:
- Connect to GitHub Codespaces directly from the Antigravity interface (e.g., a connection button in the bottom-left corner, similar to VS Code)
-
- Browse and edit remote files as if they were local
-
- Run terminal commands in the remote environment
-
- Use all AI agent capabilities (code generation, debugging, refactoring, etc.) on the remote codebase
Since Antigravity is a fork of VS Code, the Remote Development extension architecture should be technically feasible to integrate.
- Use all AI agent capabilities (code generation, debugging, refactoring, etc.) on the remote codebase
Expected Benefits
- Developers can use Antigravity’s AI capabilities in cloud development environments
-
- Seamless workflow without switching between multiple tools
-
- Better support for teams using Codespaces for collaborative development
-
- Opens up the possibility of using Antigravity with other remote environments (SSH, WSL, Dev Containers, etc.)
Current Workaround
Currently, users have to:
- Use VS Code Desktop to connect to Codespaces, then use other AI extensions
-
- Or manually sync code via Git between local and remote environments
Neither approach is ideal compared to native integration.
- Or manually sync code via Git between local and remote environments