Repository navigation
Conversation
A managed profile can name a Claude Code plugin marketplace that its gateway serves behind the same credential (Marketplace: Name, URL). KeyZapper writes it as an extraKnownMarketplaces entry next to the profile and removes it with the assignment. The new helper command headers prints the profile's credential as an Authorization header, which is what Claude Code expects from a headersHelper. A marketplace on another host than the profile's endpoint is not written, so the credential never leaves the gateway. Co-Authored-By: Claude Fable 5.2 <[email protected]>
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.
What
A gateway can serve a Claude Code plugin marketplace behind the same credential as the model calls. Claude Code fetches such a marketplace with a
headersHelper, which has to print a JSON object of HTTP headers. KeyZapper already owns the credential, so it can provide both pieces:keyzapper-helper headers --profile <UUID>prints the profile's credential as{"Authorization":"Bearer …"}. It goes through the same path ascredential(https check,AllowedGatewayHosts, SSO refresh), so nothing new decides who gets a key.Marketplacedict (Name,URL) inside aManagedProfilesentry.extraKnownMarketplacesentry (sourceurl, theheadersHelperabove,autoUpdate: true) into the project'ssettings.local.jsonand into the user settings for the default profile. It removes the entry again with the assignment, unless someone changed it since. Entries of other marketplaces are left alone.Safety
headersHelper(500 printable ASCII characters, no four spaces in a row), or for a name with characters outside[A-Za-z0-9._-].Not in this PR
ManagedProfiles.allowedPluginMarketplacesalready fits intoClaudeDesktop›Config. The README rows say so.Checked
cargo test -p keyzapper-core: 48 unit and 94 integration tests pass, three of them new (helper output, write/drop/revert of the entry next to a foreign marketplace, the managed dict).desktop/scripts/l10n_check.pypasses (the usage string changed).model.rs, which copies the block from the managed profile). Not tried against a real Claude Code client.🤖 Generated with Claude Code