Agent not working in recently updated Antigravity Version 1.20.3

Google Antigravity
1

I get a “Could not start conversation” error and it is stuck with a spinning circle and “Agent Loading” message

2026-03-06 08:59:35.727 [info] [Manager] [LsClient][lsClientState] {“timestamp”:“2026-03-06T13:59:35.336Z”,“activeTrajectory”:{“isLocal”:false,“hasSpecificClient”:false,“hasLocalFallback”:true,“isUsingFallback”:false},“trajectoryState”:{“hasCascadeState”:false,“hasTrajectory”:false},“lsClientManagers”:[{“workspaceUri”:“file:///Users/user/Documents/code/app.code-workspace”},{“workspaceUri”:“file:///Users/user/.gemini/antigravity/playground/ecliptic-belt”}],“subscriptions”:[]} (/Applications/Antigravity.app/Contents/Resources/app/out/jetskiAgent/main.js:3749)

2026-03-06 08:59:35.727 [info] [Manager] [LsClient][ERROR] Trajectory loading timeout exceeded for workspace: file:///Users/user/Documents/code/app.code-workspace (/Applications/Antigravity.app/Contents/Resources/app/out/jetskiAgent/main.js:3749)

Antigravity Version: 1.20.3
VSCode OSS Version: 1.107.0
Commit: 98d96766f768718ad6d450edb79e635b58373f9f
Date: 2026-03-06T00:31:02.617Z
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.3.0
Language Server CL: 879285883

2

Hi @knotmine,

The agent is hitting a Trajectory loading timeout exceeded error for your app.code-workspace. This typically happens when the agent’s LsClient fails to initialize in time. You can try the following workaround and let us know if it resolves

  • Instead of opening the .code-workspace file, try opening just one of your project folders directly via File > Open Folder…
  • Attempt to start a conversation in the Agent Manager again
3

That works.

But wanted to combine 2 folders into a workspace.

1 Like
4

I am having the same Trajectory loading issue, yet I am opening my project folders directly and it is not working. I just am trying out this product for the first time and the fact that I have not been able to have a single conversation with the AI is disappointing.

1 Like
5

Have this problem as well

6

I have that problem, too. Same error log.