Hi all, I’ve got a limited idea of how the system works from the outside looking in by using Antigravity 2.0. I really like the idea of Antigravity IDE, but also see how it is a huge maintenance burden. I was implementing some extensions in CCS 20 (not antigravity related) to help students streamline project creation on beagle bone black and upon realizing that Theia adopts very similar plugin systems to VSCode I wanted to see if Antigravity could be adopted to it. Long story short it was minimal effort to get the IDE extension (from VSCode) functional, and a bit more effort to get inline suggestions as a Theia native plugin.
Is your feature request related to a specific problem?
Maintaining a branded standalone IDE by directly forking VS Code introduces significant ongoing engineering drag:
- Upstream Merge & Maintenance Debt: Direct forks require continuous rebasing against Microsoft’s upstream releases, resolving merge conflicts in internal editor patches, and managing fragile build pipelines.
- Licensing & Branding Constraints: VS Code’s upstream codebase is not inherently designed for downstream white-labeling, requiring complex patching to customize branding, telemetry, and packaging.
- Ecosystem Incompatibility: Enterprise and embedded developers often cannot use an external standalone editor because their workflows mandate certified Theia-based IDEs (such as Texas Instruments Code Composer Studio or Arduino IDE 2) for proprietary hardware debuggers and compiler toolchains.
Describe the solution you’d like
Rebase the standalone branded Antigravity IDE on Eclipse Theia, leveraging Theia’s modular platform architecture designed specifically for building branded, vendor-neutral enterprise IDEs.
Key architectural advantages:
- First-Class White-Labeling & Branding: Unlike VS Code, Eclipse Theia is designed from the ground up by the Eclipse Foundation to be composed into custom-branded IDE distributions (custom splash screens, identity, default layouts, and bundled capabilities) without forking core editor binaries.
- Standard Extension Architecture: Features such as inline AI completions utilize standard platform extension interfaces (e.g.,
InlineCompletionItemProvider), ensuring clean separation between the editor shell and the AI capabilities. - Decoupled Daemon Integration: The IDE communicates with the background language completion daemon over standard local IPC/HTTP, keeping heavy model inference decoupled from the UI thread.
- Dual-Market Advantage: The modular extensions developed for the branded Antigravity IDE can be packaged and distributed directly to users of downstream Theia environments (CCS, Arduino, etc.), expanding market reach to developers who cannot leave their vendor toolchains.
Describe alternatives you’ve considered
- Continuing to Maintain a VS Code Core Fork:
- Downside: Requires ongoing dedication of core engineering resources simply to track upstream releases and resolve merge conflicts.
- Limitation: Leaves out developers in regulated or embedded domains who cannot adopt a separate standalone editor.
- Distributing Only as a Loose Extension:
- Downside: Does not provide a fully branded, end-to-end “Antigravity IDE” product experience for users who want a turnkey AI-native development environment.
Additional context
Working Proof of Concept (PoC):
- A working proof of concept has been implemented and successfully validated in an active Eclipse Theia distribution (Code Composer Studio 20).
- Parity & Performance: Demonstrated full functional parity—sub-second, multi-line inline ghost text (Tab to accept) and project-aware contextual completions without modifying the host IDE core.
- Toolchain Coexistence: Operates cleanly alongside native compilers, build systems, and active hardware debug sessions without regressions.
Why Theia is the Ideal Foundation for a Branded IDE:
- Modular Composition: Theia IDEs are assembled using modular npm packages and plugins rather than monolith source forks, drastically reducing maintenance overhead.
- Proven Industry Path: Major enterprise IDEs—including Arduino IDE 2, Arm Keil Studio, Google Cloud Shell, and TI CCS—are built on Theia specifically for its flexibility and clean extensibility.
High-Level Architecture:
┌────────────────────────────────────────────────────────┐
│ Antigravity IDE (Theia-Based Distribution) │
│ │
│ Custom Branding / Themes / Workbench Layout │
│ Monaco Editor Layer │
│ │ │
│ │ Standard InlineCompletionItemProvider │
│ ▼ │
│ Antigravity Theia Extension Layer │
└─────────┬──────────────────────────────────────────────┘
│ Standard Localhost IPC / HTTP Interface
┌─────────▼──────────────────────────────────────────────┐
│ Background Language Completion Service │
│ • Context resolution & model inference │
└────────────────────────────────────────────────────────┘