Improve token setup: keychain prompt + env var fallback#8
Merged
Conversation
The userConfig prompt should fire during plugin enable, but may not always trigger. Error message now tells users to disable/re-enable the plugin (triggers keychain prompt) or fall back to env var. README updated with both paths. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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.
Summary
bootstrap.shto guide users to disable/re-enable the plugin (triggers the keychain prompt) or setSOCKET_API_TOKENas an env varContext
The
userConfigwithsensitive: trueis designed to prompt during install and store in the system keychain. However, the prompt doesn't always fire. This gives users two clear paths to configure the token.🤖 Generated with Claude Code