feat(mcp): supply a rotating signer credential to the gateway - #40
Open
eliteprox wants to merge 1 commit into
Open
feat(mcp): supply a rotating signer credential to the gateway#40eliteprox wants to merge 1 commit into
eliteprox wants to merge 1 commit into
Conversation
Build one gateway per inference call with a signerHeaders provider backed by resolveSignerSession, seeding the first exchange so we do not mint twice. Drop the outer SignerRefreshRequired rebuild — the library now refreshes the bearer itself.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
runInferencebuilds one gateway per call with asignerHeadersprovider backed byresolveSignerSession.SignerRefreshRequiredcatch-and-rebuild. The library now rotates the bearer itself (expiry skew + HTTP 480).Depends on
@pymthouse/gateway-web@^0.4.0(pymthouse/gateway-web#23 — number may differ). Merge after that package is published;pnpm-lock.yamlis left on the currently resolved version so CI does not pick up afile:path. After 0.4.0 is on npm, runpnpm update @pymthouse/gateway-weband land the lockfile.Test plan
pnpm typecheckandpnpm lintagainst local gateway-web 0.4.0lib/mcp/gateway.ts