[GH-ISSUE #21540] feat: Allow Masking input on __event_call__ for openwebui functions #58177

Closed
opened 2026-05-05 22:28:39 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @ctolon on GitHub (Feb 17, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/21540

Check Existing Issues

  • I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.

Verify Feature Scope

  • I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.

Problem Description

https://github.com/open-webui/open-webui/issues/20852
This PR has integrated a feature for masking sensitive fields for user valves. It would be great if the same feature were also available for event_call for openwebui functions.

Desired Solution you'd like

I haven't prepared a direct solution, but I think it would be easy to integrate into the current architecture.

Alternatives Considered

No response

Additional Context

No response

Originally created by @ctolon on GitHub (Feb 17, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/21540 ### Check Existing Issues - [x] I have searched for all existing **open AND closed** issues and discussions for similar requests. I have found none that is comparable to my request. ### Verify Feature Scope - [x] I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions. ### Problem Description https://github.com/open-webui/open-webui/issues/20852 This PR has integrated a feature for masking sensitive fields for user valves. It would be great if the same feature were also available for __event_call__ for openwebui functions. ### Desired Solution you'd like I haven't prepared a direct solution, but I think it would be easy to integrate into the current architecture. ### Alternatives Considered _No response_ ### Additional Context _No response_
Author
Owner

@tjbck commented on GitHub (Feb 23, 2026):

4853ededca

<!-- gh-comment-id:3941959710 --> @tjbck commented on GitHub (Feb 23, 2026): 4853ededcabcd76d9bd2036181486cd3a41458a1
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#58177