I have searched the existing issues and discussions.
Problem Description
It would be highly benefitial to provide current user context to Tools call - for example, as a JWT token (with configurable server key). This way the response could be tailored to, for example, user permissions, user role or similar.
Desired Solution you'd like
A standardized way for Tools code to access user context - like email - in a trusted way.
Originally created by @brainboutique on GitHub (May 20, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/14097
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
### Problem Description
It would be highly benefitial to provide current user context to Tools call - for example, as a JWT token (with configurable server key). This way the response could be tailored to, for example, user permissions, user role or similar.
### Desired Solution you'd like
A standardized way for Tools code to access user context - like email - in a trusted way.
### Alternatives Considered
See #13457 or #13608
### Additional Context
_No response_
@brainboutique commented on GitHub (May 20, 2025):
Missed the existing support for this param: __user__.get("email")
<!-- gh-comment-id:2895152614 -->
@brainboutique commented on GitHub (May 20, 2025):
Missed the existing support for this param:
`__user__.get("email")`
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @brainboutique on GitHub (May 20, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/14097
Check Existing Issues
Problem Description
It would be highly benefitial to provide current user context to Tools call - for example, as a JWT token (with configurable server key). This way the response could be tailored to, for example, user permissions, user role or similar.
Desired Solution you'd like
A standardized way for Tools code to access user context - like email - in a trusted way.
Alternatives Considered
See #13457 or #13608
Additional Context
No response
@brainboutique commented on GitHub (May 20, 2025):
Missed the existing support for this param:
__user__.get("email")