-
Notifications
You must be signed in to change notification settings - Fork 18
feat: add support for ephemeral chat sessions #1086
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🦋 Changeset detectedLatest commit: a9440fd The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
server/design/chatsessions/design.go
Outdated
|
|
||
| Payload(func() { | ||
| Attribute("user_identifier", String, "Optional free-form user identifier") | ||
| Attribute("expires_after", Int, "Token expiration in seconds (max 3600, default 600)", func() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you think it's simpler for max and default to be the same
| } | ||
|
|
||
| // Revoke the token | ||
| err = s.chatSessionsManager.RevokeToken(ctx, claims.ID) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not certain about this but wondering if it's better to revoke by the token as the cache key. That way you don't need to parse to check revocation list
Adds two endpoints:
Create returns a JWT that can then be used to authenticate with certain endpoints, namely chatCompletions and MCP
Next steps: Integrate with Allowed Origins