[BUG] Windows terminal commands hang on "Running..." because Antigravity compares c:\... and C:\... as different paths

Google Antigravity
1

Summary

On Windows, terminal commands in Antigravity can get stuck on “Running…” after approval because the workspace path appears to be compared case-sensitively.

What happens

  • Antigravity receives or stores the workspace path with a lowercase drive letter, for example:
    c:\Projects\SampleApp\workspace
  • In the integrated PowerShell terminal, the actual prompt/path is shown with an uppercase drive letter:
    C:\Projects\SampleApp\workspace
  • Antigravity seems to wait for an exact string match to confirm that the directory change completed
  • Because c:… and C:… do not match exactly, it never recognizes the step as completed
  • The task stays on “Running…” indefinitely, and the actual command may never execute

Observed behavior

  • The approval card shows the intended command
  • The terminal successfully changes directory
  • Antigravity hangs on “Running…” or eventually gets canceled/times out
  • After forcing the path to use uppercase C:…, the command executed immediately

Expected behavior

On Windows, path comparison should be case-insensitive, or paths should be normalized before comparison.

Why this looks like the root cause

Windows paths are case-insensitive, so c:… and C:… should be treated as the same path. The current behavior suggests that Antigravity is doing a case-sensitive string comparison when checking whether the working directory has changed.

Environment

  • OS: Windows
  • Shell: PowerShell integrated terminal
  • Antigravity category: Google Antigravity IDE / terminal execution

Reproduction idea

  1. Open a workspace on Windows
  2. Make sure the workspace path is stored or passed with a lowercase drive letter, like c:\Projects\SampleApp\workspace
  3. Approve any terminal command
  4. The terminal prompt shows the same path but with uppercase drive letter, like C:\Projects\SampleApp\workspace
  5. Antigravity remains stuck on “Running…” waiting for the directory change step

Workaround

Using the path with an uppercase drive letter (C:\Projects\SampleApp\workspace) made terminal commands start working immediately.

1 Like
2

"Spot on! This is a classic bug caused by poor case-sensitivity handling. From a Windows user’s perspective, it’s a truly absurd situation.

To summarize the phenomenon:

  • Windows’ Flexibility: At the file system (NTFS) level, it treats C:\ and c:\ as identical.

  • PowerShell’s Precision: It strictly follows system standards and returns the drive letter in uppercase (C:\).

  • Antigravity’s Rigidity: It validates the two paths using a simple string comparison, failing to recognize they are logically the same path and flagging them as a ‘mismatch.’

Ultimately, it’s a logic error where the program obsesses over the ‘format’ rather than the ‘content.’ As a result, users are left struggling with the terminal for no good reason. :joy:"

3

Hi Everyone,

Thank you for bringing these concerns to our attention. Please be assured that I have shared your feedback with our internal team for further review. We appreciate your continued patience as we work to enhance the Antigravity experience.