Error in Antigravity - Not Generating Commit Message

Google AI Studio
, , ,
48

Same issue for me the UI throws the same error, the Agent can generate commit messages

Antigravity Version: 1.13.3
VSCode OSS Version: 1.104.0
Commit: 94f91bc110994badc7c086033db813077a5226af
Date: 2025-12-19T21:03:14.401Z (3 wks ago)
Electron: 37.3.1
Chromium: 138.0.7204.235
Node.js: 22.18.0
V8: 13.8.258.31-electron.0
OS: Darwin arm64 25.2.0
Language Server CL: 846830895

49

I tried reporting this issue using the Provide Feedback section under Settings, but the reporting feature itself is not functioning. :joy:

3 Likes
50

Same Issue. Sharing my version details as well

Antigravity Version: 1.13.3
VSCode OSS Version: 1.104.0 (user setup)
Commit: 94f91bc110994badc7c086033db813077a5226af
Date: 2025-12-19T21:03:14.401Z
Electron: 37.3.1
Chromium: 138.0.7204.235
Node.js: 22.18.0
V8: 13.8.258.31-electron.0
OS: Windows_NT x64 10.0.26200
Language Server CL: 846830895

1 Like
51

Same here
M2Max
26.1 (25B78)

Erros in extension Antigravity window
Error generating commit message: [unknown] error grabbing LLM response: stream error

ENOENT: no such file or directory, rename ‘/Users/perso/.gemini/antigravity/user_settings.pb.tmp.extHost’ → ‘/Users/perso/.gemini/antigravity/user_settings.pb’

Messages (4)

Menu item references a command antigravity.importAntigravitySettings which is not defined in the ‘commands’ section.

Antigravity Version: 1.13.3
VSCode OSS Version: 1.104.0
Commit: 94f91bc110994badc7c086033db813077a5226af
Date: 2025-12-19T21:03:14.401Z (3 wks ago)
Electron: 37.3.1
Chromium: 138.0.7204.235
Node.js: 22.18.0
V8: 13.8.258.31-electron.0
OS: Darwin arm64 25.1.0
Language Server CL: 846830895

I lose a lot of time with these issues. Uninstall, delete all preferences, install again.

1 Like
52

same issue, please fix

53

The same problem
macbook air m4

54

Same here. MacBook Pro M3 Pro Max.
MacOS tahoe 26.2.

Antigravity Version: 1.13.3
VSCode OSS Version: 1.104.0
Commit: 94f91bc110994badc7c086033db813077a5226af
Date: 2025-12-19T21:03:14.401Z
Electron: 37.3.1
Chromium: 138.0.7204.235
Node.js: 22.18.0
V8: 13.8.258.31-electron.0
OS: Darwin arm64 25.2.0
Language Server CL: 846830895

Error generating commit message: [unknown] error grabbing LLM response: stream error

55

Same here. Ubuntu 24.04.

56

same here. with os windows 11 in WSL ubuntu 24.04 folder

57

Same here, MacOS, 26.1

58

Same here. I got to the point where I open Cursor just to generate the commit message :joy:

1 Like
59

The same is happening with me, i ask ai to generate a commit message, merge to dev, and push.

60

Same here, Windows 11 x64.

61

Same here; M1 on Sequoia,

Antigravity Version: 1.13.3
VSCode OSS Version: 1.104.0
Commit: 94f91bc110994badc7c086033db813077a5226af
Date: 2025-12-19T21:03:14.401Z (3 wks ago)
Electron: 37.3.1
Chromium: 138.0.7204.235
Node.js: 22.18.0
V8: 13.8.258.31-electron.0
OS: Darwin arm64 24.6.0
Language Server CL: 846830895

62

Subject: :shield: EMERGENCY WORKAROUND: Root Cause and Fix for v1.13.3 “unleashWrapper is nil” Error

Hi everyone,

After coordinating with my team and analyzing the logs (specifically from @dev_noersy and @Milad_Alem), we have identified the most probable issue. This is a Level 5 Code Regression in version 1.13.3 affecting all architectures (macOS Tahoe, Windows 11, and Linux).

The Diagnosis:

The error “unleashWrapper is nil” indicates a race condition. The extension is trying to check your token limits (via the Unleash feature-flag client) BEFORE the Authentication handshake is finished. Because the wrapper hasn’t initialized yet, it hits a null pointer and kills the LLM stream.

Tactical Workarounds (Do these until a hotfix is pushed):

1. The “60-Second Cold Start”: Launch Antigravity and DO NOT click “Generate Commit” immediately. Wait at least 60 seconds to allow the background Auth and Feature-Flag threads to sync. This bypasses the race condition on most systems.

2. The Settings Flush (For macOS/Linux): If you see the ENOENT rename error, your settings file is stuck in a temp state. Close the app and run:

rm -rf ~/.gemini/antigravity/user_settings.pb.tmp.extHost

3. The “Possible Workaround” (CLI):

If you are blocked, use the Gemini CLI or standard git commit in the terminal for now. The LLM logic in the IDE is currently gated by this broken initialization wrapper.

Message for Google Devs:

The LanguageServerService needs an initialization guard on the unleashWrapper. It should gracefully degrade to a default token limit if the wrapper is nil instead of throwing a stream-killing error.

~CMD.Proton/The Lab :vulcan_salute:

1 Like
63

Same here on Windows 10 - AntiGravity version 1.13.3
Described workaround via rm -rf ~/.gemini/antigravity/user_settings.pb.tmp.extHost had no effect.

64

same here on windows 10:

Antigravity Version: 1.13.3
VSCode OSS Version: 1.104.0 (user setup)
Commit: 94f91bc110994badc7c086033db813077a5226af
Date: 2025-12-19T21:03:14.401Z
Electron: 37.3.1
Chromium: 138.0.7204.235
Node.js: 22.18.0
V8: 13.8.258.31-electron.0
OS: Windows_NT x64 10.0.19045
Language Server CL: 846830895

65

Thanks for the info. I did wait a lot before but it did not help. I’ll test other workarounds but honestly, I’ve switched to asking the agent itself to commit (during the conversation) and it’s better because it adds descriptions to the commits as, well. The generate button only generates a message.

I’m wondering how it’s a race condition on Auth if the agent itself is working fine and is clearly passed the auth part?

Milad (ex-Google)

1 Like
66 
2026-01-12 10:12:04.396 [info] W0112 10:12:04.396016 87493 log_context.go:106] Cache(userInfo): Singleflight refresh failed: You are not logged into Antigravity.
2026-01-12 10:12:04.425 [info] (Antigravity) 2026-01-12 10:12:04.425 [INFO]: Language server started
2026-01-12 10:12:04.429 [info] W0112 10:12:04.419171 87493 client.go:135] failed to set auth token
2026-01-12 10:12:04.429 [info] W0112 10:12:04.421841 87493 log_context.go:106] Cache(userInfo): Singleflight refresh failed: You are not logged into Antigravity.
2026-01-12 10:12:04.429 [info] I0112 10:12:04.429329 87493 server.go:1496] initialized server successfully
2026-01-12 10:12:04.472 [info] 2026/01/12 10:12:04 http: TLS handshake error from 127.0.0.1:60580: EOF
2026-01-12 10:12:04.474 [info] 2026/01/12 10:12:04 http: TLS handshake error from 127.0.0.1:60579: EOF
2026-01-12 10:12:04.497 [info] (Antigravity) 2026-01-12 10:12:04.497 [INFO]: LS lspClient started successfully
2026-01-12 10:12:06.422 [info] E0112 10:12:06.422348 87493 log.go:354] queryText was truncated because it was longer than the allowed byte length 1500
2026-01-12 10:12:21.927 [info] E0112 10:12:21.927639 87493 log.go:354] error converting token count to int: unleashWrapper is nil
2026-01-12 10:12:22.846 [info] E0112 10:12:22.846036 87493 log.go:362] Failed to generate commit message: error grabbing LLM response: stream error
2026-01-12 10:12:22.848 [info] E0112 10:12:22.848186 87493 interceptor.go:74] /exa.language_server_pb.LanguageServerService/GenerateCommitMessage (unknown): error grabbing LLM response: stream error
2026-01-12 10:12:41.131 [info] E0112 10:12:41.131535 87493 log.go:354] error converting token count to int: unleashWrapper is nil
2026-01-12 10:12:41.804 [info] E0112 10:12:41.804377 87493 log.go:362] Failed to generate commit message: error grabbing LLM response: stream error
2026-01-12 10:12:41.806 [info] E0112 10:12:41.806698 87493 interceptor.go:74] /exa.language_server_pb.LanguageServerService/GenerateCommitMessage (unknown): error grabbing LLM response: stream error

I have reinstall Antigravity and wait for 2min , But! It don’t help, the editor throw error logs above and requst LLM stream still faild.

And I have already login as Pro user, why it tells that I’m not logged into ?
How long will you fix this error?

It has exist about one week !

67

Excellent question, @Milad_Alem. Here is why Chat works while Commits fail:

1. Service Decoupling: In Antigravity, the “Agent/Chat” and the “Commit Generator” likely use different gRPC interceptors. The Chat service may be checking Auth at the edge, while the Commit service has an additional “gatekeeper” (the unleashWrapper) that specifically checks for token quotas before it even talks to the LLM.

2. The Null Pointer: Even if you are “Authed,” if the specific internal object responsible for counting the tokens (unleashWrapper) failed to instantiate during the boot sequence, any feature that calls it (like Commit Gen) will crash. Chat might simply not be calling that specific wrapper yet, or it has a different fallback mechanism.

3. Async Initialization: It’s a “Race Condition” not of the Auth itself, but of the internal state. The Auth might be ‘Green,’ but the Feature-Flag client is still ‘Gray.’ If you trigger a commit while it’s in that ‘Gray’ state, it hits a nil reference.

Think of it like a starship: The main reactor (Auth) is online so the lights (Chat) are on, but the targeting computer (Unleash Wrapper) failed its boot sequence. You can talk to the crew, but you can’t fire the main phasers.

~CMD. Proton :vulcan_salute: