# Antigravity #3501 "You Do Not Have a Valid License": 6 Causes > Antigravity #3501 on a personal account: reset the cached enterprise sign-in first. If every account fails with no VPN, it's a region or account block. - URL: https://blog.laozhang.ai/en/posts/antigravity-error-3501 - Published: 2026-10-23 - Updated: 2026-10-23 - Author: LaoZhang AI Team (https://blog.laozhang.ai/en/about) - Topic: Troubleshooting - Tags: Google Antigravity, Antigravity CLI, Error 3501, Gemini Code Assist, Troubleshooting --- Error #3501, "You do not have a valid license of this product", says your sign-in needs a paid enterprise seat, a Gemini Code Assist Standard or Enterprise license, and that the account has none. There is no "license" to buy for Antigravity that clears it, and the wording is often wrong about the cause. The same message comes back for six different rejections: a personal account cached as an enterprise one, the retired Gemini Code Assist tier for individuals, a country or VPN that fails Google's location check, an unverified age, a trial or bundled Google AI Pro plan, and use of the login outside Antigravity. The text is identical in every case, so the fix depends on where you see it and on your account. Start with the one cause you can fix on your own machine. Update the Antigravity App and CLI, run **Antigravity: Reset Onboarding** from the Command Palette (or `/logout` then `/login` in the Antigravity CLI), make sure `AGY_ADC_AUTH` isn't set, and pick your personal @gmail.com account at sign-in. Don't delete `~/.gemini`; rename folders instead, because that folder also holds your agent history. If you see #3501 in the Gemini Code Assist extension or Gemini CLI with a personal or AI Pro account, it is expected since June 18, 2026, and the fix is moving to Antigravity. If several personal accounts on the same computer all get #3501 with no VPN and no `AGY_ADC_AUTH`, stop reinstalling, because the rejection is on the account or region side. Two checks behind these steps were run on a real machine. On October 23, 2026, on a Mac running macOS 26.1 that had used the Antigravity IDE, `du -sh` and `ls` measured what deleting `~/.gemini` removes, and `env` plus `launchctl getenv` checked for `AGY_ADC_AUTH`. The #3501 error itself was not reproduced, and the Windows commands below come from forum moderator replies and were not run. Everything else is attributed where it appears: Google's docs, Google staff replies, forum moderator replies, or user reports. ## What #3501 means: an enterprise license check, not a product key The "license" in #3501 is a Gemini Code Assist Standard or Enterprise seat that an organization assigns, not a key you buy for the app. A Google staff member on the Google AI Developers Forum put it this way on September 24, 2026: the error "occurs when your sign-in is treated as needing an enterprise/business license, but no active license is found for the account" ([Google staff reply in the forum thread on #3501](https://discuss.ai.google.dev/t/184724)). For a personal Gmail account, that means something sent your sign-in down the enterprise path. The message also hides a second meaning. On September 9, 2026, Google staff said that when Antigravity rejects a connection because of region restrictions, it "throws this license error instead of clearly stating" that the region is unsupported, and apologized for the confusion ([Google staff reply on region rejections](https://discuss.ai.google.dev/t/182209)). So #3501 can mean "wrong account path" or "you aren't eligible here", and the text alone won't tell you which. In logs from the Antigravity CLI or Gemini CLI, the same rejection appears as an HTTP 403. Logs that users posted in the forum and on GitHub carry these fields, so you can match your own against them: ```json "code": 403, "status": "PERMISSION_DENIED", "reason": "SUBSCRIPTION_REQUIRED", "domain": "cloudaicompanion.googleapis.com" ``` ## Which #3501 cause is yours: match the surface, account and country Find the row that matches where the error appears and which account you use, then go to the step in the last column. The source of each cause is in brackets, because some come from Google's own pages and others only from forum moderators or user reports. | Where you see it and your setup | Likely cause | What to do | |---|---|---| | Gemini Code Assist extension in VS Code or JetBrains, or Gemini CLI, with a personal Gmail or Google AI Pro account | Gemini Code Assist stopped serving individuals and AI Pro on June 18, 2026 (Google deprecation page) | Move to Antigravity; resets won't help | | Personal Gmail in the Antigravity App, IDE or CLI that worked before, failing after an update or after you used a work or Google Cloud account | Sign-in cached as enterprise (Google staff) | Reset the sign-in and check `AGY_ADC_AUTH` | | Google Workspace account from your company or school | Antigravity's consumer sign-in is for personal accounts (Antigravity FAQ) | Sign in with a personal @gmail.com account | | Country on your Google account, or your physical location, not on Antigravity's list | Region rejection shown as #3501 (Google staff) | Not fixable on your computer | | VPN, proxy, TUN mode or split tunnel on | Location check fails (forum moderators) | Turn it off and connect directly | | Account under 18 or age never verified | Antigravity is 18+ (Antigravity FAQ); moderators list it as a #3501 trigger | Verify your age with Google | | Google AI Pro from a free trial, Jio, Pixel, a student offer or another bundle | Plan benefit not applied (moderator, one case); an X post claims bundles return #3501 (unconfirmed) | Contact Google One support or the partner | | Antigravity login used in Claude Code, OpenCode or scripts that call Antigravity's endpoints | Against the Antigravity terms (Antigravity FAQ); some users report a 403 #3501 afterward | Stop, and use an API key for other tools | The last row deserves one plain sentence: the Antigravity FAQ says using third-party software such as Claude Code, OpenClaw or OpenCode with an Antigravity login violates the Terms of Service and can get the account suspended, and it recommends a Gemini Enterprise or Google AI Studio API key for third-party agents ([Antigravity FAQ](https://antigravity.google/docs/faq)). ![Decision tree for Antigravity error #3501: Gemini Code Assist or Gemini CLI means it is expected since June 18, 2026; a Workspace account means sign in with personal Gmail; a VPN means turn it off; a break after an update or work sign-in means reset the cached sign-in; otherwise country, age or plan is decided on Google's side](https://blog.laozhang.ai/posts/en/antigravity-error-3501/img/which-cause-decision-tree.webp) ## Reset a stuck enterprise sign-in in the Antigravity App, IDE and CLI If you use a personal account in a supported country and the error started after an update or after a work sign-in, reset the cached sign-in in this order. These steps come from the Google staff reply of September 24, 2026, and later forum moderator replies; none of them deletes your data. 1. Update first. As of October 23, 2026, the latest releases on the [Antigravity changelog](https://antigravity.google/changelog) are App v2.25.0 (October 20) and CLI v1.4.0 (October 16); the CLI updates with `agy update`. Google notes that releases roll out gradually and can take a few days to reach everyone. 2. If `AGY_ADC_AUTH` is set, remove it and restart the CLI or app before signing in again, as Google staff advise. The commands are in the `AGY_ADC_AUTH` section below. 3. In the Antigravity App or IDE, open the Command Palette (Cmd+Shift+P on macOS, Ctrl+Shift+P on Windows and Linux) and run **Antigravity: Reset Onboarding**. It signs you out and restarts sign-in; a moderator adds that, unlike a plain sign-out, it clears the cached onboarding state. 4. In the Antigravity CLI, run `/logout`, then `/login`. 5. When the browser opens, choose your personal @gmail.com account, not an Enterprise, Workspace SSO or Google Cloud option. Turn off any VPN while you do this. 6. If you use the IDE and also have the standalone Antigravity App 2.x, Google staff suggested on September 28, 2026: open the App, sign in, finish the account verification or QR code scan when asked, then sign in to the IDE again. The changelog shows Google has been fixing exactly this kind of stuck state, which is why updating comes first. App v2.16.0 (September 22) fixed rejected enterprise credentials staying cached, v2.18.1 (September 28) fixed an interrupted enterprise sign-in being saved, CLI v1.1.28 (September 9) resets cached project and license data when you switch from a business account to a personal one, and CLI v1.2.9 (September 23) clears stuck partial enterprise credentials. No changelog entry names #3501 directly. If you're signed in and the problem is slow responses rather than #3501, see [Gemini 3.8 Flash Slow in Antigravity? Find the Delay Before Retrying](https://blog.laozhang.ai/en/posts/gemini-3-8-flash-antigravity-slow). ## Should you delete ~/.gemini? It held 689 MB of agent history on one Mac Rename the folders instead of deleting them, and only after Reset Onboarding has failed. A common forum suggestion for #3501 is to delete `~/.gemini` and the app's support folder, but that folder holds more than a session. On October 23, 2026, on a Mac running macOS 26.1 that had used the Antigravity IDE from December 2025 to January 2026, these commands showed what is inside: ```bash du -sh ~/.gemini/antigravity ~/.antigravity "$HOME/Library/Application Support/Antigravity" # 689M ~/.gemini/antigravity # 71M ~/.antigravity # 142M ~/Library/Application Support/Antigravity ls ~/.gemini/antigravity # brain browser_recordings code_tracker conversations implicit # mcp_config.json playground scratch user_settings.pb ... ``` `~/.gemini/antigravity` held the agent's conversations, 83 files of "brain" artifacts and 4,302 browser recording files, plus your MCP configuration. The rest of `~/.gemini` belongs to Gemini CLI: its account file, settings, `GEMINI.md` and MCP OAuth tokens, so deleting the whole folder also signs you out of Gemini CLI and your MCP servers. The browser-style sign-in state (Cookies, Local Storage, Session Storage) was in `~/Library/Application Support/Antigravity`. That Mac ran an older app version and #3501 wasn't present on it, so the layout on App v2.25.0 may differ, and renaming wasn't tested as a #3501 fix. ![Folder sizes measured on one Mac: ~/.gemini/antigravity 689 MB of agent history, Application Support/Antigravity 142 MB of sign-in state, ~/.antigravity 71 MB, with the two folders to rename to -backup instead of deleting](https://blog.laozhang.ai/posts/en/antigravity-error-3501/img/gemini-folder-rename.webp) If Reset Onboarding didn't work and you want to start clean, quit Antigravity and rename rather than delete, so you can move the folders back: ```bash mv ~/.gemini/antigravity ~/.gemini/antigravity-backup mv "$HOME/Library/Application Support/Antigravity" "$HOME/Library/Application Support/Antigravity-backup" ``` On Windows, forum moderators say deleting `.gemini` or `%APPDATA%\Antigravity` doesn't remove the CLI's saved token, because it sits in Windows Credential Manager. Run `/logout` inside `agy`, or open Credential Manager → Windows Credentials and remove the entry `LegacyGeneric:target=gemini:antigravity`. Moderators suggest deleting `%APPDATA%\Antigravity`; renaming it to `Antigravity-backup` keeps the same option to roll back as on macOS. These Windows steps were not run. ## Check AGY_ADC_AUTH on macOS and Windows, including for GUI apps `AGY_ADC_AUTH` holds Google Cloud credentials, and according to Google staff and forum moderators, having it set forces the enterprise license check. Moderators add that on Windows it survives reinstalling and folder deletion. Check every place a variable can come from, because an app opened from the Dock or Start menu doesn't read the same settings as your terminal. On macOS, a GUI app launched from the Dock doesn't read `~/.zshrc`, but it does see variables set with `launchctl setenv`, so check both. These commands were run on October 23, 2026, on macOS 26.1: ```bash env | grep -E '^(AGY_|GOOGLE_CLOUD_PROJECT|GOOGLE_APPLICATION_CREDENTIALS|GOOGLE_GENAI_USE_VERTEXAI|CLOUDSDK_)' launchctl getenv AGY_ADC_AUTH ``` Both returned nothing on that Mac, which is what a personal setup should look like. If the first command prints `AGY_ADC_AUTH`, delete its `export` line from `~/.zshrc` or `~/.bash_profile` and open a new terminal; if `launchctl getenv` prints a value, run `launchctl unsetenv AGY_ADC_AUTH`, then quit and reopen Antigravity. On Windows, check both the user and system scopes in PowerShell. These commands come from forum moderator replies and were not run: ```powershell [Environment]::GetEnvironmentVariable('AGY_ADC_AUTH','User') [Environment]::GetEnvironmentVariable('AGY_ADC_AUTH','Machine') ``` If either prints a value, remove the variable in System Properties → Environment Variables. `Remove-Item Env:\AGY_ADC_AUTH`, which moderators also suggest, clears it only for the current PowerShell window. The `env` line also lists `GOOGLE_CLOUD_PROJECT` and `GOOGLE_APPLICATION_CREDENTIALS`, which matter for Gemini CLI's Google Cloud project login. Google staff name only `AGY_ADC_AUTH` as an Antigravity trigger, so treat the others as worth checking, not as a confirmed cause. ## #3501 in Gemini Code Assist or Gemini CLI: expected since June 18, 2026 In the Gemini Code Assist extension for VS Code or JetBrains, or in Gemini CLI, #3501 on a personal Gmail or Google AI Pro account is the expected result, not a bug. Google's [Gemini Code Assist deprecations page](https://developers.google.com/gemini-code-assist/docs/deprecations) says that after June 18, 2026, the IDE extensions and Gemini CLI stopped serving requests for Google AI Pro and Ultra and for Gemini Code Assist for individuals. The extension now works only with a paid Standard or Enterprise license, and the same page says new Standard and Enterprise subscriptions can't be bought after October 9, 2026. So resetting, reinstalling and switching accounts won't bring a personal account back in those tools. A forum moderator's advice on October 1, 2026, matches the deprecation page: to use your AI Pro plan, switch to Antigravity, or in VS Code to the official Antigravity for Visual Studio Code extension. ## Is it your country or a VPN? #3501 as a region rejection If the country on your Google account or your physical location isn't on Antigravity's list, #3501 is a region rejection, and nothing on your computer will clear it. The [Antigravity FAQ](https://antigravity.google/docs/faq) lists the countries and territories where it is available; as of October 23, 2026, the list includes the United States, Mexico, Japan, South Korea, India and Ukraine, and does not include mainland China, Hong Kong, Russia, Belarus or Iran. The FAQ also tells you to check the country shown on the [Google Terms of Service page](https://policies.google.com/terms) while signed in, and to file the [Google country association form](https://policies.google.com/country-association-form) only if that country is wrong for where you live. Forum moderators describe three more ways a supported user fails the same check. A VPN, proxy, TUN mode or split tunnel can make location verification fail even when the exit looks like a supported country, for example when IPv6 traffic leaves by a separate route. A recently corrected Terms of Service country can take 24–48 hours or more to reach all of Google's services. And an older Google Payments profile tied to an unsupported country can trip the check. A VPN is therefore a cause of #3501, not a fix; turn it off and connect directly. The related message "Your current account is not eligible for Antigravity", or "not currently available in your location", is the same region check stated plainly. A moderator explained that when the location check blocks a session, the free tier is never set up for it, so the quota request that follows fails with #3501. ## Paying for Google AI Pro and still blocked: trial, Jio, Pixel or student plans A Google AI Pro plan doesn't protect you from #3501, and how you got the plan matters. The Antigravity FAQ says Gemini 4 Argon, Claude Opus 5.5 and Claude Sonnet 5.5 need a paid Google AI Pro or Ultra subscription and are not included in free trials; trial users have to cancel the trial and switch to paid Pro, or upgrade to Ultra. Plans from partners, Pixel Pass or Google Fi are managed through Google One. For a partner plan, a forum moderator answered a Jio-provided AI Pro case on October 8, 2026: Antigravity reads the plan benefit from your Google subscription and may not apply it when the plan's issuing country differs from your account country. Antigravity can't fix that manually, so contact Google One support or the partner, or subscribe to AI Pro directly in your own country. Meanwhile Antigravity still works on the free Starter Quota. In that case the plan showed up as "ineligible for higher rate limits", and the #3501 the user saw came from calling Antigravity's internal endpoints directly, which the moderator said to stop. A post on X by @StatsWire on October 17, 2026, claims Google tags bundled Pixel, Jio and student AI Pro accounts as trial or promotional, returning HTTP 403 #3501 and blocking Gemini 4 Argon and Claude 5.5. Google hasn't confirmed this; only the "not in free trials" part matches the FAQ. For which plan gets which model on which surface, see [Gemini 4 Argon Usage Limits: Pro vs Ultra, Resets, API Credits](https://blog.laozhang.ai/en/posts/gemini-4-argon-usage-limits). ## When to stop retrying #3501 and what to send Google Stop resetting when several personal accounts on the same computer all get #3501 with no VPN and no `AGY_ADC_AUTH` set. A forum moderator wrote on October 8, 2026, that this pattern "typically indicates a server-side region or account eligibility rejection". The reasoning behind stopping is an inference from the staff and moderator replies, not a Google statement: Reset Onboarding, `/logout`, removing `AGY_ADC_AUTH`, clearing the Credential Manager entry and updating only touch the cached enterprise path, so they can't change a country, age or plan decision made on Google's side. #3501 reports also come in waves. The Google AI Developers Forum had about 45 topics on #3501 as of October 23, 2026, bunched around June 22, August 19–28 and September 24–29 (about 25 topics in those six days), with new ones as late as October 15. No Google status incident matching those waves could be found as of October 23, 2026, though that doesn't mean none was recorded. Individual reports vary: one user's account worked again on October 3 with no specific fix after days of trying, then broke again on October 13 after opening Antigravity through a VPN by mistake, and another user reported older personal accounts stuck while newly created ones worked. Those are single cases, not a rule. When you stop, send one report with the details Google staff and moderators ask for, plus what you already tried: - [ ] The Error ID shown under the message, and the Trajectory ID if one appears - [ ] Surface (Antigravity App 2.x, IDE or CLI), its version and your OS - [ ] Your physical country and the country on your Google Terms of Service page - [ ] Free (Starter Quota), Google AI Pro or Ultra, and whether the plan came from a trial or partner - [ ] What you already tried: Reset Onboarding, `/logout`, `AGY_ADC_AUTH`, VPN off - [ ] Logs as a .txt file from Help > Toggle Developer Tools > Console or View > Output > Antigravity Language Server, or a screenshot, with your email address removed Post it through the communities linked on the [Antigravity support page](https://antigravity.google/support), which point to the Google AI Developers Forum. If the problem is a plan that isn't recognized, Google One support is the place, because Antigravity can't change the subscription itself. ## Sources External pages this guide links to, in the order they appear. Last updated 2026-10-23. - [Google staff reply in the forum thread on #3501](https://discuss.ai.google.dev/t/184724) (discuss.ai.google.dev) - [Google staff reply on region rejections](https://discuss.ai.google.dev/t/182209) (discuss.ai.google.dev) - [Antigravity FAQ](https://antigravity.google/docs/faq) (antigravity.google) - [Antigravity changelog](https://antigravity.google/changelog) (antigravity.google) - [Gemini Code Assist deprecations page](https://developers.google.com/gemini-code-assist/docs/deprecations) (developers.google.com) - [Google Terms of Service page](https://policies.google.com/terms) (policies.google.com) - [Google country association form](https://policies.google.com/country-association-form) (policies.google.com) - [Antigravity support page](https://antigravity.google/support) (antigravity.google)