Repository navigation
fix(scripts): fork install signs with Developer ID when the keychain has it - #52
Merged
Merged
Conversation
maschwenk
marked this pull request as ready for review
November 11, 2026 02:14
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.
1password in the T3 browser kept locking every time T3 restarted. turns out the 1password app only connects to a browser it trusts, and it was rejecting the fork because it's signed with an Apple Development cert (gatekeeper says rejected, helium says accepted / notarized developer id). so the extension ran standalone and lost its unlock on every restart
fork:install now signs with a Developer ID Application identity when one is in the keychain, and only falls back to Apple Development when that's all there is. one line change in
resolveSigningIdentity, plus the docschecked on my machine: installed a Developer ID signed build (no notarization), and 1password's native host went from stopping at "waiting for potential partner browser authorization" every time to "Connected to BrowserHelper", stays running, and the extension shows unlocked after the restart without typing my password. you also need the app added under 1Password Settings → Browser → Add Browser, which the docs now say
tradeoff: changing the signature once means macos may ask to re-grant accessibility / screen recording to T3. no notarization yet since it wasn't needed for this
claude opus 5.5 in claude code did the work