fix: resolve user ID mismatch in agent routes for device auth flow #12
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.
Problem
When publishing agents via CLI using device code authentication, users receive a
User not founderror (500 Internal Server Error).Root Cause
The JWT auth middleware sets
req.user.userId, but all agent routes were accessingreq.user.id(which is only set during OAuth callback flows).Solution
Updated all 9 agent route files to correctly access the user ID from both authentication methods:
Files Changed
Required auth routes (with proper validation):
publish.tsdelete.tsupdate-metadata.tsOptional auth routes:
get-agent.tssearch.tslist.tsversions.tsget-version.tsmcp-servers.tsTesting