Skip to content

feat: linked-account Redis cache, user JWT, /link UX - #5

Draft
owens1127 wants to merge 2 commits into
mainfrom
feat/linked-account-cache-and-user-jwt
Draft

feat: linked-account Redis cache, user JWT, /link UX#5
owens1127 wants to merge 2 commits into
mainfrom
feat/linked-account-cache-and-user-jwt

Conversation

@owens1127

Copy link
Copy Markdown
Contributor

Summary

raidhub-discord support for linked RaidHub identity: Redis-backed Turso snapshot cache, user JWT minting via API, and slash /link guidance.

Key changes

  • linked_account_context + Redis; Turso URL from env.
  • raidhub_user_jwt (POST /authorize/user with RAIDHUB_CLIENT_SECRET).
  • /link command + manifest strings; RaidHubClient passes user JWT on eligible commands.

Related PRs (linked roles stack)

  • API: feat/discord-linked-roles-api
  • Web-App: feat/discord-linked-roles
  • Services: feat/discord-linked-roles (Raid-Hub/Services)

Note

Can merge independently for bot UX; full linked-role metadata still flows Website → API → Rabbit → Hermes.

Made with Cursor

owens1127 and others added 2 commits May 3, 2026 23:02
- linked_account_context: Turso lookup + Redis cache; attach on interactions.
- raidhub_user_jwt: POST /authorize/user with RAIDHUB_CLIENT_SECRET for scoped API.
- link command + manifest copy for Account linking; config/env/README updates.
- Slash commands pass RaidHubClient with user JWT where applicable.

Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant