Current behavior
When the user selects an auth method at startup or via `/auth`, the prompt lists the two options (Google sign-in vs API key) but does not explain that some tools are only available with API key auth.
The README documents this:
`google_web_search` and `web_fetch` currently require `GEMINI_API_KEY` auth.
But the interactive auth chooser does not surface this information.
Proposed change
When presenting the auth selection prompt, add a brief note indicating which capabilities differ between auth methods. For example:
1. Google sign-in (OAuth)
2. Gemini API key
Note: google_web_search and web_fetch require API key auth.
The exact wording and placement can be decided during implementation. The goal is that users make an informed choice without needing to read the README first.
Relevant files
- `internal/authselect/` — prompt text generation
- `internal/ui/auth_command.go` — `/auth` UI flow
- `cmd/gemini-cli/auth_runtime.go` — startup auth prompt
Current behavior
When the user selects an auth method at startup or via `/auth`, the prompt lists the two options (Google sign-in vs API key) but does not explain that some tools are only available with API key auth.
The README documents this:
But the interactive auth chooser does not surface this information.
Proposed change
When presenting the auth selection prompt, add a brief note indicating which capabilities differ between auth methods. For example:
The exact wording and placement can be decided during implementation. The goal is that users make an informed choice without needing to read the README first.
Relevant files