Source Control not auto-refreshing file changes - requires manual refresh

Environment

  • IDE: Antigravity (latest version)
  • OS: macOS
  • Issue started: February 7, 2026

Problem Description

The Source Control panel in Antigravity does not automatically detect and display file changes. When I modify files (either through the AI agent or manually), the change indicator/badge does not appear on the Source Control icon, and the “Changes” section remains empty until I manually click the refresh button.

What Works

  • Git CLI commands work perfectly (git status correctly detects changes)
  • Commits via CLI or agent work fine
  • Manual refresh in Source Control panel shows changes correctly

What Doesn’t Work

  • Real-time file change detection in Source Control UI
  • Badge/indicator on Source Control icon when files are modified
  • Automatic update after commits

Steps to Reproduce

  1. Open any git-initialized folder in Antigravity
  2. Modify any tracked file (either directly in editor or via agent)
  3. Check Source Control panel → No changes shown
  4. Click refresh button → Changes now appear

Additional Context

  • This worked correctly until February 6, 2026
  • The issue persists even with a fresh folder and new git init
  • No settings were changed on my end
  • The issue affects both agent-made changes AND manual edits

Expected Behavior

Source Control should automatically detect file changes and update the UI in real-time, similar to VS Code behavior.


Is anyone else experiencing this issue? Any workarounds besides manual refresh?

8 Likes

Same issue here

Antigravity Version: 1.16.5
VSCode OSS Version: 1.107.0
Commit: 1504c8cc4b34dbfbb4a97ebe954b3da2b5634516
Date: 2026-02-02T23:37:17.781Z (6 days ago)
Electron: 39.2.3
Chromium: 142.0.7444.175
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 25.2.0
Language Server CL: 864538994

1 Like

The same issue appeared week ago

1 Like

Same problem here. antigravity 1.16.5

1 Like

Antigravity Version: 1.16.5
VSCode OSS Version: 1.107.0
Commit: 1504c8cc4b34dbfbb4a97ebe954b3da2b5634516
Date: 2026-02-02T23:37:17.781Z
Electron: 39.2.3
Chromium: 142.0.7444.175
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin x64 24.6.0
Language Server CL: 864538994

Same issue. Note that on my case, manually edited files are shown, only those generated by Gemini or Claude Code on my setup were not refreshed.

same issue here, for antigravity/antigravity-debian,now 1.16.5-1770081357 amd64

Hi everyone,

Thank you for the detailed reports. We have attempted to reproduce this issue on our end using the build details provided, but the Source Control panel and blue badge are updating automatically in our tests.

Testing Environment thread:
thread

Since we are currently unable to reproduce the failure in a clean state, could you please provide any additional details, logs, or environmental context that might help us isolate why this is occurring on your machines?

Thank you for your help in tracking this down!

same issue.
Environment Details

  • OS: Windows 10.0.26200.7840

  • Product: Google Deepmind Antigravity (Agentic AI Coding Assistant)

  • Context: Python Project

  • Python Version: 3.12.3

  • Git Version: 2.45.0.windows.1

Version: Antigravity
Commit: 1.16.5
Date: 1.107.0 (user setup)
Electron: 1504c8cc4b34dbfbb4a97ebe954b3da2b5634516
ElectronBuildId: 2026-02-02T23:37:17.781Z
Chromium: 39.2.3
Node.js: 142.0.7444.175
V8: 22.21.1
OS: 14.2.231.21-electron.0

Hi,

Thank you for the update. Since you are unable to reproduce the issue in a clean state, I have captured my console logs from Antigravity to help isolate the cause.

In my environment, the Source Control panel and badge have not updated automatically since February 7, 2026. Based on the logs, there seem to be several critical errors related to extension initialization and service dependencies that might be interfering with the file watcher or UI refresh logic:

1. Git Extension & UI Property Failures The log explicitly mentions a missing mandatory property for the Git extension, which likely prevents the Source Control UI from rendering badges correctly.

  • ERR [vscode.git]: property 'title' is mandatory and must be of type 'string' or 'object'

2. Core Service Dependency Errors A critical service dependency (agentSessions) is failing to initialize, causing instance creation errors.

  • ERR [createInstance] fZ depends on UNKNOWN service agentSessions.

3. Language Server Initialization Race Condition There is a recurring error where the system attempts to update user status before the Language Server Client is ready.

  • ERR [Extension Host] Failed to update user status Error: LanguageServerClient must be initialized first!

4. Command and Activation Mismatches Several internal commands are referenced but not defined, and certain extensions (e.g., google.chrome-devtools-mcp) are failing to activate due to missing modules.

Sanitized Log Snippet:

Plaintext

[DEBUG bootstrap-window] esModule: vs/workbench/workbench.desktop.main
[DEBUG bootstrap-window] new URL: vscode-file://vscode-app/Applications/Antigravity.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js

// Git & UI Property Errors
ERR [vscode.git]: property `title` is mandatory and must be of type `string` or `object`

// Service Dependency & Instance Failures
ERR [createInstance] fZ depends on UNKNOWN service agentSessions.: Error: [createInstance] fZ depends on UNKNOWN service agentSessions.
    at wUs.createInstance (vscode-file://vscode-app/Applications/Antigravity.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4549:1207)

// Command Definition Mismatches
ERR [google.antigravity]: Menu item references a command `antigravity.prioritized.chat.open` which is not defined.

// Initialization Order Issues
ERR [Extension Host] Failed to update user status Error: LanguageServerClient must be initialized first!

I am running Antigravity on macOS (Mac mini M4). This issue persists across fresh folders and new git init environment s.

I hope these details help your team identify the root cause. Please let me know if you need any further information.

Hi @Terrytime ,

Thank you for providing those detailed error logs. They helped us to reproduce the agentSessions and vscode.git errors in our local environment.

The issue stems from the git.autorefresh setting being disabled, which causes the git extension to fail specific validations. To fix this, please follow these steps:

Open your Command Palette (Cmd/Ctrl+Shift+P).

Run “Preferences: Open User Settings (JSON)”.

Locate your current configuration and update it from the existing version to the new version:

Existing Configuration:

JSON
{
“terminal.integrated.enableMultiLinePasteWarning”: “never”,
“git.autorefresh”: false
}

Updated Configuration (Change to this):

JSON
{
“terminal.integrated.enableMultiLinePasteWarning”: “never”,
“git.autorefresh”: true
}

Restart the application.

Please confirm if this resolves the state in your environment!

Adding “git.autorefresh”: true didn’t help

Hi @Thatipamula_Namratha,

Thank you for the suggestion.

Following your instructions, I added "git.autorefresh": true to my settings.json and restarted the application. To clarify, the "git.autorefresh" setting did not exist in my settings.json initially. I added the entire line "git.autorefresh": true as you instructed. Here is my current settings.json configuration:

{
“json.schemaDownload.enable”: true,
“workbench.colorTheme”: “Default Light Modern”,
“redhat.telemetry.enabled”: false,
“git.autorefresh”: true
}

Unfortunately, the issue persists. Here is exactly what happened:

  1. Immediately after the restart, the auto-refresh seemed to work briefly.

  2. However, after I performed a single commit, the auto-refresh feature stopped working again.

I have extracted the critical errors that seem to be causing the issue. Looking at the logs, this seems to be more than just a settings issue:

  • vscode.git Error: I see multiple errors stating: ERR [vscode.git]: property 'title' is mandatory and must be of type 'string' or 'object'.

  • Command Loop Error: Towards the end of the log, the error Error: command 'antigravity.getChromeDevtoolsMcpUrl' not found repeats hundreds of times.

It seems like these errors might be causing the Extension Host to hang, preventing the Git UI from updating. Could you please investigate these specific errors?

Please check the sanitized logs below:

[Relevant Error Logs - Sanitized]

  1. Git Extension Error (Likely causing the autorefresh failure):
    ERR [vscode.git]: property title is mandatory and must be of type string or object
    ERR [vscode.git]: property title is mandatory and must be of type string or object

  2. Missing Module Error:
    Activating extension ‘google.chrome-devtools-mcp’ failed: Cannot find module ‘/Applications/Antigravity.app/Contents/Resources/app/extensions/chrome-devtools-mcp/out/extension.js’
    Require stack:

  • /Applications/Antigravity.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js
  1. Infinite Loop Error (Repeated hundreds of times in the log):
    [Extension Host] [ExtensionServer] Failed to get Chrome DevTools MCP URL: Error: command ‘antigravity.getChromeDevtoolsMcpUrl’ not found
    at r9i.n (vscode-file://vscode-app/Applications/Antigravity.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4426:5759)
    at r9i.executeCommand (vscode-file://vscode-app/Applications/Antigravity.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4426:5691)

(The above error repeats continuously, likely causing the Extension Host to hang.)

I had the same synchronization issues with the source control, and it was fixed after I updated my Google Antigravity to the latest version.

Antigravity Version: 1.18.3
VSCode OSS Version: 1.107.0
Commit: c9b91c281ca4919466bd32a6ea2fcdab11102259
Date: 2026-02-19T02:34:56.403Z
Electron: 39.2.3
Chromium: 142.0.7444.175
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 24.6.0
Language Server CL: 872125356

Same here. Auto-refresh is back to normal after yesterday’s update.

It’s unclear from the update history whether a fix for this bug was officially included, but it appears to be resolved now.

Thank you all.

1 Like

Hi Everyone

Thank you @curly_potato and @Terrytime for the update! It is great to hear that the issue is resolved in the latest version 1.18.3 of Antigravity and that auto-refresh is back to normal for you. Please let us know if the issue still persists.

2 Likes

Unfortunately the above mentioned problems are not solved for me neither with 1.18.3 neither with 1.18.4.
I’m using windows 11. I’ve tried many ways to workaround these issues like:

  • uninstalling Antigravity , manually remove %userprofile%/.antigravity and %userprofile%/.gemini, %APPDATA%/Antigravity ; reinstalling the latest 1.18.4 version
  • do the same but first uninstall VS Code and delete manually %userprofile%/.vscode and %APPDATA%/Code

The errors are the same:
[vscode.git]: property `title` is mandatory and must be of type `string` or `object`
[google.antigravity]: Menu item references a command `antigravity.importAntigravitySettings` which is not defined in the ‘commands’ section.
[google.antigravity]: Menu item references a command `antigravity.prioritized.chat.open` which is not defined in the ‘commands’ section.
[Window] [Extension Host] Failed to update user status Error: LanguageServerClient must be initialized first!
at R.getInstance (c:\Users\\AppData\Local\Programs\Antigravity\resources\app\extensions\antigravity\dist\extension.js:2:1106230)

*at a.updateUserStatus (c:\\Users\\<user>\\AppData\\Local\\Programs\\Antigravity\\resources\\app\\extensions\\antigravity\\dist\\extension.js:2:1195683)*

*at a.restartUpdateLoop (c:\\Users\\<user>\\AppData\\Local\\Programs\\Antigravity\\resources\\app\\extensions\\antigravity\\dist\\extension.js:2:1196174)*

*at t.activate (c:\\Users\\<user>\\AppData\\Local\\Programs\\Antigravity\\resources\\app\\extensions\\antigravity\\dist\\extension.js:2:710004)*

*at async UNt.n (file:///c:/Users/<user>/AppData/Local/Programs/Antigravity/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:118:14207)*

*at async UNt.m (file:///c:/Users/<user>/AppData/Local/Programs/Antigravity/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:118:14170)*

*at async UNt.l (file:///c:/Users/<user>/AppData/Local/Programs/Antigravity/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:118:13625)*

[error] [Window] [Extension Host] (node:14660) [MODULE_TYPELESS_PACKAGE_JSON] Warning: Module type of file:///c:/Users//AppData/Local/Programs/Antigravity/resources/app/extensions/chrome-devtools-mcp/cdt_mcp/main.js is not specified and it doesn’t parse as CommonJS.

Reparsing as ES module because module syntax was detected. This incurs a performance overhead.

To eliminate this warning, add “type”: “module” to c:\Users\\AppData\Local\Programs\Antigravity\resources\app\extensions\chrome-devtools-mcp\package.json.

(Use `Antigravity --trace-warnings …` to show where the warning was created)

2026-02-24 21:18:26.312 [error] [Window] [vscode.git]: property `title` is mandatory and must be of type `string` or `object`
2026-02-24 21:19:00.061 [error] [Window] [createInstance] Woe depends on UNKNOWN service agentSessions.: Error: [createInstance] Woe depends on UNKNOWN service agentSessions.

*at sxr.y (vscode-file://vscode-app/c:/Users/<user>/AppData/Local/Programs/Antigravity/resources/app/out/vs/workbench/workbench.desktop.main.js:5412:4186)*

*at sxr.o (vscode-file://vscode-app/c:/Users/<user>/AppData/Local/Programs/Antigravity/resources/app/out/vs/workbench/workbench.desktop.main.js:5412:1360)*

*at sxr.createInstance (vscode-file://vscode-app/c:/Users/<user>/AppData/Local/Programs/Antigravity/resources/app/out/vs/workbench/workbench.desktop.main.js:5412:1207)*

*at new UEi (vscode-file://vscode-app/c:/Users/<user>/AppData/Local/Programs/Antigravity/resources/app/out/vs/workbench/workbench.desktop.main.js:6081:8181)*

*at new KYs (vscode-file://vscode-app/c:/Users/<user>/AppData/Local/Programs/Antigravity/resources/app/out/vs/workbench/workbench.desktop.main.js:6081:15818)*

*at sxr.o (vscode-file://vscode-app/c:/Users/<user>/AppData/Local/Programs/Antigravity/resources/app/out/vs/workbench/workbench.desktop.main.js:5412:1710)*

*at sxr.createInstance (vscode-file://vscode-app/c:/Users/<user>/AppData/Local/Programs/Antigravity/resources/app/out/vs/workbench/workbench.desktop.main.js:5412:1207)*

*at new jEi (vscode-file://vscode-app/c:/Users/<user>/AppData/Local/Programs/Antigravity/resources/app/out/vs/workbench/workbench.desktop.main.js:6081:18531)*

*at sxr.o (vscode-file://vscode-app/c:/Users/<user>/AppData/Local/Programs/Antigravity/resources/app/out/vs/workbench/workbench.desktop.main.js:5412:1710)*

*at sxr.createInstance (vscode-file://vscode-app/c:/Users/<user>/AppData/Local/Programs/Antigravity/resources/app/out/vs/workbench/workbench.desktop.main.js:5412:1207)

Not sure what else I can do to workaround these issues.*

Antigravity

Antigravity Version: 1.18.4
VSCode OSS Version: 1.107.0 (user setup)
Commit: c19fdcaaf941f1ddd45860bfe2449ac40a3164c2
Date: 2026-02-20T22:30:09.460Z (3 days 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: 873063495