Skip to content

Multi-Workspace Projects

A real application spans multiple codebases: a frontend in one repo, a backend in another, shared libraries in a third. Antigravity Projects let you group these workspaces together so agents can operate across all of them from a single conversation. An agent can read the API schema from the backend repo, generate TypeScript types in the frontend repo, and update the shared library — all in one session.

Owl mascot

What you'll learn

  • Projects group multiple workspaces under one context so agents can work across repos
  • Agents in a Project share GEMINI.md, skills, and conversation history
  • The agent manager shows all workspaces in a Project with their current status

Build it

Step 1: Create a multi-workspace Project

In the Antigravity IDE, create a new Project and add workspaces:

Project: "my-fullstack-app"
Workspaces:
  - /Users/you/projects/frontend
  - /Users/you/projects/backend
  - /Users/you/projects/shared-lib

Step 2: Work across workspaces

In the backend workspace, read the API schema from src/api/openapi.yaml.
Generate TypeScript types from it and write them to the frontend workspace
at src/types/api.ts. Then update the shared library's client to use the new types.

The agent navigates all three workspaces, reads from one, writes to another, and updates the third — all in one session.

Step 3: CLI equivalent

You can launch the same multi-workspace session directly from the command line by supplying the project identifier and multiple workspace flags. This connects the agent to all defined repositories simultaneously.

bash
antigravity --project my-fullstack-app --workspace /Users/you/projects/frontend --workspace /Users/you/projects/backend --workspace /Users/you/projects/shared-lib

What goes wrong

MistakeHow you notice itThe fix
Agent writes to wrong workspaceFile appears in unexpected repoBe explicit about workspace paths in prompts. Use the full path: "Write to /Users/you/projects/frontend/src/types/api.ts"
Workspace permissions differAgent can read one repo but not write to anotherCheck file permissions across all workspaces. The agent inherits your user permissions
Context window overflows with multiple workspacesAgent forgets context from earlier workspacesUse /compact to compress context. Limit to 3 workspaces per Project for complex tasks

Next: Day 5 — Skills, Extensions & Production