Multi-root Workspace is not recognized by agent in Antigravity Visual Studio Code Extension

In multi-root workspace (by opening a .code-workspace file), the <user_information> block provided to the agent is not refreshed.

This stale context causes the LLM to hallucinate that it lacks permissions for the newly added directories, forcing it to fall back to terminal commands (bash/powershell) instead of using native file tools.

Evidence / Logs: Here is the exact <user_information> block injected into the LLM context, which still shows only one workspace, even after the .code-workspace file (which includes a second G:/ drive) was successfully loaded and active in the IDE:

<user_information>
The USER's OS version is windows.
Active Workspaces:
- c:\Users\[USER]\OneDrive\Documentos\agents\queonda-agent
Command Working Directory: c:\Users\[USER]\OneDrive\Documentos\agents\queonda-agent
Code relating to the user's requests should be written in the locations listed above. Avoid writing project code files to tmp, in the .gemini dir, or directly to the Desktop and similar folders unless explicitly asked.
App Data Directory: C:\Users\[USER]\.gemini\antigravity
Conversation ID: [REDACTED_UUID]
Artifact Directory Path: C:\Users\[USER]\.gemini\antigravity\brain\[REDACTED_UUID]
</user_information>

it should be

Active Workspaces:
- c:\Users\[USER]\OneDrive\Documentos\agents\queonda-agent
- g:\shared units\agent\output

Steps to Reproduce:

  1. Open a Multi-root Workspace in VS Code (File > Open Workspace from File...) that contains at least two distinct folders (e.g., C:\Project and a secondary drive like G:\Outputs).
  2. Start an Antigravity chat session.
  3. Ask the agent: “Please list your Active Workspaces based on your <user_information> block.”
  4. Observation 1 (Incomplete LLM Context): The agent only lists the primary folder (e.g., C:\Project). It completely omits the secondary folder. Because the LLM thinks the second folder is out of bounds, if asked to write a file there, it will proactively avoid the native write_to_file tool and fall back to terminal commands (run_command) out of caution.

Expected Behavior: When generating the <user_information> block, Antigravity should iterate through all active folders in a Multi-root Workspace (i.e., all entries in vscode.workspace.workspaceFolders) and list every single one of them under Active Workspaces. The LLM needs to know its complete authorized boundaries so it can confidently use native file editing tools across all workspace roots.

Environment:

  • OS: Windows
  • IDE: VS Code / Antigravity IDE
  • Workspace type: Multi-root Workspace (.code-workspace)

Hi @molavec,

If it is possible, could you please share the screen recording by showing how to reproduce this issue?

I just ran into the same issue- it has previously worked so I’m not sure why it didn’t this time. My workspace has the base folder (a C# Minimal API project) and a sub-folder (Lit web components based web app) as folders in the code-workspace file. The project that is “working” is the sub-folder and that is also listed as the first item in the code-workspace. The second project is no longer recognized.