Antigravity 2.0, our workshop
Copy, paste, hope
Before you joined, Kai and Remy built Hyper Shards in a chat window. The AI wrote code, Kai copied it into a file, pasted it over the old code, and hoped it worked.
That's like building a treehouse with tools scattered all over the garden. Real developers keep everything in one place: a workshop for code. Setting one up is the first card on our board.
What is an IDE?
An IDE (integrated development environment) is one app that holds all your coding tools together.
Its heart is the code editor, where you read and type code. It colours different parts of the code so they're easy to spot, and it can underline mistakes, like a spell checker for code.
Our studio uses Antigravity 2.0, Google's agentic development platform. "Agentic" means AI agents do real work inside it. It comes with its own code editor, the Antigravity IDE, and that is our workshop.
The parts of the workshop
- File explorerA list of every file and folder in the project. Click score.js and it opens.
- The editorThe big area in the middle where the code of the open file appears.
- The terminalA panel where you type commands, like npm run dev to start the game. It has its own lesson in this stage.
- Run the gameStart the game straight from the workshop and play it to see your change.
Bolt says: Most code editors share these same parts, so these skills work in other tools too.
Quick check
You want to open score.js in Garden Defense. Where do you look first?
- The file explorer
- The game's main menu
- The web browser's address bar
Show the answer
The file explorer
The file explorer lists every file in the project. Find score.js there and click it to open it in the editor.
AI agents built in
Antigravity 2.0 has AI agents built in. An agent is an AI helper that can do a job with several steps on its own: read our files, make a plan, edit the code and even run the game.
You can type "make Sprig's shield last 2 seconds longer", and the agent finds the right file and changes it.
You review every change
An agent should never sneak changes in. In Antigravity 2.0 you review what an agent changed, line by line, before you keep it. Lines it removes and lines it adds are marked, usually in red and green, or with a minus and a plus sign.
This view of changes is called a diff, short for "difference". You read it, then you choose: keep the change or throw it away.
Bolt says: Reading the diff takes a minute. Finding a hidden bug next week can take a whole afternoon.
Quick check
To save time, it's a good habit to keep the agent's changes without reading them.
- True
- False
Show the answer
False
The agent can make mistakes. Reading the diff before you keep a change is how you catch them while they're still small and easy to fix.
Read the diff
1- shieldTime: 3,2+ shieldTime: 5,3- shieldColor: 'blue',4+ shieldColor: 'pink',
Remy asked the agent: "make Sprig's shield last 2 seconds longer". This is the diff. What should Remy do?
- Keep all of it, the agent knows best
- Keep the shield time change, and ask the agent to undo the colour change
- Throw all of it away and give up on the shield
Show the answer
Keep the shield time change, and ask the agent to undo the colour change
Lines 1 and 2 are exactly what Remy asked for: 3 seconds becomes 5. Lines 3 and 4 change the colour, which nobody asked for. Reading the diff is how you spot extras like this.
Change, run, play
Here's the loop we use all day in the workshop:
- Ask the agent for one small change.
- Read the diff.
- Run the game and play it.
If it works, great. If not, we ask again or throw the change away.
Bolt says: Agents can type commands too. Next lesson: the terminal, the panel where we type them. After that, meet the brain behind the agents: Claude Opus 5.5.
Fact-checked 9 October 2026
- Google Antigravity: Getting started antigravity.google
- Google Antigravity: Antigravity 2.0 overview antigravity.google
- Google Antigravity: Review changes antigravity.google
- Google Antigravity: Models antigravity.google
- Google Codelabs: Getting started with the Antigravity IDE codelabs.developers.google.com