Google Antigravity’s April replace in any case made it usable, and VS Code must be fearful

Antigravity is Google’s IDE constructed at the similar open-source task as VS Code. It’s necessarily the entirety VS Code is, simply with out the extension ecosystem. Google describes Antigravity as a sophisticated, AI-powered built-in building atmosphere designed for the “agent-first” generation of tool building.

I had attempted Antigravity off and on ahead of, however I by no means used it as my number one IDE. That modified after the April replace Google rolled out. The replace fastened a number of problems many people had with the IDE, however extra importantly, it offered up to date agentic permissions. That one function on my own made me transfer to Antigravity and ditch VS Code for excellent. At this level, I feel there are only a few causes left to stay with VS Code as an alternative of shifting to those more moderen agentic IDEs.

Google Antigravity is significantly better now

The April replace has fastened numerous issues

One of the most greatest guarantees of those new AI-powered IDEs is that they’re meant to really feel self reliant. You give them a job, give an explanation for what you need constructed, and allow them to paintings via it when you do one thing else. That’s the dream, a minimum of. Actually, maximum agentic coding workflows nonetheless want babysitting.

I will not rely the choice of instances I gave an AI agent a recommended to construct one thing, were given as much as make espresso, and got here again anticipating a minimum of some significant development, most effective to search out the IDE sitting there looking forward to me to click on “Permit” on a permission pop-up it precipitated two mins once I left. The AI is technically in a position to proceeding, however it’s caught looking forward to human approval each and every few steps.

That used to be my enjoy with Antigravity for the longest time. I preferred the course Google used to be taking with the IDE, and I stored checking again after primary updates, however I by no means totally switched to it for the reason that enjoy used to be nonetheless unfinished. On the other hand, Google made issues significantly better with the April replace. The replace utterly overhauled how permissions paintings in Antigravity via introducing what Google calls a Unified Permission Device. Antigravity now provides you with right kind keep watch over over how the AI agent interacts together with your device.

The device revolves round 3 permission tiers: Permit, Ask, and Deny. Those tiers let making a decision what the AI must care for autonomously and what in reality calls for guide approval. You’ll permit protected, repetitive movements like Git instructions or project-specific document get entry to, require affirmation for extra delicate duties, and completely block bad instructions or directories you by no means need the agent touching.

Those permissions are cut up throughout terminal instructions, filesystem get entry to, community requests, and MCP equipment. You’ll permit npm instructions whilst blockading harmful shell operations, prohibit the AI to a unmarried task folder, whitelist particular domain names, or tightly keep watch over how MCP servers have interaction together with your workspace.

Antigravity isn’t on my own right here. Equivalent permission techniques exist already in Cursor, Claude Code, and to a point in OpenAI’s Codex tooling as smartly, even supposing implementation main points range. Cursor already helps allowlists and denylists for instructions, MCP equipment, browser get entry to, and agent execution habits. You’ll outline which instructions the AI is authorized to run routinely and which of them must at all times be blocked or require approval.

Antigravity is most often higher than VS Code

It has the entirety you wish to have after which some

Whilst Google Antigravity is in response to VS Code, the real product is so much other and I might say higher than what Microsoft’s IDE has to provide. It doesn’t deal with AI as a unmarried assistant layered on best of the editor, however as a multi-agent execution fashion the place duties will also be deliberate, assigned, and achieved similtaneously. Other brokers perform inside outlined scopes and generate intermediate artifacts equivalent to job plans, reasoning summaries, or proposed code adjustments ahead of changes are carried out.

This additionally adjustments the place accountability sits all the way through building. Within VS Code, accountability for correctness in large part falls at the developer, each all the way through and after technology. Antigravity distributes that procedure throughout more than one phases that every produce inspectable output. Whilst that doesn’t ensure higher code, it does make stronger traceability. I will assessment intent ahead of comparing implementation, which is far nearer to how formal tool engineering workflows are designed.

As discussed previous, Google Antigravity has the entirety that you just get with VS Code. The core editor habits stays unchanged. The document explorer, built-in terminal, supply keep watch over panel, debugger interface, job runner, settings device, and command palette all behave precisely the way in which they do in Visible Studio Code. Current keyboard shortcuts raise over cleanly, together with customized keybindings, whilst issues, layouts, cut up perspectives, and multi-root workspaces paintings the similar approach as smartly.

Since Antigravity is dependent upon the similar Language Server Protocol ecosystem, options equivalent to syntax highlighting, IntelliSense, go-to-definition, diagnostics, and refactoring equipment additionally behave the similar approach they do in VS Code.

Extension compatibility stays some of the most powerful the reason why I used to be ready to modify to Antigravity. Most generally used VS Code extensions, together with formatters, linters, Git integrations, container tooling, and trying out frameworks, set up and serve as generally.