Customizations Panel Empty + "no workspaces found" Error After 1.20.3 Update

# Bug Report: Customizations Panel Empty + “no workspaces found” Error After 1.20.3 Update

## Environment

- **OS**: Windows 11 (x64)

- **Antigravity Version**: 1.20.3 (updated from a working version on ~March 6, 2026)

- **Previous Version**: Was working perfectly before the update (likely 1.19.x)

## Problem Description

After updating to Antigravity 1.20.3, **all workspace-level Rules and Workflows disappeared** from the Customizations panel. The panel shows completely empty — no rules, no workflows — even though the files exist on disk and are correctly structured.

Additionally, attempting to create a new rule via the `+ Workspace` button produces the following error:

> **Failed to create rule: ConnectError: [unknown] no workspaces found…**

### What’s broken:

1. **Customizations panel** → Rules tab is empty, Workflows tab is empty

2. **Slash commands** → Typing `/` in chat shows no workflow suggestions

3. **Creating new rules/workflows via UI** → Fails with “no workspaces found” error

4. **Terminal “Always proceed” setting** → Seems to have regressed; prompts for approval on every command

### What still works:

- The AI agent **does receive** the rules and workflows via the system prompt (verified — the agent can see all rules/workflows in its context)

- Files on disk are intact and correctly formatted

- The workspace folder opens normally; git, file editing, extensions all work fine

## File Structure (Verified Correct)

```

.agent/

├── rules/

│ ├── core-rules.md ← YAML frontmatter + markdown content :white_check_mark:

│ └── style.md ← YAML frontmatter + markdown content :white_check_mark:

└── workflows/

├── commit.md            ← YAML frontmatter + markdown content ✅

├── implement.md         ← YAML frontmatter + markdown content ✅

├── plan.md              ← YAML frontmatter + markdown content ✅

└── strategy-research.md ← YAML frontmatter + markdown content ✅

```

- `.agent/` is **NOT** in `.gitignore`

- All files have valid YAML frontmatter with `description` field

- All files were working perfectly on the previous version

## Troubleshooting Steps Attempted (All Failed)

| # | Attempted Fix | Result |

|—|--------------|--------|

| 1 | Added `!.agent/` to `.gitignore` (explicit un-ignore) | :cross_mark: No effect |

| 2 | Deleted files from `.agent/`, restored from backup (file watcher trigger) | :cross_mark: No effect |

| 3 | `Developer: Reload Window` | :cross_mark: No effect |

| 4 | Restart Agent Service | :cross_mark: No effect |

| 5 | Close workspace → Reopen workspace | :cross_mark: No effect |

| 6 | Full Antigravity quit → Restart | :cross_mark: No effect |

| 7 | Deleted `%APPDATA%\Antigravity\Cache` and `GPUCache` folders → Restart | :cross_mark: No effect |

## Root Cause Analysis

The error message **“no workspaces found”** suggests that the 1.20.3 update broke the workspace registration/detection mechanism in the Customizations subsystem. The workspace is clearly open and functional (the agent works, files are accessible), but the Customizations panel and rule/workflow creation API cannot find it.

This appears to be a **regression introduced in 1.20.3**, not a configuration issue, since:

- The exact same setup worked on the previous version

- No configuration files were changed between the update and the bug appearing

- Multiple users on Reddit/Google Dev forums report the identical issue after updating to 1.20.3

## Expected Behavior

- Customizations panel should display all rules from `.agent/rules/`

- Customizations panel should display all workflows from `.agent/workflows/`

- `/` slash command should list available workflows

- `+ Workspace` button should successfully create new rules/workflows

## Workaround

The only confirmed workaround reported by other users is **downgrading to version 1.19.6**.

4 Likes

same here, for new projects, old projetcs, etc.

Same. I can’t figure out how to download the old version

I wonder if AI could help you with that?

1 Like

We appreciate you for bringing this to our attention. This issue have been escalated to our internal teams for a thorough investigation.

To ensure our engineering team can investigate and resolve these issues effectively, we highly recommend filing bug reports directly through the Antigravity in-app feedback tool. You can do this by navigating to the top-right corner of the interface, clicking the Feedback icon, and selecting Report Issue.

Same problem with all my projects

1 Like

Same problem in Antigravity Version: 1.20.5

2 Likes

Same problem with all my projects

same problem here with my projects

You can download the previous release from Antigravity Releases

1 Like

same in 1.20.5, for new projects, old projetcs, etc.

same, i retrograted it on 1.19.6 for the moment. But what is frustrating is that i spent many tokens to debug this … using Gemini pro 3.1 high and low to debug this yesterday…

on Linux you can make this with apt :

  1. use apt remove –purge antigravity

  2. reinstall it this way : sudo apt install antigravity=1.19.6-1772152296

  3. mark it to not update until the bug is fixed : sudo apt-mark hold antigravity

  4. IMPORTANT : unhold it to upgrade when it’s ok → sudo apt-mark unhold antigravity

  5. NOTE : wait 1 week or 2 before upgrade it in the future

same problem. for old and new.

Same here since the latest update.

Same here since the last update

same question since the last update

Failed to create rule: ConnectError: [unknown] no workspaces found

Antigravity

Verze: Antigravity
Potvrzení změn: 1.20.5
Datum: 1.107.0 (user setup)
Electron: 4603c2a412f8c7cca552ff00db91c3ee787016ff
ElectronBuildId: 2026-03-07T01:34:20.929Z (Před 1 týd.)
Chromium: 39.2.3
Node.js: 142.0.7444.175
V8: 22.21.1
OS: 14.2.231.21-electron.0

Hello @zhangsongbo @Camel, welcome to AI Forum!

To ensure you have the latest performance improvements and fixes, please download and install the newest version of Antigravity from our official download page (Google Antigravity). Please reach out if you experience any further difficulties after the update. As a reminder, please ensure that your use of the platform adheres to our Terms of Service .