🛸 antigravity-projects-fix

Clean up the Google Antigravity 2.0 "duplicate projects" mess in one command.

When one project folder shows up in the sidebar as MyApp, MyApp 2, MyApp 3 … all the way to MyApp 41, this tool collapses them back to a single, tidy entry.

---

📑 Table of contents

• Introduction
• What is this?
• The problem
• Why does it happen?
• The solution
• Installation
• Usage
• Where are the files? (auto-detect)
• The result
• Safety
• Will the duplicates come back? (cloud sync)
• Limitations
• FAQ
• Contributing
• License & disclaimer

---

👋 Introduction

Google Antigravity is Google's agentic, AI‑first IDE (a fork of VS Code). It's great — until you update to 2.0 and discover your Projects sidebar has quietly multiplied. A single repository you've opened a few times suddenly appears dozens of times, each with a number — 2, 3, … 41 — tacked on the end.

Deleting them one by one is hopeless when there are 40+ copies of one folder, and there's no "remove all" button. This tool fixes that in seconds — safely, with a dry‑run preview and an automatic backup.

🔎 What is this?

antigravity-projects-fix is a tiny, zero‑dependency Node.js command‑line tool. It reads Antigravity's local project registry, groups the entries by the real folder each one points to, and lets you:

• scan — see exactly how bad the duplication is (read‑only)
• interactive — a checkbox UI to pick exactly which entries to delete
• consolidate — keep one entry per folder, delete the rest
• merge — keep one entry and re‑home your chats under it (no chat is deleted)
• purge — wipe all project entries for a clean slate
• restore — undo, from an automatic backup
• diagnose — read‑only: show how chats link to projects on your machine

No installer, no npm packages, no network calls. One file, runs anywhere Node runs.

ℹ️ Unofficial community project. Not affiliated with Google LLC.

⚠️ Platform support — please read. This has been tested on Windows only. macOS (Apple Silicon and Intel) and Linux are supported in the code but are not yet tested on real hardware. If you're on a Mac, please be careful: run scan first (read‑only, changes nothing), and keep the automatic backup so you can restore if anything looks wrong. Reports from macOS/Linux are very welcome — see Discussions.

🐛 The problem

After the 2.0 update, the Projects panel looks like this:

Projects
 📁 my-app
 📁 my-app 2
 📁 my-app 3
 ...
 📁 my-app 41      ← 41 copies of ONE folder

Every numbered item opens the exact same directory. The list becomes unusable, and clearing the local SQLite/state files doesn't help because that's not where this list lives.

🧠 Why does it happen?

Antigravity identifies each workspace by a generated UUID, not by its folder path. During the 2.0 migration / cloud re‑sync it keeps minting a brand‑new UUID for the same folder instead of reusing the existing one. Each new UUID becomes another sidebar entry, and the UI appends 2, 3, … to tell the identical names apart.

The panel is rendered from one JSON file per entry here:

~/.gemini/config/projects/<uuid>.json

A real example — note that 41 of these files carry the same folderUri:

{
  "id": "0381f70c-d691-4bd0-bd02-0ec63f39d168",
  "name": "my-app 19",
  "projectResources": {
    "resources": [
      { "gitFolder": { "folderUri": "file:///home/user/code/my-app" } }
    ]
  }
}

This tool reads that folder, groups entries by their normalized folderUri, and collapses the duplicates.

✨ The solution

Point the tool at your machine and let it report the damage first:

Then merge --apply to keep one entry per folder and keep chats grouped (a backup is made first). If you only care about cleaning up the Projects list and don't need old chats re‑homed, use consolidate --apply instead — or purge --apply for a clean slate.

📦 Installation

Requires Node.js ≥ 16.7 (for fs.cpSync). No install needed — npx fetches and runs it in one step.

# Recommended — run without installing anything
npx antigravity-projects-fix scan

Other ways to run it

# Install globally, then use the `agfix` / `antigravity-projects-fix` command
npm install -g antigravity-projects-fix
agfix scan

# Or clone the repo and run the file directly
git clone https://github.com/ryukenshin546-a11y/antigravity-projects-fix.git
cd antigravity-projects-fix
node index.js scan

🚀 Usage

npx antigravity-projects-fix <command> [options]

The examples below use npx antigravity-projects-fix. If you cloned the repo instead, just swap that for node index.js — every command is identical.

Which command should I use?

Your goal	Command
Just look — change nothing	scan
Keep my projects, drop duplicates, and I don't need old chats grouped	consolidate --apply
Drop duplicates and keep all my chats grouped	merge --apply
Choose exactly what to delete / keep	interactive
Delete everything — start fresh	purge --apply
Undo a previous run	restore <backup-dir>
merge found 0 chats/project references / not sure what's safe	diagnose

All destructive commands are dry‑run by default, make an automatic backup, and ask for confirmation before deleting. Close Antigravity first.

Commands

Command	What it does
scan (default)	List projects grouped by folder and count the duplicates
interactive, i	Checkbox UI — tick exactly which entries to delete
consolidate	Keep one entry per folder, remove the duplicates
merge	Re‑point chats onto one keeper, then remove duplicates — no chat deleted
purge	Remove every project entry (clean slate)
restore <dir>	Copy project, chat, agyhub, or VS Code state backup files back
diagnose, doctor	Read‑only — report where chats link to projects on your machine (safe to share)

Interactive mode (recommended)

Antigravity itself has no multi‑select and takes ~3 clicks to remove a single project. This mode fixes that: one screen, tick everything you want gone, keep the rest, apply once.

npx antigravity-projects-fix interactive

• ↑ / ↓ (or j / k) — move
• Space — toggle the row
• a — select all · n — select none · d — select all duplicates (the default)
• Enter — review, then confirm before anything is deleted
• q / Esc — quit without changing anything

Duplicates are pre‑selected for you (one keeper per folder stays unchecked), so for the common case you can just press Enter. Nothing is deleted until you confirm, and a backup is always made first.

merge — keep your chats grouped under one project

consolidate removes the duplicate project entries, but each chat secretly remembers which duplicate it was created under. So after consolidating, a chat that belonged to “MyApp 19” can end up orphaned — its project is gone, so it may not appear under the surviving “MyApp”.

merge fixes that. Before removing the duplicates, it re‑points every affected chat to the single keeper project, so they all line up under one entry:

# Preview what would be re-pointed (changes nothing)
npx antigravity-projects-fix merge

# Re-home chats under one keeper, then drop the duplicate entries
npx antigravity-projects-fix merge --apply

How it works, and why it's safe:

• On many machines, each chat is a separate SQLite database in ~/.gemini/antigravity/conversations, with the project it belongs to stored inside as a 36‑character UUID.
• Antigravity keeps a large persistent write‑ahead log (.db-wal) next to each chat, and the live value often lives there. WAL frames are checksummed, so editing the .db-wal directly would corrupt the chat. merge therefore checkpoints the WAL into the main .db first (folding it in safely), then rewrites the UUID in place in the .db — same 36 characters, so the byte length never changes.
• Antigravity 2.0.1 can also keep conversation summaries as ~/.gemini/antigravity/conversations/*.pb and/or mirror the chat→project pointer in ~/.gemini/antigravity/agyhub_summaries_proto.pb.
• On some builds, especially the current macOS reports, Antigravity also stores trajectory summaries in the VS Code state database (globalStorage/state.vscdb and sometimes workspaceStorage/**/state.vscdb) as base64-encoded protobuf rows in ItemTable.
• merge scans the SQLite chat DBs, per-conversation protobuf files, the agyhub summaries file, and decoded state.vscdb protobuf rows. It rewrites whichever duplicate project UUID references it finds and verifies protobuf wire structure before and after each protobuf write.
• After each SQLite database write it runs SQLite's integrity_check; if a chat doesn't come back clean it's restored from backup automatically and its project is kept.
• No chat is ever deleted. Only its "belongs to project" pointer changes.
• Checkpointing needs a SQLite engine: Node ≥ 22 (built‑in node:sqlite) or a sqlite3 CLI on your PATH. If neither is available and a chat has a pending WAL, merge --apply refuses rather than risk corruption — your data is left untouched.
• Decoded state.vscdb scans/edits require Node ≥ 22 because they use Node's built-in node:sqlite reader.
• If merge finds only agyhub_summaries_proto.pb, merge --apply now refuses to delete duplicate project entries by default. That file can update the visible list, but it may be only a summary/index; recent macOS reports show chats can disappear again when opened if the authoritative state is elsewhere. Use diagnose and share the output first.
• The project registry, every chat file it touches, the agyhub protobuf file, and decoded VS Code state DBs (when used) are backed up first (projects.backup-…, conversations.merge-backup-…, antigravity.agyhub-backup-…, and User.state-backup-…). restore puts them back.
• Antigravity must be closed (the databases are otherwise locked).

🧪 Experimental. merge reverse‑engineers Antigravity's on‑disk format (there's no official API for this). The checkpoint‑then‑edit mechanism is verified on real chat databases and on Windows, but the chat↔project link is stored differently on some machines (see below). Run merge (the dry‑run) first, keep the automatic backups, and if anything looks off, restore and fall back to consolidate. Feedback welcome in Discussions.

⚠️ If merge reports "0 chats/project references" but you do have chats under the duplicates, the link between chats and projects on your machine is stored differently than merge currently detects. Don't run consolidate yet — it could unlink those chats from the sidebar (they're not deleted, and restore brings them back). Instead run the read‑only diagnose command and share the output so we can fix merge for your setup:

npx antigravity-projects-fix diagnose

diagnose now reports both broad byte-level hits and structured hints when the runtime can read them, such as the SQLite table/column (trajectory_metadata_blob.data), the agyhub protobuf field path, or decoded state.vscdb ItemTable keys like antigravityUnifiedStateSync.trajectorySummaries. It still prints counts only — no project paths, UUID values, or chat text.

Options

Option	Description
--apply	Actually perform the change (consolidate/merge/purge preview without it)
-y, --yes	Skip the confirmation prompt
--no-backup	Do not create a backup before changing files
--force	Skip the "is Antigravity running?" safety check
--dir <path>	Override the projects folder (otherwise it's auto-detected)
--conversations <path>	Override the chats folder for merge (default ~/.gemini/antigravity/conversations)
--agyhub-summaries <path>	Override the agyhub summaries protobuf file for merge / diagnose
--user-data-dir <path>	Override Antigravity's VS Code User data dir for decoded state.vscdb scans (or set ANTIGRAVITY_USER_DATA_DIR)
--allow-agyhub-only	Allow the legacy agyhub-summary-only merge behavior
--no-color	Disable colored output
-h, --help	Show help
-v, --version	Show version

Examples

# Pick exactly what to delete in a checkbox UI (recommended)
npx antigravity-projects-fix interactive

# 1. See what's going on (read-only, changes nothing)
npx antigravity-projects-fix scan

# 2. Preview the consolidation
npx antigravity-projects-fix consolidate

# 3. Collapse duplicates to one entry per folder (backs up first)
npx antigravity-projects-fix consolidate --apply

# 4. Nuke every project entry, no prompt
npx antigravity-projects-fix purge --apply --yes

# 5. Undo — restore from a backup
npx antigravity-projects-fix restore ~/.gemini/config/projects.backup-2026-05-20_06-32-10

📍 Where are the files? (auto-detect)

The project registry isn't in the same place on every machine. Its location depends on your OS, your Antigravity version, environment overrides, and where Electron put its user-data directory. Hard-coding one path would make the tool report "no projects found" on a perfectly affected machine — so instead it auto-detects.

On startup (when you don't pass --dir) it probes these locations in order and uses the first one that actually contains project files (a .json with a folderUri inside):

Order	Location	When it applies
1	$GEMINI_HOME/config/projects	explicit env override
2	~/.gemini/config/projects	current default
3	$XDG_CONFIG_HOME/gemini/config/projects · ~/.config/gemini/config/projects	Linux
4	%APPDATA%\Antigravity\config\projects · %LOCALAPPDATA%\…	Windows (Electron)
5	~/Library/Application Support/Antigravity/config/projects	macOS

• If detection lands somewhere other than the default, the tool prints Using detected projects folder: … so you can see exactly what it's touching.

• If nothing matches, it lists every path it checked and tells you to point --dir at the right one — it never fails silently.

• You can always skip detection with --dir:

  npx antigravity-projects-fix scan --dir "/custom/path/.gemini/config/projects"

💡 Not sure where yours is? Run npx antigravity-projects-fix scan first — it either finds it or shows you the list of places it looked.

✅ The result

A real run on a machine with the bug:

58 project files  →  5 real folder(s)  →  53 duplicate(s)

Before	After
58 sidebar entries	5 (one per real folder)
41× my-app	1× my-app
9× api-server	1× api-server
unusable panel	clean, navigable panel

Reopen Antigravity and the Projects panel is back to normal.

Which entry is kept?

For consolidate, the keeper per folder is chosen as: the name without a numeric suffix first (e.g. my-app over my-app 19), then the shortest name, then the oldest file.

🛡️ Safety

This tool is built to be hard to misuse:

• Dry‑run by default — consolidate, merge, and purge only print a preview until you add --apply.
• Automatic backup — before changing files, the project registry and every touched chat/protobuf/state file are copied to timestamped backup folders (skip with --no-backup).
• Backup must succeed first — if the backup can't be written (disk full, permissions), the tool aborts before changing anything rather than risk unprotected data.
• Won't fight the app — it refuses to run while Antigravity is detected as running (override with --force). Close Antigravity first.
• Won't touch the wrong folder — auto-detection only picks a directory that actually contains project files, and --dir is validated (it must be a real directory). Malformed JSON files are reported and skipped, never guessed at.
• Fully reversible — restore <backup-dir> puts project, chat, agyhub, and VS Code state backups back.
• Offline — it only touches local files and never makes a network request.

☁️ Will the duplicates come back? (cloud sync)

Antigravity syncs workspace data to your Google account. Local cleanup sticks in most cases, but if entries reappear after reopening, the duplicates are being re‑synced from the server. In that case you can:

• remove them from inside the app, or
• wait for an official fix (this is a known 2.0 migration bug), or
• re‑run this tool after a sync as a stopgap.

⚠️ Limitations

• consolidate operates only on the project registry (~/.gemini/config/projects), so chats attached to a removed duplicate can be left orphaned. Use merge if you want those chats re‑homed under the surviving project instead. With consolidate/purge, your conversation data itself (in ~/.gemini/antigravity/conversations) is never touched.
• merge is experimental — it edits chat databases and, on setups that use them, conversations/*.pb, agyhub_summaries_proto.pb, and decoded state.vscdb protobuf rows via length‑preserving UUID rewrites (reverse‑engineered, validated on synthetic data and Windows plus macOS user diagnostics). It never deletes a chat and backs every file up first, but treat it with the same care: dry‑run, keep the backup, restore if needed.
• An agyhub-only result is not enough evidence that chats are safely re-homed. In that case merge --apply will not delete duplicate project entries unless you explicitly pass --allow-agyhub-only; it prints a [blocked] message, changes no files, and exits with code 2.
• Tested on Windows only. macOS (Apple Silicon & Intel) and Linux use the same code paths (~/.gemini, pgrep) and should work — but they are unverified on real hardware. On those systems, treat it as experimental: run scan first, rely on the automatic backup, and please report results in an issue or discussion.

❓ FAQ

How do I remove duplicate projects in Google Antigravity 2.0? Run npx antigravity-projects-fix scan to see the duplicates, then use npx antigravity-projects-fix merge --apply if you want to keep chats grouped under one surviving project. If you only want to clean up the Projects list and don't need old chats re‑homed, use npx antigravity-projects-fix consolidate --apply. A backup is made automatically. See Usage.

Why does my Antigravity sidebar show the same project many times (MyApp 2, MyApp 3 …)? Antigravity 2.0 identifies each workspace by a generated UUID instead of by its folder path, and the migration keeps minting a new UUID for the same folder. See Why does it happen?.

Is it safe? Will it delete my code or conversations? It never touches your source code, and it never deletes conversation content. consolidate and purge edit only the project registry files (~/.gemini/config/projects). merge also rewrites the stored project pointer in chat DBs and, on some setups, conversations/*.pb, agyhub_summaries_proto.pb, or decoded state.vscdb protobuf rows — but it never deletes a chat and backs each touched file up first. Every destructive action is dry‑run by default. See Safety.

My duplicate projects each have their own chats — can I keep the chats and group them under one project? Yes — that's exactly what merge does. It re‑points each chat to a single keeper project (without deleting any chat), then removes the duplicate entries: npx antigravity-projects-fix merge --apply.

Can I undo it? Yes — npx antigravity-projects-fix restore <backup-dir> restores from the automatic backup. For merge, there may be separate backups for projects, conversations, agyhub, and VS Code state; restore each one you need.

It says "No projects folder found" but I have the bug — what now? Your install may live in a non-default location. The tool auto-detects common paths and, if it can't find one, lists everywhere it looked so you can point --dir at the right folder.

Does it work on macOS / Linux? The code paths are cross-platform, but it's currently tested on Windows only. On macOS/Linux, run scan first and rely on the backup — and please report your results.

🤝 Contributing & feedback

There are a few ways to get involved:

• 🐛 Open an issue — report a bug or request a feature (guided templates).
• 💬 Start a discussion — questions, ideas, or general feedback.
• 🔀 Open a pull request — fork, change, and submit; a PR template will guide you.
• ⭐ Star the repo if it helped you.

Especially welcome:

• testing on macOS / Linux,
• findings about how/when cloud sync re‑creates entries,
• optional conversation re‑mapping during consolidate.

📄 License & disclaimer

Released under the MIT License.

This is an independent, community‑made utility. It is not affiliated with, endorsed by, or supported by Google LLC. "Antigravity" and "Google" are trademarks of their respective owners. Use at your own risk — though the dry‑run‑by‑default and automatic backups are there to keep you safe.