Gemini CLI error
Gemini CLI: You must be a named user on your organization's Gemini Code Assist...
You must be a named user on your organization's Gemini Code Assist Standard edition subscription to use this service. Please contact your administrator to request an entitlement to Gemini Code Assist Standard edition.Status: WorkaroundLast verified 3 documented fixes2 sources
What it means
A 403 PERMISSION_DENIED returned during sign-in or on the first request: the CLI is checking for an organization (Standard edition) subscription and the signed-in account has no entitlement.
Causes
- Per the official troubleshooting guide, Gemini CLI detected the GOOGLE_CLOUD_PROJECT or GOOGLE_CLOUD_PROJECT_ID environment variable; setting these forces an organization subscription check, which fails for an individual Google account not linked to an organizational subscription.
- Maintainer (cornmander, #13108): it looks like the user is trying to use the Standard (paid) tier of Gemini Code Assist without a license.
How to fix it
- Fix 1.
Individual users: unset GOOGLE_CLOUD_PROJECT and GOOGLE_CLOUD_PROJECT_ID, and remove them from shell configuration files (for example .bashrc, .zshrc) and any .env files. If that does not resolve it, try a different Google account.
Terminalunset GOOGLE_CLOUD_PROJECT GOOGLE_CLOUD_PROJECT_ID - Fix 2.
Organizational users: contact your Google Cloud administrator to be added to your organization's Gemini Code Assist subscription.
- Fix 3.
Maintainer guidance in #13108: email gemini-code-assist-user-feedback@google.com with information about the Google account you are using.
More Gemini CLI errors
All 19 Gemini CLI errorsFailed to sign in. Message: Your current account is not eligible... because it is not currently available in your location.Status: By designFailed to sign in. Message: Request contains an invalid argumentStatus: WorkaroundUNABLE_TO_GET_ISSUER_CERT_LOCALLY or unable to get local issuer certificateStatus: WorkaroundThis account requires setting the GOOGLE_CLOUD_PROJECT or GOOGLE_CLOUD_PROJECT_ID env var. See https://geminicli.com/docs/get-started/authentication/#set-gcpStatus: By designInvalid Google Cloud Project ID: "<projectId>". The GOOGLE_CLOUD_PROJECT (or GOOGLE_CLOUD_PROJECT_ID) environment variable must be set to your string-based Project ID (e.g., "my-project-123"), not your numeric Project Number. Please update your environment variables.Status: By designFailed to login. Message: Precondition check failed.Status: Fixed in releaseYou are currently configured to use a Google Cloud Project but lack a Gemini Code Assist license. Please contact your administrator to request a license.Status: WorkaroundFailed to sign in. Message: You do not have a valid license of this product. Please contact your administrator to request a license. If you are not an enterprise user and believe you are receiving this message as an error, please try using the latest version and logging in again.Status: Open
Related reading
- Do Your Agent Hooks Fail Open? Claude Code vs Codex vs Cursor vs Gemini CLIA guard hook that crashes, times out or points at a missing script lets the tool call through by default in Claude Code. v2.1.295 adds onFailure: block. Here is what each coding agent does when your policy hook breaks, with real test runs.
- How to Keep API Keys Away From Your AI Coding Agent: Claude Code vs Codex vs Cursor vs Gemini CLIA deny rule on .env stops cat but not a Python one-liner. Here are the three layers that actually keep secrets out of a coding agent's context - file rules, environment scrubbing and credential masking - and what Claude Code, Codex, Cursor and Gemini CLI give you for each, with real test runs.
- Headless AI Coding Agents in CI: Claude Code, Codex CLI, Gemini CLI, and opencode ComparedHeadless AI coding agents in CI compared: Claude Code, Codex CLI, Gemini CLI, and opencode on invocation flags, sandboxing, auth, and output formats.
- Gemini CLI to Antigravity CLI Migration Guide: The June 18 DeadlineGemini CLI to Antigravity CLI migration guide: install, migrate config, update scripts and CI, and avoid the silent MCP failure that breaks tool calls.
- Gemini CLI Guide: 1M Token Context and Who Can Still Use ItGemini CLI puts a 1 million token context in your terminal but now only serves paid Gemini API, Vertex AI and Code Assist users. Setup and TypeScript workflow.
FAQ
What does "You must be a named user on your organization's Gemini Code Assist..." mean in Gemini CLI?
A 403 PERMISSION_DENIED returned during sign-in or on the first request: the CLI is checking for an organization (Standard edition) subscription and the signed-in account has no entitlement.
How do I fix "You must be a named user on your organization's Gemini Code Assist..."?
There are 3 documented fixes. Start with the first: Individual users: unset GOOGLE_CLOUD_PROJECT and GOOGLE_CLOUD_PROJECT_ID, and remove them from shell configuration files (for example .bashrc, .zshrc) and any .env files. If that does not resolve it, try a different Google account.
Is this Gemini CLI error fixed?
Status: Workaround. No release removes the cause. The documented fixes work around it. Affected versions: Reported on 0.16.0-preview.2 (#13108); docs entry applies to current releases
Sources
Last verified against 2 sources: official docs, maintainer replies and release notes.
Newsletter
Fixes for the tools you use, weekly
One email per week. New coding agent releases, what broke, and how developers are working around it.