Document macOS keychain prompts and update the AGENTS.md auth command list - #61
Merged
sionsmith merged 2 commits intoAug 19, 2026
Merged
Conversation
docs/troubleshooting.md gains a macOS keychain section alongside the existing Windows and Linux keyring sections: why grants bind to the binary signature, why upgrades and source builds re-prompt, and the local re-signing workaround. AGENTS.md's auth command list catches up with refresh, consent-url, and doctor, and the development gotchas note the per-binary keychain grant behavior for contributors testing against the real keychain. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NXWLJ9g87M3GtLSACr2gmi
Co-Authored-By: Claude Fable 5 <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
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.
Documentation only. No code changes.
docs/troubleshooting.mdgains a "macOS keychain prompts" section next to the existing Windows and Linux keyring sections. It explains the cause: macOS binds keychain access grants to the exact code signature of the binary, the released binaries are ad-hoc signed, so every upgrade or source build counts as a different application and prompts again, and "Always Allow" does not carry over. It shows how to inspect the stored items withsecurity find-generic-password -s teams-cli, and documents a workaround: re-sign the binary with a stable self-signed code-signing certificate after each upgrade or build.AGENTS.mdgets two small updates. The auth command inventory addsrefresh,consent-url, anddoctor, which shipped in earlier releases but were missing from the list. The development gotchas note that each local build triggers a fresh keychain prompt on macOS for the same signature reason, with a pointer to the new troubleshooting section and toTEAMS_CLI_DISABLE_KEYRING=1for tests.🤖 Generated with Claude Code
https://claude.ai/code/session_01NXWLJ9g87M3GtLSACr2gmi