[Bug] Claude Code 2.1.120 bundled binary exits with code 1 on Antigravity spawn
Bug Description
Environment:
macOS, darwin-arm64
CLI: native 2.1.119 (commit 6f6855483975), /doctor OK
IDE host: Google Antigravity, using bundled anthropic.claude-code-2.1.120-darwin-arm64
Problem:
When Antigravity spawns the bundled claude binary (2.1.120), it immediately logs:
From claude: error: An unknown error occurred (Unexpected)
Error spawning Claude ... process exited with code 1
Same project, same machine: native claude 2.1.119 runs fine. /doctor reports “Diagnostics: OK”.
OAuth tokens are present (OAuth tokens found in secure storage).
No Python virtualenv leakage, MCP config reduced to { "mcpServers": {} }.
Logs from Antigravity:
text
2026-04-25 12:10:42.621 [info] AuthManager initialized
2026-04-25 12:10:42.621 [info] Claude code extension is now active?
2026-04-25 12:10:42.621 [info] MCP Server running on port 61271 (localhost only)
2026-04-25 12:10:42.621 [info] Getting authentication status
2026-04-25 12:10:42.621 [info] OAuth tokens found in secure storage
2026-04-25 12:10:42.621 [info] AuthManager initialized
...
2026-04-25 12:10:42.953 [info] Received message from webview: {"type":"launch_claude","channelId":"mhanwg7iyw","cwd":"/Users/marcparisotto/Desktop/HERMES/OpenWork","permissionMode":"acceptEdits","thinkingLevel":"default_on"}
2026-04-25 12:10:42.956 [info] Launching Claude on channel: mhanwg7iyw
2026-04-25 12:10:42.958 [info] Spawning Claude with SDK query function - cwd: /Users/marcparisotto/Desktop/HERMES/OpenWork, permission mode: acceptEdits, version: 2.1.120, /Users/marcparisotto/.antigravity/extensions/anthropic.claude-code-2.1.120-darwin-arm64/resources/native-binary/claude, resume: undefined
2026-04-25 12:10:42.997 [info] From claude: error: An unknown error occurred (Unexpected)
2026-04-25 12:10:43.003 [error] Error spawning Claude (on channel mhanwg7iyw): Error: Claude Code process exited with code 1
2026-04-25 12:10:43.004 [error] Failed to load config cache: Error: Claude Code process exited with code 1
Request:
Can you check for regressions in the 2.1.120 bundled binary / Antigravity integration that would cause this behavior while 2.1.119 CLI remains healthy?
Ideally, either:
Allow Antigravity to use the working native 2.1.119 binary, or
Patch/roll back the bundled 2.1.120 for this host.
Happy to run with extra debug flags or a canary build if that helps.
Environment Info
- Platform: darwin
- Terminal: Apple_Terminal
- Version: 2.1.119
- Feedback ID: c675563a-8fb9-4c1c-b0ad-ff409c5dcc87
Errors
[]This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗