Gemini CLI / AI Coding Tools

Gemini CLI — --list-sessions Ignores Saved OAuth Auth State, Requires GEMINI_API_KEY

Fix gemini --list-sessions crashing when GEMINI_API_KEY is not set despite saved OAuth auth Includes evidence for Gemini CLI troubleshooting demand.

Source-backed Last updated May 12, 2026 1 source Needs local verification

Category: AI Coding Tools
Error signature: gemini --list-sessions ignores saved /auth state and strictly requires GEMINI_API_KEY env var
Quick fix: Verify the account session, API key, provider settings, and environment where the failing tool is running.
Updated: May 12, 2026
Verification status: Source-backed
Evidence: 1 public source URL

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for Gemini CLI, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

gemini --list-sessions ignores saved /auth state and strictly requires GEMINI_API_KEY env var is a Gemini CLI failure pattern reported for developers trying to fix gemini --list-sessions crashing when gemini_api_key is not set despite saved oauth auth. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Official Gemini CLI issue #26906 (2026-05-12) reports --list-sessions ignores internally saved OAuth authentication state and crashes without GEMINI_API_KEY env var. Main gemini command works fine with saved auth, but --list-sessions uses different auth resolution logic.

Common causes

Developers who authenticated Gemini CLI via OAuth (/auth command) find that --list-sessions ignores the saved auth state and crashes unless GEMINI_API_KEY is explicitly set in the shell. This breaks the core workflow of session management after OAuth login.
Official Gemini CLI issue #26906 (2026-05-12) reports --list-sessions ignores internally saved OAuth authentication state and crashes without GEMINI_API_KEY env var. Main gemini command works fine with saved auth, but --list-sessions uses different auth resolution logic.

Quick fixes

Confirm the exact error signature matches gemini --list-sessions ignores saved /auth state and strictly requires GEMINI_API_KEY env var.
Check the Gemini CLI account, local tool state, and provider configuration involved in the failing workflow.
Verify the account session, API key, provider settings, and environment where the failing tool is running.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match gemini --list-sessions ignores saved /auth state and strictly requires GEMINI_API_KEY env var exactly before applying the quick fix.
Compare the failing environment with Gemini CLI versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does gemini --list-sessions ignores saved /auth state and strictly requires GEMINI_API_KEY env var mean in Gemini CLI?

gemini --list-sessions ignores saved /auth state and strictly requires GEMINI_API_KEY env var indicates the workflow described by "Gemini CLI — --list-sessions Ignores Saved OAuth Auth State, Requires GEMINI_API_KEY" failed in a AI Coding Tools context. Start by confirming the exact signature and the component that emitted it.

What should I check first for gemini --list-sessions ignores saved /auth state and strictly requires GEMINI_API_KEY env var?

Check whether this cause matches your environment: Developers who authenticated Gemini CLI via OAuth (/auth command) find that --list-sessions ignores the saved auth state and crashes unless GEMINI_API_KEY is explicitly set in the shell. This breaks the core workflow of session management after OAuth login.

Is the gemini --list-sessions ignores saved /auth state and strictly requires GEMINI_API_KEY env var guidance source-backed?

The "Gemini CLI — --list-sessions Ignores Saved OAuth Auth State, Requires GEMINI_API_KEY" page is labeled source-backed. It has 1 public source URL from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for gemini --list-sessions ignores saved /auth state and strictly requires GEMINI_API_KEY env var?

For "Gemini CLI — --list-sessions Ignores Saved OAuth Auth State, Requires GEMINI_API_KEY", avoid applying "Verify the account session, API key, provider settings, and environment where the failing tool is running." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging gemini --list-sessions ignores saved /auth state and strictly requires GEMINI_API_KEY env var?

For "Gemini CLI — --list-sessions Ignores Saved OAuth Auth State, Requires GEMINI_API_KEY", collect the failing Gemini CLI command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.