github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-06 19:08:59 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #23091] feat: User Memory Injection During Function Call Enablement and Disablement #19883

New Issue
Closed
opened 2026-04-20 02:24:54 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-20 02:24:54 -05:00
Owner
Copy Link

Originally created by @ffyuhf on GitHub (Mar 26, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/23091

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

AI only invokes ordinary tools but does not actively invoke memory functions. In most cases, they do not actively view memories. Therefore, can the memory injection behavior under native function calls be consistent with the default mode, i.e., enabled by default?

Desired Solution you'd like

AI only invokes ordinary tools but does not actively invoke memory functions. In most cases, they do not actively view memories. Therefore, can the memory injection behavior under native function calls be consistent with the default mode, i.e., enabled by default?

Alternatives Considered

No response

Additional Context

No response

Originally created by @ffyuhf on GitHub (Mar 26, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/23091 ### 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 AI only invokes ordinary tools but does not actively invoke memory functions. In most cases, they do not actively view memories. Therefore, can the memory injection behavior under native function calls be consistent with the default mode, i.e., enabled by default? ### Desired Solution you'd like AI only invokes ordinary tools but does not actively invoke memory functions. In most cases, they do not actively view memories. Therefore, can the memory injection behavior under native function calls be consistent with the default mode, i.e., enabled by default? ### Alternatives Considered _No response_ ### Additional Context _No response_
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
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/open-webui#19883
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?