The original Antigravity was an IDE with native integration for Google’s generative AI models. With Antigravity 2, Google offers a refashioned version of the product that it describes as a “standalone desktop command center” for agents. Antigravity 2 is closer to projects like LM Studio than a full-blown IDE.
The original Antigravity was an IDE with native integration for Google’s generative AI models. With Antigravity 2, Google offers a refashioned version of the product that it describes as a “standalone desktop command center” for agents. Antigravity 2 is closer to projects like LM Studio than a full-blown IDE.
When you launch the Antigravity app and start a new task, you have a few choices about how to manage your work. If you just want to have a quick conversation and don’t need to create a whole project to go with it, you can select “No Project” and just start prompting. If you do create a project, you can either configure the details yourself — what directory to use, what to call it — or have Antigravity set a randomly generated name and empty directory for starters.
Antigravity 2.0’s agent chat interface. This discussion revolves around a Python web project, which the agent has permission to modify.
Earlier versions of Antigravity had the concept of workspaces, which were confined to a single directory and lacked granular permissions or customizations. With Antigravity 2.0, workspaces are replaced by projects, which may span multiple directories (that you define explicitly) and have their own isolated settings and permissions. This new scheme better accommodates how many software projects work, especially those with shared components living in different places.
Another new option is local mode vs. worktree mode, which controls how agents interact with your project’s directories. It’s another example of how the Antigravity app lets you choose between the quick-and-dirty or slow-but-correct way of doing things. Local mode has the agent working directly on local folders or Git checkouts, for convenience and speed. The new worktree mode creates a new Git worktree for each conversation, so that the active working folder won’t be affected and work done by any subagents running in parallel won’t conflict.
In context
- Topic: Desarrollo con IA — Copilotos y agentes en el ciclo de desarrollo de software.
- Source: InfoWorld
- Published: 19/10/2026
Continue reading at the original source →
Excerpt published automatically by the site radar. The full text belongs to its publisher and is linked above.
Why it matters
What is changing in engineering is not typing speed, it is the relationship between whoever produces and whoever answers for the result. An assistant can generate in minutes something nobody on the team fully understands, and that carries a cost that shows up in no productivity metric.
I look at it from operations, not from the demo. The question is not whether the assistant writes a correct function, but whether the team can maintain what it produced six months later, with different people, without the original context. That is the real test and it almost never appears in the announcements.
What usually goes wrong
The problem appears when somebody accepts code they do not fully understand but which passes the tests. It works, it ships, and six months later it needs changing. That is when you discover nobody on the team can explain why it is written that way, and the small change becomes a rewrite.
What to watch
- Whether total time to production drops or only writing time, which is not the same thing.
- What happens to code review: if the assistant produces more, somebody has to read more.
- What happens to tests — generating code without generating tests only moves the problem forward.
How I read this entry
If I were rolling this out, I would do it with written rules: what can be generated, what always gets human eyes, and what is off limits to an assistant — typically anything handling money, identity or personal data. Rules give freedom, they do not remove it.
This entry is an excerpt from the original source, selected by the site radar. The commentary above is the site's own and does not belong to the cited publisher.
Comments
No comments yet. Yours can be the first.
Living through this in your own team?
Open the chat and tell me how you're handling it. I'm interested in comparing notes.
