github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-22 06:16:18 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[GH-ISSUE #3117] Support caching of modified session data with customSession plugin #9478

New Issue
Closed
opened 2026-04-13 04:57:30 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-13 04:57:30 -05:00
Owner
Copy Link

Originally created by @arthberman on GitHub (Jun 21, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/3117

Is this suited for github?

  • Yes, this is suited for github

Is your feature request related to a problem? Please describe.

I'm frustrated that when using the customSession plugin to add custom fields to the session data, the session caching mechanism in Better Auth no longer works. This means that any custom data added to the session cannot be accessed through getSessionCookie or auth.api.getSession, which limits the flexibility and performance benefits of session caching.

Describe the solution you'd like

I would like Better Auth to support session caching even when the customSession plugin is used to modify or extend the session data. Ideally, it should be possible to add custom fields to the session, have them cached, and access them through the standard session retrieval methods.

Describe alternatives you've considered

I've considered not using the customSession plugin and only relying on the default session fields, but this does not meet my application's requirements for storing additional user-specific or context-specific data. Another alternative is to manage custom data outside of the session, but this adds unnecessary complexity and overhead.

Additional context

This limitation was discussed in the Better Auth Discord, where it was confirmed that session caching does not currently work with custom session data. Having this feature would greatly improve developer experience and enable more advanced use cases.

Originally created by @arthberman on GitHub (Jun 21, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/3117 ### Is this suited for github? - [x] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. I'm frustrated that when using the customSession plugin to add custom fields to the session data, the session caching mechanism in Better Auth no longer works. This means that any custom data added to the session cannot be accessed through getSessionCookie or auth.api.getSession, which limits the flexibility and performance benefits of session caching. ### Describe the solution you'd like I would like Better Auth to support session caching even when the customSession plugin is used to modify or extend the session data. Ideally, it should be possible to add custom fields to the session, have them cached, and access them through the standard session retrieval methods. ### Describe alternatives you've considered I've considered not using the customSession plugin and only relying on the default session fields, but this does not meet my application's requirements for storing additional user-specific or context-specific data. Another alternative is to manage custom data outside of the session, but this adds unnecessary complexity and overhead. ### Additional context This limitation was discussed in the Better Auth [Discord](https://discord.com/channels/1288403910284935179/1385189982813159507), where it was confirmed that session caching does not currently work with custom session data. Having this feature would greatly improve developer experience and enable more advanced use cases.
GiteaMirror added the enhancementlocked labels 2026-04-13 04:57:30 -05:00
GiteaMirror commented 2026-04-13 04:57:32 -05:00
Author
Owner
Copy Link

@dosubot[bot] commented on GitHub (Sep 20, 2025):

Hi, @arthberman. I'm Dosu, and I'm helping the better-auth team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You requested support for caching modified session data when using the customSession plugin.
  • Currently, custom session fields are not cached or accessible via standard methods.
  • This limitation affects flexibility and performance, requiring developers to manage custom data outside sessions.
  • Enabling caching for custom session data would improve developer experience and enable advanced use cases.
  • There has been no activity or comments on this issue so far.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of better-auth by commenting below.
  • If I do not hear back within 7 days, I will automatically close this issue.

Thank you for your understanding and contribution!

<!-- gh-comment-id:3315072698 --> @dosubot[bot] commented on GitHub (Sep 20, 2025): Hi, @arthberman. I'm [Dosu](https://dosu.dev), and I'm helping the better-auth team manage their backlog and am marking this issue as stale. **Issue Summary:** - You requested support for caching modified session data when using the customSession plugin. - Currently, custom session fields are not cached or accessible via standard methods. - This limitation affects flexibility and performance, requiring developers to manage custom data outside sessions. - Enabling caching for custom session data would improve developer experience and enable advanced use cases. - There has been no activity or comments on this issue so far. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of better-auth by commenting below. - If I do not hear back within 7 days, I will automatically close this issue. Thank you for your understanding and contribution!
GiteaMirror commented 2026-04-13 04:57:32 -05:00
Author
Owner
Copy Link

@kevinehosford commented on GitHub (Sep 30, 2025):

I still see this issue and it is kind of frustrating behavior.

<!-- gh-comment-id:3353869393 --> @kevinehosford commented on GitHub (Sep 30, 2025): I still see this issue and it is kind of frustrating behavior.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label enhancement locked
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#9478
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?