Issue Station
Sign In
Tools hereToolbox

gemini-cli - 💡(How to fix) Fix gemini-cli installations done through brew having Keychain perpetually unavailable [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
google-gemini/gemini-cli#25864•Fetched 2026-04-24 06:13:50
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Author
ebartiebarti
Participants
ebartiebarti
Timeline (top)
labeled ×1

Code Example

> /about
CLI Version                              0.39.0                                                                      │
│ Git Commit                               398f78dca                                                                   │
RAW_BUFFERClick to expand / collapse

What happened?

Initially I installed gemini-cli via homebrew, but any time an extension had a sensitive variable it would fail to store it in the keychain, defaulting to file storage.

When I switched to npm installed gemini-cli, everything works as designed.

What did you expect to happen?

Either we have feature parity on using keychain on homebrew VS npm installed versions, or a disclaimer is added that keychain will not be used to store sensitive variables.

Client information

<details> <summary>Client Information</summary>

Run gemini to enter the interactive CLI, then run the /about command.

> /about
CLI Version                              0.39.0                                                                      │
│ Git Commit                               398f78dca                                                                   │
</details>

Login information

Auth Method : vertex-ai

Anything else we need to know?

No response

extent analysis

TL;DR

The issue with keychain storage for sensitive variables in gemini-cli may be resolved by using the npm-installed version instead of the homebrew version.

Guidance

  • The homebrew version of gemini-cli has issues with storing sensitive variables in the keychain, while the npm version works as expected.
  • To verify the issue, try installing gemini-cli via npm and check if sensitive variables are stored correctly in the keychain.
  • If using the npm version is not feasible, consider adding a disclaimer about the keychain limitation in the homebrew version.
  • Check the gemini-cli documentation for any known issues or workarounds related to keychain storage on different installation methods.

Notes

The exact cause of the issue is unclear, but the difference in behavior between the homebrew and npm versions suggests a potential installation or dependency-related problem.

Recommendation

Apply workaround: Use the npm-installed version of gemini-cli to ensure feature parity and correct keychain storage for sensitive variables.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#installation#tensor shape#autograd error#model save/load

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING