feat: use file-based token storage instead of keychain#8
Merged
Conversation
Replaces keyring with file-based storage at ~/.config/ghune/token with 600 permissions. This avoids repeated keychain password prompts on macOS for unsigned binaries.
This was referenced Jan 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
motivation
On macOS, unsigned binaries using the keychain trigger password prompts on every run due to code signing requirements. This makes the tool frustrating to use for local development builds.
change
keyringcrate withdirscrate for cross-platform config directory detection~/.config/ghune/token(or platform equivalent)0o600on Unix systems (owner read/write only)This approach matches how other CLI tools (gh, aws, gcloud) handle credential storage.
testing
0600on macOS/Linux