Simplify Smithery auth flow and fix connection runtime errors#55
Open
Simplify Smithery auth flow and fix connection runtime errors#55
Conversation
|
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.
This PR removes the token creation/sandbox fallback flow and makes Smithery auth use a server-provided API key passed into client state via SmitheryProvider/useSmithery. It deletes the server token action, updates app/docs entry points to pass process.env.SMITHERY_API_KEY, and simplifies the Tokens UI to namespace management plus masked API key display. It also migrates Smithery connection usage from experimental.connect.connections to the current client.connections API (including updated type imports) to fix runtime connect failures. Finally, it clamps connection ID masking to prevent negative String.repeat counts and resolves the RangeError seen in connections rendering.