Antigravity IDE Bug: Topmost workspace in settings menu spawns an uncloseable separate window

Google Antigravity
1

Selecting the top-most workspace (authenticator) in the Settings menu triggers an unexpected behavior where a separate, uncloseable window is spawned. This window remains locked and cannot be closed as long as the workspace selection stays the same, whereas other workspaces below it behave normally.

Steps to Reproduce:

  1. Open Settings in Antigravity IDE.

  2. Navigate to the Workspaces section in the left sidebar.

  3. Click on the first/top-most workspace option (authenticator).

  4. Notice that a separate window opens and cannot be dismissed/closed until you click on a different workspace.

Expected Behavior:

Workspace settings should load cleanly within the main Settings panel without spawning a separate, uncloseable window.

Additional Information:

  • This issue only affects the first item in the workspace list (other workspaces like punyatoko work fine).

  • A screen recording demonstrating the bug has been uploaded here:
    https://youtu.be/Rho_vJQyVMk

2

Hi @qidamqolby,

I attempted to reproduce it using the provided steps, but i was unable to reproduce the behavior in my environment.

Could you please provide some additional information:

  • Antigravity IDE Version?
  • Operation System and version?
  • Is the authenticator workspace created manually, or is it generated automatically?
  • If available, please include any relevant logs or error messages?"
3

Here are my environment details:

Antigravity IDE Version: 2.1.1
VSCode OSS Version: 1.107.0 (user setup)
Commit: e0b7a2bcf575cfba10528c4e7c10bd3ce2d7769a
Date: 2026-06-17T22:39:43.962Z (1 mo ago)
Electron: 39.2.3
Chromium: 142.0.7444.175
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26200
Language Server CL: 933924006

The authenticator is generated by opening the project (though it’s an older project).

Currently, I can no longer reproduce the issue either because:

  1. Initially, I used ‘Clear Recently Opened’, then opened Antigravity settings, which triggered the bug.
  2. There might have been another trigger involved that I wasn’t aware of.

However, I tried again today and nothing happened.