Antigravity UI solid blank (Settings window & Agent Chat panel fail to render)

Environment:

  • OS: Windows 10/11
  • IDE: Antigravity IDE (VS Code core 1.107.0)
  • Local Service: agy.exe v1.5.3 (spawning from ~/.gemini/bin/agy.exe)
  • Workspace: Local folder on secondary drive (d:\Comfy-Desktop)

Description

Both the Antigravity Settings window and the Agent Chat side panel fail to display content, rendering as solid blank areas.

Inspecting the developer tools reveals the local backend (agy.exe) starts and answers on port 39979, but the workbench crashes during panel registration and webview loading.


Key Log Errors Identified

  1. View Conflict & Workbench Registration Failure:
    • ERR [google.google-antigravity]: A view with id 'antigravity.panel' is already registered.
    • ERR Unable to create workbench contribution 'antigravity.rendererStartupPerf'. Error: IWorkbenchContributionsRegistry#getContribution('antigravity.agentSidePanel'): contribution with that identifier is unknown.
  2. Webview / Service Worker Failure:
    • No service worker controller found. Waiting for controllerchange.
    • Multiple webview iframes failing to mount with unrecognized feature warnings: Unrecognized feature: 'local-network-access'.
  3. Environment Polyfill Error:
    • Failed to polyfill process.env.NODE_ENV: TypeError: Cannot add property NODE_ENV, object is not extensible

Full Developer Console Output

[DEBUG bootstrap-window] cssModules: undefined
workbench.js:3 [DEBUG bootstrap-window] esModule: vs/workbench/workbench.desktop.main
workbench.js:3 [DEBUG bootstrap-window] baseUrl: URL
workbench.js:3 [DEBUG bootstrap-window] new URL: vscode-file://vscode-app/c:/Users/Ruchira/AppData/Local/Programs/Antigravity%20IDE/resources/app/out/vs/workbench/workbench.desktop.main.js
workbench.desktop.main.js:3423 Failed to polyfill process.env.NODE_ENV: TypeError: Cannot add property NODE_ENV, object is not extensible
at workbench.desktop.main.js:3423:2721
(anonymous) @ workbench.desktop.main.js:3423
workbench.desktop.main.js:2802 WARN Via ‘product.json#extensionEnabledApiProposals’ extension ‘ms-vscode.vscode-selfhost-test-provider’ wants API proposal ‘attributableCoverage’ but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check ‘vscode.d.ts’) or was abandoned.
warn @ workbench.desktop.main.js:2802
workbench.desktop.main.js:2802 WARN Via ‘product.json#extensionEnabledApiProposals’ extension ‘ms-vsliveshare.vsliveshare’ wants API proposal ‘notebookCellExecutionState’ but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check ‘vscode.d.ts’) or was abandoned.
warn @ workbench.desktop.main.js:2802
workbench.desktop.main.js:2802 WARN Via ‘product.json#extensionEnabledApiProposals’ extension ‘ms-python.python’ wants API proposal ‘contribIssueReporter’ but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check ‘vscode.d.ts’) or was abandoned.
warn @ workbench.desktop.main.js:2802
workbench.desktop.main.js:2802 WARN Via ‘product.json#extensionEnabledApiProposals’ extension ‘github.vscode-pull-request-github’ wants API proposal ‘fileComments’ but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check ‘vscode.d.ts’) or was abandoned.
warn @ workbench.desktop.main.js:2802
workbench.desktop.main.js:2802 WARN Via ‘product.json#extensionEnabledApiProposals’ extension ‘github.copilot-chat’ wants API proposal ‘chatVariableResolver’ but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check ‘vscode.d.ts’) or was abandoned.
warn @ workbench.desktop.main.js:2802
workbench.desktop.main.js:2802 WARN Via ‘product.json#extensionEnabledApiProposals’ extension ‘github.copilot-chat’ wants API proposal ‘lmTools’ but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check ‘vscode.d.ts’) or was abandoned.
warn @ workbench.desktop.main.js:2802
workbench.desktop.main.js:2802 WARN Via ‘product.json#extensionEnabledApiProposals’ extension ‘ms-python.gather’ wants API proposal ‘notebookCellExecutionState’ but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check ‘vscode.d.ts’) or was abandoned.
warn @ workbench.desktop.main.js:2802
workbench.desktop.main.js:2802 WARN Via ‘product.json#extensionEnabledApiProposals’ extension ‘ms-python.vscode-pylance’ wants API proposal ‘notebookCellExecutionState’ but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check ‘vscode.d.ts’) or was abandoned.
warn @ workbench.desktop.main.js:2802
workbench.desktop.main.js:2802 WARN Via ‘product.json#extensionEnabledApiProposals’ extension ‘ms-python.debugpy’ wants API proposal ‘contribIssueReporter’ but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check ‘vscode.d.ts’) or was abandoned.
warn @ workbench.desktop.main.js:2802
workbench.desktop.main.js:2802 WARN Via ‘product.json#extensionEnabledApiProposals’ extension ‘ms-toolsai.jupyter’ wants API proposal ‘notebookCellExecutionState’ but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check ‘vscode.d.ts’) or was abandoned.
warn @ workbench.desktop.main.js:2802
workbench.desktop.main.js:2802 WARN Via ‘product.json#extensionEnabledApiProposals’ extension ‘dbaeumer.vscode-eslint’ wants API proposal ‘notebookCellExecutionState’ but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check ‘vscode.d.ts’) or was abandoned.
warn @ workbench.desktop.main.js:2802
workbench.desktop.main.js:2802 WARN Via ‘product.json#extensionEnabledApiProposals’ extension ‘ms-azuretools.vscode-azure-github-copilot’ wants API proposal ‘lmTools’ but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check ‘vscode.d.ts’) or was abandoned.
warn @ workbench.desktop.main.js:2802
workbench.desktop.main.js:2802 WARN Via ‘product.json#extensionEnabledApiProposals’ extension ‘ms-vscode.cpptools’ wants API proposal ‘lmTools’ but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check ‘vscode.d.ts’) or was abandoned.
warn @ workbench.desktop.main.js:2802
workbench.desktop.main.js:2802 WARN Via ‘product.json#extensionEnabledApiProposals’ extension ‘redhat.java’ wants API proposal ‘documentPaste’ but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check ‘vscode.d.ts’) or was abandoned.
warn @ workbench.desktop.main.js:2802
workbench.desktop.main.js:2802 WARN Via ‘product.json#extensionEnabledApiProposals’ extension ‘vscjava.vscode-java-pack’ wants API proposal ‘lmTools’ but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check ‘vscode.d.ts’) or was abandoned.
warn @ workbench.desktop.main.js:2802
workbench.desktop.main.js:8344 Unrecognized feature: ‘local-network-access’.
_createElement @ workbench.desktop.main.js:8344
workbench.desktop.main.js:8344 An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can escape its sandboxing.
mountTo @ workbench.desktop.main.js:8344
workbench.desktop.main.js:2802 INFO Started local extension host with pid 20492.
index.html?id=350f383a-0cb6-4bb3-a59f-ba8d214eb30c&parentId=1&origin=e032af19-e7e9-466c-98bc-f3b2a9f61073&swVersion=4&extensionId=&platform=electron&vscode-resource-base-authority=vscode-resource.vscode-cdn.net&parentOrigin=vscode-file%3A%2F%2Fvscode-app&purpose=webviewView:303 No service worker controller found. Waiting for controllerchange.
2workbench.desktop.main.js:2802 ERR [vscode.git]: property title is mandatory and must be of type string or object
error @ workbench.desktop.main.js:2802
workbench.desktop.main.js:2802 ERR [google.google-antigravity]: A view with id antigravity.panel is already registered.
error @ workbench.desktop.main.js:2802
workbench.desktop.main.js:4804 USS file icon theme updated for rendering
workbench.desktop.main.js:8175 Extension Host
workbench.desktop.main.js:8175 Set default auto-select family attempt timeout to 1000ms

workbench.desktop.main.js:4702 [Extension Host] [LAUNCH] Spawning C:\Users\Ruchira.gemini\bin\agy.exe (v1.5.3) --hub --hub-port=39979 --app_data_dir=antigravity --csrf_token=98dcf152-b8c2-4935-9669-5ea1dfdc31ee --add-dir=d:\Comfy-Desktop
workbench.desktop.main.js:4702 [Extension Host] [LAUNCH POLL 1] Error connecting to http://127.0.0.1:39979/healthz: connect ECONNREFUSED 127.0.0.1:39979
workbench.desktop.main.js:4702 [Extension Host] [LAUNCH] Server at http://127.0.0.1:39979 is READY after 2 attempt(s).
workbench.desktop.main.js:4702 [Extension Host] Antigravity AGY Extension: Subextension activation result: Object
workbench.desktop.main.js:4702 [Extension Host] [Jetski] Loading iframe URL: http://127.0.0.1:39979/settings-standalone?extensionView=true&extensionVariant=vs-code&hostVersion=0.0.1&ideVersion=1.107.0&useWebSocket=true&hostTheme=dark&enableMicrophone=false&platform=electron&isEnterpriseDisabled=true&hideWelcomePrefix=true&defaultGroupByNone=true&workspaceUri=file%3A%2F%2F%2Fd%253A%2FComfy-Desktop
workbench.desktop.main.js:8344 An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can escape its sandboxing.
mountTo @ workbench.desktop.main.js:8344
workbench.desktop.main.js:4702 [Extension Host] [Jetski] Loading iframe URL: http:/127.0.0.1:39979/c/0c0ed018-7f17-4f4c-b40a-c915e496ce91?extensionView=true&extensionVariant=vs-code&hostVersion=0.0.1&ideVersion=1.107.0&useWebSocket=true&hostTheme=dark&enableMicrophone=false&platform=electron&isEnterpriseDisabled=true&hideWelcomePrefix=true&defaultGroupByNone=true&workspaceUri=file%3A%2F%2F%2Fd%253A%2FComfy-Desktop
index.html?id=350f383a-0cb6-4bb3-a59f-ba8d214eb30c&parentId=1&origin=e032af19-e7e9-466c-98bc-f3b2a9f61073&swVersion=4&extensionId=&platform=electron&vscoderesource-base-authority=vscode-resource.vscode-cdnnet&parentOrigin=vscode-file%3A%2F%2Fvscode-app&purpose=webviewView:1069 Unrecognized feature: ‘local-network-access’.
(anonymous) @ index.html?id=350f383a-0cb6-4bb3-a59f-ba8d214eb30c&parentId=1&origin=e032af19-e7e9-466c-98bc-f3b2a9f61073&swVersion=4&extensionId=&platform=electron&vscode-resource-base-authority=vscode-resource.vscode-cdnnet&parentOrigin=vscode-file%3A%2F%2Fvscode-app&purpose=webviewView:1069
index.html?id=a5150566-82de-4b58-8315-1b8a46c96751&parentId=1&origin=7446459e-2f05-49ac-a3a9-e94daf870aef&swVersion=4&extensionId=google.google-antigravity&platform=electron&vscode-resource-base-authority=vscode-resource.vscode-cdnnet&parentOrigin=vscode-file%3A%2F%2Fvscode-app:1069 Unrecognized feature: ‘local-network-access’.
(anonymous) @ index.html?id=a5150566-82de-4b58-8315-1b8a46c96751&parentId=1&origin=7446459e-2f05-49ac-a3a9-e94daf870aef&swVersion=4&extensionId=google.google-antigravity&platform=electron&vscode-resource-base-authority=vscode-resource.vscode-cdnnet&parentOrigin=vscode-file%3A%2F%2Fvscode-app:1069
workbench.desktop.main.js:2802 ERR Unable to create workbench contribution ‘antigravity.rendererStartupPerf’. Error: IWorkbenchContributionsRegistry#getContribution(‘antigravity.agentSidePanel’): contribution with that identifier is unknown.
at iSi.getWorkbenchContribution (workbench.desktop.main.js:4671:29410)
at zbi._measureAgentSidePanelInitTime (workbench.desktop.main.js:8395:2391)
at new zbi (workbench.desktop.main.js:8395:2052)
at Ggr._createInstance (workbench.desktop.main.js:5595:2181)
at Ggr.createInstance (workbench.desktop.main.js:5595:1611)
at iSi.safeCreateContribution (workbench.desktop.main.js:4671:31643)
at l (workbench.desktop.main.js:4671:31238)
error @ workbench.desktop.main.js:2802
workbench.desktop.main.js:2802 WARN SettingsEditor2: Settings not included in settingsLayout.ts: antigravity.enableAgentMode, extensions.requestTimeout, chat.agent.terminal.allowList, chat.agent.terminal.autoApprove, chat.agent.terminal.denyList, chat.tools.terminal.autoApprove, chat.tools.terminal.autoReplyToPrompts, chat.tools.terminal.blockDetectedFileWrites, chat.tools.terminal.enableAutoApprove, chat.tools.terminal.ignoreDefaultAutoApproveRules, chat.tools.terminal.outputLocation, chat.tools.terminal.shellIntegrationTimeout, chat.tools.terminal.terminalProfile.linux, chat.tools.terminal.terminalProfile.osx, chat.tools.terminal.terminalProfile.windows, github.copilot.chat.agent.terminal.allowList, github.copilot.chat.agent.terminal.denyList, terminal.integrated.developer.devMode, terminal.integrated.developer.ptyHost.latency, terminal.integrated.developer.ptyHost.startupDelay, inlineChat.accessibleDiffView, inlineChat.enableV2, inlineChat.finishOnType, inlineChat.holdToSpeech, inlineChat.notebookAgent, chat.agent.codeBlockProgress, chat.agent.enabled, chat.agent.maxRequests, chat.agent.thinking.collapsedTools, chat.agent.thinking.generateTitles, chat.agent.thinkingStyle, chat.agentSessionsViewLocation, chat.allowAnonymousAccess, chat.checkpoints.enabled, chat.checkpoints.showFileChanges, chat.commandCenter.enabled, chat.customAgentInSubagent.enabled, chat.detectParticipant.enabled, chat.disableAIFeatures, chat.editing.autoAcceptDelay, chat.editing.confirmEditRequestRemoval, chat.editing.confirmEditRequestRetry, chat.editor.fontFamily, chat.editor.fontSize, chat.editor.fontWeight, chat.editor.lineHeight, chat.editor.wordWrap, chat.editRequests, chat.edits2.enabled, chat.exitAfterDelegation, chat.experimental.detectParticipant.enabled, chat.extensionTools.enabled, chat.extensionUnification.enabled, chat.fontFamily, chat.fontSize, chat.implicitContext.enabled, chat.implicitContext.suggestedContext, chat.instructionsFilesLocations, chat.math.enabled, chat.mcp.access, chat.mcp.assisted.nuget.enabled, chat.mcp.autostart, chat.mcp.discovery.enabled, chat.mcp.gallery.enabled, chat.mcp.serverSampling, chat.modeFilesLocations, chat.notifyWindowOnConfirmation, chat.notifyWindowOnResponseReceived, chat.promptFilesLocations, chat.promptFilesRecommendations, chat.renderRelatedFiles, chat.restoreLastPanelSession, chat.sendElementsToChat.attachCSS, chat.sendElementsToChat.attachImages, chat.sendElementsToChat.enabled, chat.showAgentSessionsViewDescription, chat.suspendThrottling, chat.todoListTool.descriptionField, chat.todoListTool.writeOnly, chat.tools.edits.autoApprove, chat.tools.eligibleForAutoApproval, chat.tools.global.autoApprove, chat.tools.todos.showWidget, chat.tools.urls.autoApprove, chat.undoRequests.restoreInput, chat.useAgentsMdFile, chat.useClaudeSkills, chat.useNestedAgentsMdFiles, chat.viewSessions.enabled, chat.viewSessions.orientation, chat.viewTitle.enabled, chat.viewWelcome.enabled

Tracing your stack lines against out/vs/workbench/contrib/webview/browser/pre/index.html, service-worker.js, and workbench.desktop.main.js in VS Code core 1.107.0 separates the harmless startup warnings in your console from the actual failure blocking both [Jetski] iframes (/settings-standalone and /c/<session>):

  1. Why index.html:303 and index.html:1069 prove the Service Worker already resolved: In webview/browser/pre/index.html, No service worker controller found. Waiting for controllerchange is logged at line 303 during initial registration. The content handler awaits workerReady at line 991 and only assigns newFrame.src = './fake.html?...' at line 1069 after workerReady resolves. Because both of your webviews reach index.html:1069 (Unrecognized feature: 'local-network-access', which is just Chromium ignoring an experimental permission token on newFrame.setAttribute('allow', ...) at line 1060), the outer vscode-webview:// wrapper is already past the worker handshake. Likewise, the process.env.NODE_ENV TypeError (workbench.desktop.main.js:3423) is a benign caught exception on a frozen object.
  2. Why antigravity.panel collides (ERR [google.google-antigravity]: A view with id 'antigravity.panel' is already registered): This happens when a duplicate copy of google.google-antigravity in %USERPROFILE%\.antigravity-ide\extensions (typically pulled in by running Import VS Code extensions) loads alongside the bundled extension or an older version folder. The first registration claims antigravity.panel in ViewsRegistry, while the second spawns agy.exe (v1.5.3) --hub --hub-port=39979, leaving the visible container bound to an orphaned provider. (The antigravity.rendererStartupPerf error at workbench.desktop.main.js:8395 is a side effect of _measureAgentSidePanelInitTime() looking up the legacy antigravity.agentSidePanel ID in memory.)
  3. Why the inner 127.0.0.1:39979 iframe stays blank: Although the Node Extension Host (pid 20492) reaches 127.0.0.1:39979/healthz, the inner [Jetski] iframe inside fake.html routes 127.0.0.1:39979 through processLocalhostRequest() (load-localhost in service-worker.js). When %APPDATA%\Antigravity IDE (defined by "nameLong": "Antigravity IDE" in product.json) has a corrupted Electron webview/GPU cache or Chromium routes 127.0.0.1 through a local proxy, the sub-frame renders blank.

Run these three steps in PowerShell to clear any duplicate extension collision and reset the Electron webview pipeline (while preserving your User\workspaceStorage project state):

1. Stop all processes and remove any duplicate google.google-antigravity extension folders

Stop-Process -Name "Antigravity IDE","Antigravity","agy","language_server" -Force -ErrorAction SilentlyContinue
$bundledExt = "$env:LOCALAPPDATA\Programs\Antigravity IDE\resources\app\extensions"
$extRoot = "$env:USERPROFILE\.antigravity-ide\extensions"
$copies = @(Get-ChildItem -Path $extRoot -Directory -Filter "google.google-antigravity*" -ErrorAction SilentlyContinue | Sort-Object LastWriteTime -Descending)
if ((Test-Path "$bundledExt\google.google-antigravity*") -or (Test-Path "$bundledExt\antigravity")) {
    $copies | Remove-Item -Recurse -Force -ErrorAction SilentlyContinue
} elseif ($copies.Count -gt 1) {
    $copies | Select-Object -Skip 1 | Remove-Item -Recurse -Force -ErrorAction SilentlyContinue
}

2. Purge the Electron webview, code, and GPU caches under %APPDATA%\Antigravity IDE

$ideRoot = "$env:APPDATA\Antigravity IDE"
foreach ($cache in @("Cache", "Code Cache", "CachedData", "GPUCache", "DawnWebGPUCache", "DawnGraphiteCache", "blob_storage")) {
    $targetPath = Join-Path $ideRoot $cache
    if (Test-Path -LiteralPath $targetPath) {
        Remove-Item -LiteralPath $targetPath -Recurse -Force -ErrorAction SilentlyContinue
    }
}

3. Relaunch Antigravity IDE.exe with loopback proxy bypass and GPU sub-frame flags

$env:NO_PROXY = "127.0.0.1,localhost"
& "$env:LOCALAPPDATA\Programs\Antigravity IDE\Antigravity IDE.exe" --no-proxy-server --disable-gpu

If you want to verify agy.exe --hub independently while the IDE is open, copy the 127.0.0.1:<hub-port>/settings-standalone?... URL from your console log into a regular browser tab; if it renders there, the issue was strictly the duplicate extension / Electron webview cache above.

Hi,

I ran the provided PowerShell steps (stopped all running processes, removed duplicate extensions from ~/.antigravity-ide/extensions, cleared the Electron/GPU/webview caches under %APPDATA%\Antigravity IDE, and relaunched with --no-proxy-server --disable-gpu), but the issue still persists.

The inner webview/iframe remains blank, and the Developer Tools console continues to report the following errors:

  1. ERR [google.google-antigravity]: A view with id ‘antigravity.panel’ is already registered.
  2. ERR Unable to create workbench contribution ‘antigravity.rendererStartupPerf’. Error: IWorkbenchContributionsRegistry#getContribution(‘antigravity.agentSidePanel’): contribution with that identifier is unknown.
    at iSi.getWorkbenchContribution (workbench.desktop.main.js:4671:29410)
    at zbi._measureAgentSidePanelInitTime (workbench.desktop.main.js:8395:2391)
  3. ERR [vscode.git]: property title is mandatory and must be of type string or object

It appears that the view collision on ‘antigravity.panel’ is still being triggered upon startup, and the renderer is failing to register/resolve the side panel contribution.

Could you please advise on what additional steps or manual cleanup are needed to completely resolve this?

Hi,

I tested launching with --disable-extensions, and the issue still reproduces entirely. This confirms that the view collision is not caused by any user-installed extension in ~/.antigravity-ide/extensions, but is bundled directly into the core workbench bundle.

Here is the exact terminal output and Developer Tools console logs upon running with --disable-extensions:

  1. Critical Webview Block (Causing the blank sub-frame/iframe):
    [main] Blocked vscode-webview request vscode-webview://0bphk0e7uu2hvm4e6obb9j2st2bae0aa9c833je6b156r755ln5s/index.html?id=…&purpose=webviewView

  2. Console Errors:

  • ERR [google.google-antigravity]: A view with id antigravity.panel is already registered.
  • Failed to get VSCode workspaces: Error: command ‘antigravity.importVSCodeRecentWorkspaces’ not found
  • ERR Unable to create workbench contribution ‘antigravity.rendererStartupPerf’. Error: IWorkbenchContributionsRegistry#getContribution(‘antigravity.agentSidePanel’): contribution with that identifier is unknown.

The root cause of the blank UI appears to be the Electron main process blocking the vscode-webview:// scheme request during panel instantiation, alongside the internal registration collisions in workbench.desktop.main.js.

Is there a command-line flag or configuration workaround to allow/unblock this webview protocol in Electron, or does this require an updated build?

Hi,

I performed a 100% clean reinstall (completely removing %LOCALAPPDATA%\Programs\Antigravity IDE, %APPDATA%\Antigravity IDE, and %USERPROFILE%.antigravity-ide prior to running the installer).

Immediately upon launching the fresh installation, the exact same errors trigger in the Developer Tools console out-of-the-box:

  • ERR [google.google-antigravity]: A view with id antigravity.panel is already registered.
  • ERR Unable to create workbench contribution ‘antigravity.rendererStartupPerf’. Error: IWorkbenchContributionsRegistry#getContribution(‘antigravity.agentSidePanel’): contribution with that identifier is unknown.
    at iSi.getWorkbenchContribution (workbench.desktop.main.js:4671:29410)
    at zbi._measureAgentSidePanelInitTime (workbench.desktop.main.js:8395:2391)
  • [main] Blocked vscode-webview request vscode-webview://…/index.html?..&purpose=webviewView

Because this reproduces on a pristine install with no residual user profile data or imported extensions, it confirms that this specific installer build has a package regression:

  1. antigravity.panel is doubly registered within the bundled core workbench scripts.
  2. _measureAgentSidePanelInitTime() has a legacy dependency looking up the unregistered antigravity.agentSidePanel.
  3. The Electron main process intercepts and blocks internal vscode-webview:// requests.

Could you provide an updated patch release or a download link to the previous stable build while this regression is resolved?

Thanks for running the --disable-extensions test and checking on a clean reinstall. That narrows things down considerably and shows that my first cache/extension hypothesis missed the mark - this is definitely inside the packaged bundle itself.

Looking at the exact errors from your terminal and console logs against main.js, workbench.desktop.main.js, and service-worker.js in 1.107.0, this installer build was caught mid-migration between the old built-in workbench panel (antigravity.agentSidePanel) and the bundled google.google-antigravity extension (antigravity.panel).


What Can Be Solved Locally vs. What Cannot (and Why)

1. What CAN be solved locally right now (via file patching):

Because Electron ships main.js, workbench.desktop.main.js, service-worker.js, and product.json as unpacked files under %LOCALAPPDATA%\Programs\Antigravity IDE\resources\app, we can patch four specific issues on disk:

  • Unblocking vscode-webview:// in main.js: In defaultSession.webRequest.onBeforeRequest, main.js checks:

    h=(m,E)=>{if(m.path!=="/index.html")return!0;const A=E.frame;if(!A||!this.windowsMainService)return!1;for(const v of this.windowsMainService.getWindows())if(v.win&&A.processId===v.win.webContents.mainFrame.processId)return!0;return!1}
    

    When the webview <iframe> navigates inside its Out-Of-Process Iframe renderer process (A.processId !== mainFrame.processId) or via the Service Worker (A === null), h returns false and logs [main] Blocked vscode-webview request. We can patch h so OOPIF subframes (E.frame.top) and Service Worker requests (!E.frame) are allowed through.

  • Fixing the antigravity.panel registry collision in workbench.desktop.main.js: When google.google-antigravity loads, ViewsExtensionHandler.addViews() hits:

    if(this.viewsRegistry.getView(g.id)!==null){o.error(p(2983,null,g.id));continue}
    

    Because antigravity.panel is already in ViewsRegistry (with an empty extensionId=, as seen on line 81 of your first log), it logs ERR [google.google-antigravity]: A view with id antigravity.panel is already registered and skips registering the extension’s view descriptor. We can patch that check to deregister the pre-existing stub view first instead of skipping.

  • Stopping the antigravity.agentSidePanel crash (workbench.desktop.main.js:8395): _measureAgentSidePanelInitTime() calls getWorkbenchContribution('antigravity.agentSidePanel')?.onboardingCompleted(). Because getWorkbenchContribution() throws when an ID isn’t registered rather than returning undefined, optional chaining (?.) doesn’t catch it. We can no-op _measureAgentSidePanelInitTime().

  • Bypassing the service-worker.js localhost stall for 127.0.0.1:39979: Even when index.html:1069 loads fake.html (as your Settings webview did on line 99 of your first log), the inner [Jetski] iframes (http://127.0.0.1:39979/settings-standalone and /c/<session>) are intercepted by service-worker.js (processLocalhostRequest), which waits on a load-localhost port-mapping round-trip back to the outer index.html client (only needed when remoteAuthority is set for SSH/WSL). We can guard that interceptor with remoteAuthority&& so local 127.0.0.1 iframes load directly, and update the SHA-256 hash in product.json so VS Code doesn’t show [Unsupported].

2. What CANNOT be guaranteed 100% yet (and why):

  • We don’t have your exact installer build files locally: My local 1.107.0 build is a slightly older commit where _measureAgentSidePanelInitTime is at line 8787 instead of line 8395. Remember that --disable-extensions only disables user extensions in ~/.antigravity-ide/extensions - it still loads all built-in extensions in resources\app\extensions. Without seeing the contents of resources\app\extensions in your specific installer build, we can’t tell yet whether two built-in extension folders in your installer (antigravity and google-antigravity) are colliding at the package.json level.
  • Missing antigravity.importVSCodeRecentWorkspaces command & updates: Any missing command inside the compiled extension bundle itself, as well as permanent persistence across future auto-updates, will require an updated official installer from the Antigravity team.

Step 1: Workaround & Diagnostic Script to Test (PowerShell)

Close Antigravity IDE and run this in PowerShell. It uses minifier-independent regexes (so it works even if minified variable names differ in your build), updates the product.json checksum, clears Electron’s CachedData (V8 bytecode cache) and Service Worker cache, and prints diagnostic info about your build’s built-in extensions:

Stop-Process -Name "Antigravity IDE", "agy", "language_server*" -Force -ErrorAction SilentlyContinue

$appRoot = "$env:LOCALAPPDATA\Programs\Antigravity IDE\resources\app"
$appOut  = "$appRoot\out"
$prodJs  = "$appRoot\product.json"
$mainJs  = "$appOut\main.js"
$wbJs    = "$appOut\vs\workbench\workbench.desktop.main.js"
$swJs    = "$appOut\vs\workbench\contrib\webview\browser\pre\service-worker.js"

# 0. Diagnostic: print build metadata and check built-in extensions for duplicate antigravity.panel declarations
if (Test-Path $prodJs) {
    $prod = Get-Content $prodJs -Raw | ConvertFrom-Json
    Write-Host "[INFO] Build: version=$($prod.version) ideVersion=$($prod.ideVersion) date=$($prod.date) commit=$($prod.commit)" -ForegroundColor Yellow
}
Get-ChildItem "$appRoot\extensions" -Directory -ErrorAction SilentlyContinue |
    Where-Object { $_.Name -match "antigravity|google" } |
    ForEach-Object { Write-Host "[INFO] Built-in extension folder: $($_.Name)" -ForegroundColor Yellow }
Get-ChildItem "$appRoot\extensions" -Recurse -Filter "package.json" -ErrorAction SilentlyContinue |
    Select-String "antigravity\.panel|google-antigravity|importVSCodeRecentWorkspaces" |
    ForEach-Object { Write-Host "[INFO] package.json match: $($_.Path):$($_.LineNumber) -> $($_.Line.Trim())" -ForegroundColor Yellow }

# 1. Patch main.js (minifier-independent): allow vscode-webview:// /index.html for OOPIF subframes and Service Workers
if (Test-Path $mainJs) {
    if (!(Test-Path "$mainJs.bak")) { Copy-Item $mainJs "$mainJs.bak" -Force }
    $cMain = [System.IO.File]::ReadAllText("$mainJs.bak")
    $rxMain = 'if\(([a-zA-Z0-9_$]+)\.path!=="/index\.html"\)return!0;const ([a-zA-Z0-9_$]+)=([a-zA-Z0-9_$]+)\.frame;if\(!\2\|\|!this\.windowsMainService\)return!1;'
    $repMain = 'if($1.path!=="/index.html"||!$3.frame||$3.frame.top)return!0;const $2=$3.frame;if(!$2||!this.windowsMainService)return!1;'
    if ([regex]::IsMatch($cMain, $rxMain)) {
        [System.IO.File]::WriteAllText($mainJs, [regex]::Replace($cMain, $rxMain, $repMain))
        Write-Host "[OK] Patched main.js (unblocked vscode-webview:// requests)" -ForegroundColor Green
    } else {
        Write-Warning "Pattern not found in main.js"
    }
}

# 2. Patch workbench.desktop.main.js (minifier-independent):
#    a) Deregister the pre-existing stub view when google.google-antigravity registers antigravity.panel
#    b) No-op _measureAgentSidePanelInitTime() so it stops looking up the removed antigravity.agentSidePanel
if (Test-Path $wbJs) {
    if (!(Test-Path "$wbJs.bak")) { Copy-Item $wbJs "$wbJs.bak" -Force }
    $cWb = [System.IO.File]::ReadAllText("$wbJs.bak")

    $rxView = 'if\(this\.viewsRegistry\.getView\(([a-zA-Z0-9_$]+)\.id\)!==null\)\{[a-zA-Z0-9_$]+\.error\([a-zA-Z0-9_$]+\(\d+,null,\1\.id\)\);continue\}'
    $repView = 'if(this.viewsRegistry.getView($1.id)!==null){this.viewsRegistry.deregisterViews([this.viewsRegistry.getView($1.id)],this.viewsRegistry.getViewContainer($1.id))}'
    if ([regex]::IsMatch($cWb, $rxView)) {
        $cWb = [regex]::Replace($cWb, $rxView, $repView)
        Write-Host "[OK] Patched workbench.desktop.main.js (resolved antigravity.panel view collision)" -ForegroundColor Green
    } else {
        Write-Warning "View collision pattern not found in workbench.desktop.main.js"
    }

    $oldPerf = '_measureAgentSidePanelInitTime(){'
    $newPerf = '_measureAgentSidePanelInitTime(){return;'
    if ($cWb.Contains($oldPerf)) {
        $cWb = $cWb.Replace($oldPerf, $newPerf)
        Write-Host "[OK] Patched workbench.desktop.main.js (disabled legacy antigravity.agentSidePanel lookup)" -ForegroundColor Green
    }

    [System.IO.File]::WriteAllText($wbJs, $cWb)

    # Update workbench.desktop.main.js SHA-256 checksum in product.json so [Unsupported] is not shown
    if (Test-Path $prodJs) {
        if (!(Test-Path "$prodJs.bak")) { Copy-Item $prodJs "$prodJs.bak" -Force }
        $hashBytes = [System.Security.Cryptography.SHA256]::HashData([System.IO.File]::ReadAllBytes($wbJs))
        $newHash = [Convert]::ToBase64String($hashBytes).TrimEnd('=')
        $cProd = [System.IO.File]::ReadAllText($prodJs)
        $cProd = [regex]::Replace($cProd, '("vs/workbench/workbench\.desktop\.main\.js"\s*:\s*")[^"]+(")', "`$1$newHash`$2")
        [System.IO.File]::WriteAllText($prodJs, $cProd)
        Write-Host "[OK] Updated product.json checksum for workbench.desktop.main.js" -ForegroundColor Green
    }
}

# 3. Patch service-worker.js: bypass processLocalhostRequest in local workspaces (!remoteAuthority) so 127.0.0.1 hub iframes load directly
if (Test-Path $swJs) {
    if (!(Test-Path "$swJs.bak")) { Copy-Item $swJs "$swJs.bak" -Force }
    $cSw = [System.IO.File]::ReadAllText("$swJs.bak")
    $oldSw = 'if(t.origin!==sw.origin&&t.host.match(/^(localhost|127.0.0.1|0.0.0.0):(\d+)$/))'
    $newSw = 'if(remoteAuthority&&t.origin!==sw.origin&&t.host.match(/^(localhost|127.0.0.1|0.0.0.0):(\d+)$/))'
    if ($cSw.Contains($oldSw)) {
        [System.IO.File]::WriteAllText($swJs, $cSw.Replace($oldSw, $newSw))
        Write-Host "[OK] Patched service-worker.js (direct 127.0.0.1 hub iframe fetch)" -ForegroundColor Green
    } else {
        Write-Warning "Pattern not found in service-worker.js"
    }
}

# 4. Clear V8 bytecode cache (CachedData) and Service Worker cache so Electron loads the patched JS
$ideData = "$env:APPDATA\Antigravity IDE"
foreach ($dir in @("CachedData", "Code Cache", "Cache", "GPUCache", "Service Worker")) {
    Remove-Item (Join-Path $ideData $dir) -Recurse -Force -ErrorAction SilentlyContinue
}
Write-Host "[OK] Cleared CachedData and Service Worker cache." -ForegroundColor Cyan

Then launch it from the terminal again:

& "$env:LOCALAPPDATA\Programs\Antigravity IDE\Antigravity IDE.exe"

Step 2: Additional Data Needed From Your Machine (If Anything Still Fails)

Please let me know how this test goes. If the panels still don’t render after running the script, could you share these 4 specific data points so we can see what is different in your installer build?

  1. The PowerShell output from Step 1 above: Specifically the yellow [INFO] lines (showing your product.json commit/date and which built-in resources\app\extensions folders matched antigravity.panel) and whether all five green [OK] lines printed.

  2. Direct browser check on agy.exe --hub: While Antigravity IDE is open, copy the http://127.0.0.1:<port>/settings-standalone?... URL from your DevTools Console and open it directly in Chrome or Edge. Does the Settings UI render normally in an external browser, or does it show a blank page/error there too?

  3. Where antigravity.panel is defined in your bundle: Run this one-liner in PowerShell and paste the output so we can see every file in your install that registers antigravity.panel:

    Get-ChildItem "$env:LOCALAPPDATA\Programs\Antigravity IDE\resources\app" -Recurse -Include *.js,*.json -ErrorAction SilentlyContinue | Select-String "antigravity\.panel" | Select-Object Path, LineNumber
    
  4. Updated Console / Terminal log: Any remaining errors in the terminal or DevTools Console after launching the patched build.

Hi,

Here is the complete diagnostic data from Step 1 and Step 2 gathered from my installation:

  1. Step 1 Patch Script Results:
  • Build metadata: The diagnostic scan reports that the built-in extension is located under resources\app\extensions\agy (not google.google-antigravity).
  • Patched issues:
    • The [main] Blocked vscode-webview request error is completely gone.
    • The antigravity.panel is already registered collision is resolved.
    • The antigravity.rendererStartupPerf crash no longer triggers.
  1. Step 2 Diagnostic Findings:
  • Exact locations of antigravity.panel in my bundle:

    • \resources\app\extensions\agy\vscode\extension.js (Lines 24238, 27918, 27919)
    • \resources\app\extensions\agy\package.json (Line 1)
    • \resources\app\out\vs\workbench\workbench.desktop.main.js (Lines 4773, 8085)
  • Direct Browser Check on agy.exe --hub:

    • Checked active listeners on agy (PID 12824): listening on 127.0.0.1:2194 and 127.0.0.1:2196.
    • When navigating to http://127.0.0.1:2194/settings-standalone in Chrome, the HTML shell is served and the browser tab title resolves to “antigravity”, but the page body remains blank (no UI elements render).
    • This indicates agy.exe is serving the container, but the frontend React/client bundle halts during mount without valid session/auth context.
  1. Current Blockers & Warnings:
  • Corrupt Installation Warning:
    Upon launch, VS Code displays an integrity notification:
    “Your Antigravity IDE installation appears to be corrupt. Please reinstall…”
    (Triggered by the file modifications to workbench.desktop.main.js / product.json checksums).
  • Missing Command / Auth Handshake Failure:
    The inner webview UI remains hung because the core cannot find the authentication command:
    workbench.desktop.main.js:2802 ERR command ‘antigravity.handleAuthRefresh’ not found: Error: command ‘antigravity.handleAuthRefresh’ not found
    at mei._tryExecuteCommand (workbench.desktop.main.js:5472:7376)
    at mei.executeCommand (workbench.desktop.main.js:5472:7274)

Since agy is serving the shell over port 2194 and the webview protocol interceptor is cleared, could you advise how to:

  1. Bypass/suppress the “installation corrupt” checksum warning.
  2. Stub or register antigravity.handleAuthRefresh so the authentication handshake finishes and the UI components can mount?

Glad to see the Step 1 patch eliminated the three core renderer crashes (vscode-webview protocol blocking, antigravity.panel registry collision, and rendererStartupPerf).

Here is the exact resolution for the two items in Post #7:

1. Permanently Suppressing the “Installation Corrupt” Checksum Warning

VS Code’s integrity validator (_isPure()) loops over Object.keys(productService.checksums) in resources\app\product.json. Because multiple core files were patched on disk, it detects the modified file signatures.

Setting "checksums": {} in product.json causes _isPure() to evaluate an empty set and return true immediately, permanently silencing the warning.

2. Resolving antigravity.handleAuthRefresh and Webview Mounting

The command antigravity.handleAuthRefresh is registered dynamically by the built-in extension (resources\app\extensions\agy\vscode\extension.js) inside its activate() handler.

When launching with --disable-extensions, the extension host disables all extensions (including built-ins), so the command is never registered. (This also explains why opening http://127.0.0.1:2194/settings-standalone directly in Chrome shows a blank page—the client-side bundle expects the acquireVsCodeApi() parent iframe messaging bridge from the IDE).

To silence the missing command error and test normal extension activation, close Antigravity IDE and run this in PowerShell:

Stop-Process -Name "Antigravity IDE", "agy", "language_server*" -Force -ErrorAction SilentlyContinue

$appRoot = "$env:LOCALAPPDATA\Programs\Antigravity IDE\resources\app"
$prodJs  = "$appRoot\product.json"
$wbJs    = "$appRoot\out\vs\workbench\workbench.desktop.main.js"

# 1. Blank out product.json checksums to eliminate integrity warning
if (Test-Path $prodJs) {
    $cProd = [System.IO.File]::ReadAllText($prodJs)
    $cProd = [regex]::Replace($cProd, '(?s)"checksums"\s*:\s*\{.*?\}', '"checksums":{}')
    [System.IO.File]::WriteAllText($prodJs, $cProd)
    Write-Host "[OK] Silenced corrupt installation checksum check in product.json" -ForegroundColor Green
}

# 2. Append .catch() to antigravity.handleAuthRefresh so missing/delayed extension registration does not reject
if (Test-Path $wbJs) {
    $cWb = [System.IO.File]::ReadAllText($wbJs)
    $oldAuth = 'this._commandService.executeCommand("antigravity.handleAuthRefresh")'
    $newAuth = 'this._commandService.executeCommand("antigravity.handleAuthRefresh").catch(()=>{})'
    if ($cWb.Contains($oldAuth)) {
        $cWb = $cWb.Replace($oldAuth, $newAuth)
        [System.IO.File]::WriteAllText($wbJs, $cWb)
        Write-Host "[OK] Guarded antigravity.handleAuthRefresh with .catch() handler" -ForegroundColor Green
    }
}

# 3. Clear CachedData so the updated JS bytecode is recompiled cleanly
$ideData = "$env:APPDATA\Antigravity IDE"
Remove-Item (Join-Path $ideData "CachedData") -Recurse -Force -ErrorAction SilentlyContinue
Write-Host "[OK] Cleared CachedData" -ForegroundColor Cyan

# 4. Launch WITHOUT --disable-extensions so built-in agy extension activates normally
& "$env:LOCALAPPDATA\Programs\Antigravity IDE\Antigravity IDE.exe"

Once launched without --disable-extensions, check whether the built-in agy extension completes activation and mounts the Settings and Agent Chat views. If anything remains blank, check the DevTools Console (Help > Toggle Developer Tools) for any new errors logged during extension activation.

Hi,

I performed a complete uninstall and clean install of the newest update (Antigravity IDE 2.7.0, bundled with agy.exe v1.5.8 / hostVersion=1.11.0 / ideVersion=1.107.0), and unfortunately, the exact same issue persists out of the box.

I re-applied the local patches to the new 2.7.0 files (including bypassing the onboarding maximization lock in workbench.desktop.main.js and guarding service-worker.js with remoteAuthority &&). Here is the exact status on 2.7.0 right now:

  1. What is Working:
  • The main VS Code workbench is now unlocked (Explorer, editor tabs, and standard Settings render and work normally).
  • agy.exe (v1.5.8) spawns cleanly and becomes ready on http://127.0.0.1:59795.
  • The subextension activates and [Jetski] initiates loading the iframe URLs (/?extensionView=true... and /settings-standalone).
  1. Exact Remaining Blocker on 2.7.0:
  • Both the Antigravity Settings tab and the right-side Agent Chat panel still render completely blank/dark.
  • Inside the webview wrapper, the inner Jetski iframe stalls permanently at:
    VM8:114 [Antigravity] Connection attempt 1/6
  • We also see this workbench service error in the DevTools Console:
    ERR [createInstance] hoe depends on UNKNOWN service agentSessions.: Error: [createInstance] hoe depends on UNKNOWN service agentSessions.

Since service-worker.js is already patched with remoteAuthority && and agy.exe is listening properly on localhost, what is blocking the inner Jetski iframe from getting past VM8:114 [Antigravity] Connection attempt 1/6 in 2.7.0 (e.g., WebSocket handshake, CSP connect-src, or acquireVsCodeApi() postMessage relay)?

Those two console errors come from separate layers inside Antigravity IDE 2.7.0:

  1. ERR [createInstance] hoe depends on UNKNOWN service agentSessions is not blocking Jetski. In out\vs\workbench\workbench.desktop.main.js, createDecorator("agentSessions") is injected into upstream VS Code Chat and Agent Sessions workbench classes (ChatWidget, ChatViewPane, AgentSessionsView), while the registerSingleton binding for agentSessions is omitted from the workbench bundle. That failure stays isolated inside _createInstance for built-in Chat views and does not stop extension webviews from mounting.
  2. Where VM8:114 [Antigravity] Connection attempt 1/6 originates. In out\vs\workbench\contrib\webview\browser\pre\index.html, #active-frame (vscode-webview://) applies sandbox="allow-same-origin allow-pointer-lock allow-scripts allow-downloads allow-forms" plus the Content-Security-Policy meta tag injected by the extension. Since your remoteAuthority && patch in service-worker.js already passes HTTP 127.0.0.1 fetches through, a stall at attempt 1/6 occurs inside the agy.exe (v1.5.8) page script (VM8:114), its WebSocket/RPC stream (/connect-websocket), or the extension’s CSP / postMessage bridge (extensions\agy\vscode\extension.js).

Run these two read-only checks on 2.7.0 to isolate the exact blocked call:

$agyExt = "$env:LOCALAPPDATA\Programs\Antigravity IDE\resources\app\extensions\agy"
Get-ChildItem $agyExt -Recurse -Include *.js,*.html -ErrorAction SilentlyContinue | ForEach-Object {
    $raw = [System.IO.File]::ReadAllText($_.FullName)
    foreach ($m in [regex]::Matches($raw, '.{0,70}(Content-Security-Policy|connect-src|useWebSocket|extensionView|acquireVsCodeApi).{0,70}')) {
        "$($_.Name): $($m.Value.Trim())"
    }
}

Then click VM8:114 in the IDE DevTools Console to copy lines 100-130 around Connection attempt 1/6, and open the complete verbatim 127.0.0.1:<port>/?extensionView=true... URL (including all query parameters) logged by [Jetski] in Chrome/Edge with DevTools (F12) → Console & Network → WS open. Seeing the exact VM8:114 target plus whether external Chrome shows the same 1/6 stall isolates an agy.exe backend/WebSocket failure from a VS Code webview CSP or postMessage handshake block.

Hi,

Here are the results from the read-only checks on Antigravity IDE 2.7.0 (note that agy.exe also auto-updated to v1.5.9):

  1. PowerShell CSP & Bridge Scan (extensions\agy):
  • extension.js: host = typeof acquireVsCodeApi === ‘function’ ? acquireVsCodeApi() : null;
  • extension.js:
  • extension.js:
  • bridge.js: const ep=,{antigravityApi:fp,extensionApi:gp}=(()=>{var a=acquireVsCodeApi();return gf({postToIframe:c=>{var d=id(c)&&c.channel===Xe.EXTENSION_A…
  • loading_bridge.js: const k=acquireVsCodeApi(),m=document.getElementById(“loading-details”)…
  1. IDE DevTools Console Status (agy.exe v1.5.9):
  • agy.exe (v1.5.9) spawns on http://127.0.0.1:4901 and reports READY.
  • [Jetski] Loading iframe URL: http://127.0.0.1:4901/?extensionView=true&extensionVariant=vs-code&hostVariant=antigravity-ide&hostVersion=1.11.0&ideVersion=1.107.0&useWebSocket=true&hostTheme=dark&enableMicrophone=false&platform=electron&isEnterpriseDisabled=true&hideWelcomePrefix=true&defaultGroupByNone=true&workspaceUri=...
  • Notably, on v1.5.9, the VM8:114 [Antigravity] Connection attempt 1/6 log no longer appears in the top-level console (it is either inside the nested OOPIF frame context or silent).
  1. External Chrome Check:
  • Opening the full verbatim http://127.0.0.1:4901/?extensionView=true... URL in Chrome sets the tab title to "antigravity", but the page remains completely blank with no Antigravity console errors (confirming it waits on bridge.js / acquireVsCodeApi() postMessage handshake from the parent webview).

Since bridge.js uses postToIframe to relay messages between acquireVsCodeApi() and the 127.0.0.1 iframe, how can we inspect the inner OOPIF frame or verify why bridge.js isn’t completing the handshake inside the IDE?

On Antigravity IDE 2.7.0, here is what can and cannot be resolved locally before patching further:

What can be resolved locally (unpacked JS/HTML): Any break inside extensions\agy\vscode\extension.js, bridge.js, loading_bridge.js, service-worker.js, or Content-Security-Policy headers (load-localhost routing, WebSocket URL blocking, or postToIframe origin filtering) lives in unpacked files on disk and can be fixed once traced. What cannot be resolved without diagnostics (and why): We cannot isolate a 2.7.0-specific failure blindly without the hidden 127.0.0.1 child frame trace, and if the compiled agy.exe (v1.5.9) binary itself fails internally or rejects WebSocket/auth sessions before sending readiness, no JS patch can alter agy.exe.

VS Code nests this UI three layers deep: the outer workbench, the vscode-webview:// iframe.webview.ready host (index.html → fake.html, where bridge.js runs), and the cross-origin 127.0.0.1 OOPIF. Focus the blank panel and run Developer: Open Webview Developer Tools from the Command Palette (Ctrl+Shift+P), which runs only when iframe.webview.ready is mounted, then switch the Console context dropdown from top to fake.html or 127.0.0.1. If the nested frame stays hidden, restart with Electron remote debugging and open 127.0.0.1:9222/json (or chrome://inspect/#devices) to attach directly to the 127.0.0.1 OOPIF target and check Console plus Network -> WS:

Stop-Process -Name "Antigravity IDE" -ErrorAction SilentlyContinue
Start-Process "$env:LOCALAPPDATA\Programs\Antigravity IDE\Antigravity IDE.exe" -ArgumentList "--remote-debugging-port=9222"

Inside the fake.html Console context, attach window.addEventListener("message", e => console.log("BRIDGE_MSG", e.origin, e.data)), check Output → Extension Host / Antigravity, and extract the handshake code on disk:

$agy = "$env:LOCALAPPDATA\Programs\Antigravity IDE\resources\app\extensions\agy"
Get-ChildItem $agy -Recurse -Include bridge.js,loading_bridge.js | ForEach-Object {
    $t = [System.IO.File]::ReadAllText($_.FullName)
    foreach ($kw in @('postToIframe','loading-details')) {
        $i = $t.IndexOf($kw); if ($i -ge 0) { $s = [Math]::Max(0,$i-120); "$($_.Name): " + $t.Substring($s, [Math]::Min(450, $t.Length-$s)) }
    }
}

Share the 127.0.0.1:9222 Console/WS output and those bridge.js / loading_bridge.js slices so we can separate a patchable JS/CSP mismatch from an upstream agy.exe failure.

Hi,

Here are the exact outputs from the PowerShell extraction and the --remote-debugging-port=9222 inspection on Antigravity IDE 2.7.0 (agy.exe v1.5.9):

  1. bridge.js and loading_bridge.js Slices:
  • bridge.js:
    =function(a,c,d){var g=new Xe.AntigravityApiEmitters;return{...ef(a,c,k=>g.merge(d(k))),...g.getEvents()}};function gf({postToIframe:a,iframeMessageEvent:c,postToExtension:d,extensionMessageEvent:g,extensionApiInterceptors:k,antigravityApiInterceptors:l}){function m(B,E,J){var Q={};for(let U of B.methods){let X=U.localName,da=U.localName;Q[U.localName]=async(Pa,Ma)=>{var Qa=J[X];return Qa?Qa.call(J,Pa,Ma):(0,E[da])(Pa)}}return Q}var {client:p,rou

  • loading_bridge.js:
    turn b};function h(b,c=\unexpected value ${b}!`){throw Error(c);};const k=acquireVsCodeApi(),m=document.getElementById(“loading-details”),n=document.getElementById(“loading-error”),p=document.getElementById(“error-message-text”),q=document.getElementById(“retry-button”),r=document.getElementById(“report-button”),u=document.getElementById(“loading-indicator”),v=document.getElementById(“host-input-container”),w=document.getElementById(“host-input”)`

  1. Findings from http://127.0.0.1:9222/json (Remote Debugging):
    When inspecting 127.0.0.1:9222/json while the Agent panel is open, there is NO vscode-webview:// (fake.html) or http://127.0.0.1:<port> target mounted at all. The only targets registered in Electron are:
  • workbench.html (.aider - Antigravity IDE - analytics.json)
  • DevTools
  • editorWorkerService
  • TextMateWorker
  1. Console Output:
  • agy.exe (v1.5.9) starts cleanly on http://127.0.0.1:20404 and logs:
    [Extension Host] [Jetski] Loading iframe URL: http://127.0.0.1:20404/?extensionView=true&extensionVariant=vs-code&hostVariant=antigravity-ide&hostVersion=1.11.0&ideVersion=1.107.0&useWebSocket=true&hostTheme=dark&enableMicrophone=false&platform=electron&isEnterpriseDisabled=true&hideWelcomePrefix=true&defaultGroupByNone=true&workspaceUri=...
  • However, the webview iframe never mounts into Electron’s target list (so neither fake.html nor the 127.0.0.1 OOPIF exists to attach to, and no red webview console errors appear).
  • Also logged in the workbench console:
    ERR command 'antigravity.isFileGitIgnored' not found

Why is the vscode-webview:// / 127.0.0.1 frame failing to mount as a target in Electron even after [Jetski] Loading iframe URL is logged?

Hi @Ruchira_Rodrigo,

You are already testing on the latest Antigravity IDE v2.7.0 with CLI v1.5.9.

Because the issue reproduces out of the box on a fresh installation and involves internal Electron webview protocol handling and workbench registration, please note the following documented guidance:

  1. Download and run the official Antigravity IDE v2.7.0 build directly from Google Antigravity - Releases rather than manually modifying packaged workbench JavaScript files, as patching core bundle scripts triggers installation integrity warnings.
  2. Follow the official changelog at Changelog | Google Antigravity Docs for upcoming patch releases addressing this Windows webview initialization regression.

Please reply to let us know how these steps work for you and whether they resolve the issue. If the problem continues, tell us what else we can help with.

[Extension Host] [Jetski] Loading iframe URL logs on the Node extension host when assigning webview.html, before the Electron renderer creates and navigates <iframe class="webview">. In workbench.desktop.main.js, mountTo() appends that <iframe>, asynchronously resolves the webview origin before setting src to index.html, and only adds .ready (and enables Developer: Open Webview Developer Tools) once "webview-ready" posts back. Chromium 127.0.0.1:9222/json only lists a nested <iframe> target once it navigates out-of-process; if src is never set or navigation is cancelled, nothing appears in /json.

Run this check in workbench.html DevTools Console while the blank Agent panel is open to see which layer actually stopped:

[...document.querySelectorAll('iframe')].map(f => ({
  id: f.id, cls: f.className, src: f.src,
  rect: f.getBoundingClientRect().toJSON()
}))

Then check the latest session logs (main.log, exthost.log, renderer.log, views.log) on 2.7.0 (Blocked vscode-webview request cancels navigation silently in Electron without raising red Console errors, and clean-installing 2.7.0 would have overwritten main.js unless re-patched alongside service-worker.js):

$d = Get-ChildItem "$env:APPDATA\Antigravity IDE\logs" -Directory | Sort-Object LastWriteTime -Descending | Select-Object -First 1
Get-ChildItem $d.FullName -Recurse -Include main.log,exthost.log,renderer.log,views.log | Select-String -Pattern "Blocked vscode-webview|isFileGitIgnored|agy|Jetski" | Select-Object -Last 20

If main.log shows Blocked vscode-webview request, re-applying the main.js onBeforeRequest fix restores index.html loading. If iframe.webview is absent ([]) with errors around antigravity.isFileGitIgnored in exthost.log, extension activation or view resolution aborted before creating the frame; if src is empty or .ready is missing, origin resolution (_initElement) or index.html / service-worker.js stalled before "webview-ready".

Update: resolved :tada:

The Settings window and Agent Chat panel render correctly now.

What fixed it: the agy backend auto-updated from v1.5.9 to v1.5.10 (its language server went from 2.32.0 to 2.32.2). The IDE build is unchanged (2.7.0, build date 2026-11-11, bundled extension 1.11.0). After the update the panels load straight away.

How to confirm:

  • Check the version in %USERPROFILE%\.gemini\bin\agy.version.json (should be 1.5.10 or later).
  • Or check the newest log in %USERPROFILE%\.gemini\antigravity\log\, which should show Language server version: 2.32.2.

If you’re still on 1.5.9, fully close Antigravity and reopen it so the auto-updater runs, then restart the IDE once more after it finishes.

One caution: if you applied the main.js / workbench / product.json patches from earlier in this thread, undo them. Restore the .bak files or reinstall the official build. The update fixes the issue without them, and the main.js patch weakens a security check on webviews.

Thanks @dllhell and @Ritesh_Dhawade for the help :heart:.