Starting with Antigravity: Setting Up Your First Workspace in the 2.0 Era

March 4, 2026Updated: July 25, 2026Articles

You have opened Google Antigravity and cannot tell where on the screen to begin. The original article answered that first stumble by starting with registering a working folder as a workspace.

Antigravity 2.0 then arrived in May 2026 and the product range widened. There is now a standalone app, an IDE, a CLI, and an SDK. The screens have changed, but deciding where the work happens and what you delegate is still the thing to settle first.

First, choose your entry point

Antigravity 2.0: for managing several projects and agents together
Antigravity IDE: for developing alongside an agent while editing code
Antigravity CLI: for calling it up quickly from a terminal
Antigravity SDK: for developers embedding Antigravity’s agents in their own programs

If this is your first time, Antigravity 2.0 or the IDE — where the state of things is visible on screen — is easier to follow. The official getting-started guide is also built around the app and the IDE.

A workspace is a desk you are willing to hand over

A folder registered as a workspace becomes the place where the agent reads files, edits them, and runs commands as needed. Rather than handing over your whole computer, think of it as a dedicated desk holding only what one job requires.

To begin with, create an empty practice folder containing nothing but a short description and some sample files. There is no need to point it at a production site or a folder of important photos.

Make your first request something you can check by eye

Start with requests whose output you can open and inspect: “make an about page in this folder”, “organize these three notes into one Markdown file”.

Delegating a large application or an automated process from the outset makes it hard to follow what happened. Learn to read the plan, the diff, and the output on small requests, then widen the scope.

Safety checks before starting

Do not put passwords or API keys in the practice folder
Have copies or Git in place so deletions and overwrites can be undone
Read the plan and the diff it shows you
Keep a human as the final check on anything that sends data out, publishes, or costs money
Do not leave unnecessary permissions on projects you are not using

From older how-to articles, carry over the thinking rather than the screens

The Agent Manager and shortcuts described in the original article may sit differently in 2.0’s products and layout. Rather than hunting for the same place as an old screenshot, check the current official guide.

What carries over is the approach: separate your working locations by project, and start with small requests.

In summary: spend the first thirty minutes on boundaries, not on building

When starting with Antigravity, settle your entry point, your working folder, and the scope you delegate before choosing a model. Make one practice folder and ask for one small, reversible piece of work.