Antigravity workflow guide

Antigravity Agent Manager: Where It Is and What Changed in 2.0

A practical guide for opening the legacy IDE surface, running parallel agent tasks, troubleshooting a missing entry, and moving to the current Antigravity 2.0 workspace model.

Agent Manager in Antigravity IDE vs Antigravity 2.0

Agent Manager originally described the mission-control view inside Antigravity IDE. It let developers start several agent tasks, inspect progress, review artifacts, and return to the editor when manual work was needed.

Antigravity 2.0 is presented as a broader agentic development platform rather than only a desktop IDE. That distinction matters when a tutorial says to click Open Agent Manager: the instruction can be correct for the legacy IDE while the current 2.0 interface uses a different workspace, account, or project entry.

ProductWhere agent work appearsBest match
Legacy Antigravity IDEOpen Agent Manager in the desktop top barFollowing IDE screenshots and managing tasks beside a local editor
Antigravity 2.0Current agentic workspace and project surfacesNew accounts, cloud-connected projects, and the latest platform workflow

How to Open Agent Manager in Antigravity IDE

Open a project first and wait until sign-in, model access, and workspace indexing finish. The Open Agent Manager control is normally visible in the upper application bar in the legacy desktop interface.

If the button is present but nothing opens, save your files, close blocking dialogs, and retry after the current agent response finishes. Avoid repeatedly clicking while a project is still loading because the surface can appear delayed on first launch.

Step 1

Open a real project

Launch the legacy desktop IDE, sign in, and wait for project indexing and model access to finish.

Step 2

Find the top-bar entry

Look for Open Agent Manager near the layout and account controls in the upper application bar.

Step 3

Create one bounded task

Start with a small repository task, define the expected output, and avoid overlapping file ownership.

Step 4

Review before applying

Inspect plans, artifacts, command requests, and changed files before accepting or merging the result.

A Safe Agent Manager Workflow

Treat Agent Manager as an orchestration surface, not as permission to let every task run unattended. Give each agent a bounded objective, review the proposed plan, and keep unrelated edits in separate tasks.

The screenshots below are real Antigravity IDE captures already used by this site. They show the editor, the Agent Manager entry, planning controls, and version context rather than an AI-generated mock interface.

Switch between editor and mission control

The project view keeps code, files, terminal access, and the Open Agent Manager entry in one desktop frame. Use the editor for precise manual changes and the manager for parallel task visibility.

Antigravity IDE editor and Open Agent Manager control

Set planning behavior before execution

The assistance panel exposes planning and faster execution modes. Choose the safer planning path for broad or risky work, and reserve fast execution for small, reversible tasks.

Antigravity IDE planning mode and settings panel

Confirm the build before troubleshooting

The About dialog identifies the installed Antigravity version. This is the fastest way to explain why your interface does not match a tutorial, screenshot, or current 2.0 documentation.

Antigravity IDE About dialog showing version information

Why Open Agent Manager May Be Missing

The most common reason is a version mismatch: you are reading a legacy IDE tutorial while using Antigravity 2.0, a newer build, or a differently provisioned account. A narrow window, unfinished onboarding, sign-in failure, disabled network access, or an update loop can also hide or delay the control.

Do not install an old build only to reproduce a screenshot. First confirm your product name and version, then use the current official documentation and the site update guide.

  • Check Help or About and record the exact product and version.
  • Finish Google sign-in and allow workspace initialization to complete.
  • Maximize the desktop window and close onboarding or update dialogs.
  • Open a normal local project instead of an empty welcome screen.
  • If you use Antigravity 2.0, look for the current workspace or project agent controls rather than the legacy label.

Should You Keep the Legacy IDE or Move to 2.0?

Use the legacy IDE only when your existing installation and workflow still require its desktop editor and Agent Manager layout. For a new setup, follow the current Antigravity 2.0 product flow unless an official compatibility requirement says otherwise.

Before changing versions, commit or back up project files, note active tasks, and test one real repository. Do not assume agent history, permissions, extensions, terminal behavior, or model availability will transfer unchanged.

Stay on the IDE temporarily

Reasonable for a stable existing workstation, a documented team workflow, or a short migration window. Keep the installer source and update notes verified.

Move to Antigravity 2.0

Best for new projects and current platform features. Recreate a small task first, review permissions, and confirm the replacement for every Agent Manager step you depended on.

Antigravity Agent Manager FAQ

Where is Agent Manager in Antigravity IDE?

In the legacy desktop IDE, look for Open Agent Manager in the upper application bar after opening a project and finishing sign-in.

Why can I not see Open Agent Manager?

You may be using Antigravity 2.0 instead of the legacy IDE, or onboarding, window size, sign-in, initialization, or an update dialog may be blocking the entry.

Is Agent Manager removed in Antigravity 2.0?

The old IDE label and layout are not the best guide to the 2.0 platform. Use the current workspace and project agent surfaces documented for 2.0 rather than forcing a legacy menu path.

Can Agent Manager run several agents at once?

The legacy concept supports parallel agent tasks, but each task should have a clear objective and separate file ownership to reduce conflicting edits.

Should I downgrade to get Agent Manager back?

Not just to match a screenshot. Confirm the current product, official support path, project compatibility, and security implications before installing an older build.

What should I check before moving to 2.0?

Back up or commit code, record active tasks, verify permissions and models, and test terminal, extensions, browser tools, and one small agent workflow.

Official references