github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-07-16 23:21:44 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #24597] feat: Scoped MemoryFeed integration collaboration #91092

New Issue
Closed
opened 2026-05-15 16:21:55 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-05-15 16:21:55 -05:00
Owner
Copy Link

Originally created by @hieuchaydi on GitHub (May 12, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24597

Hi maintainers,

I maintain MemoryFeed, a local-first memory system with MCP support.

I want to propose a scoped paid collaboration around integration or hardening in your project:

  • fast first scope (24-72h)
  • clean PR + docs + tests
  • clear acceptance criteria before implementation

If this is useful, I can start with a small paid pilot scope first.

Repository:

Thanks.

Originally created by @hieuchaydi on GitHub (May 12, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/24597 Hi maintainers, I maintain MemoryFeed, a local-first memory system with MCP support. I want to propose a scoped paid collaboration around integration or hardening in your project: - fast first scope (24-72h) - clean PR + docs + tests - clear acceptance criteria before implementation If this is useful, I can start with a small paid pilot scope first. Repository: - https://github.com/hieuchaydi/MemoryFeed Thanks.
GiteaMirror commented 2026-05-15 16:21:56 -05:00
Author
Owner
Copy Link

@owui-terminator[bot] commented on GitHub (May 12, 2026):

⚠️ Missing Issue Title Prefix

@hieuchaydi, your issue title is missing a categorising prefix (e.g. bug:, feat:, docs:).

Please update the title to lead with one of:

  • bug: bug report or error
  • feat: feature request or enhancement
  • docs: documentation issue
  • question: usage question
  • help: support request

Example: bug: Login fails when the password contains special characters

<!-- gh-comment-id:4426454296 --> @owui-terminator[bot] commented on GitHub (May 12, 2026): # ⚠️ Missing Issue Title Prefix @hieuchaydi, your issue title is missing a categorising prefix (e.g. `bug:`, `feat:`, `docs:`). Please update the title to lead with one of: - **bug**: bug report or error - **feat**: feature request or enhancement - **docs**: documentation issue - **question**: usage question - **help**: support request Example: `bug: Login fails when the password contains special characters`
GiteaMirror commented 2026-05-15 16:21:57 -05:00
Author
Owner
Copy Link

@owui-terminator[bot] commented on GitHub (May 12, 2026):

🔍 Related Issues Found

I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:

  1. 🟣 #17034 feat: Current RAG and Memory Behaviour breaks caching of LLM Providers and should be more flexible
    This issue is about changing how memory is handled in prompts, including making memory behavior more flexible. It is the closest match to an integration/hardening effort involving a local-first memory system like MemoryFeed.
    by Podden

  2. 🟣 #23091 feat: User Memory Injection During Function Call Enablement and Disablement
    This request focuses specifically on user memory injection during function calls, which is directly related to memory integration behavior and enabling/disabling memory use in Open WebUI.
    by ffyuhf

  3. 🟢 #19313 feat: User specific MCP headers
    Although centered on MCP headers, it is about improving MCP integration so each user can supply credentials for a globally configured MCP server. That is relevant if the proposed collaboration involves MCP-based integration work.
    by patrykkozuch

  4. 🟢 #16940 feat: Confirming inputs passed to MCP/tools
    This issue is about confirming or modifying data sent to MCP/tools before execution, which is a closely related MCP hardening and safety topic.
    by jayteaftw

💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead.

This comment was generated automatically. React with 👍 if helpful, 👎 if not.

<!-- gh-comment-id:4426455019 --> @owui-terminator[bot] commented on GitHub (May 12, 2026): <!-- terminator-bot:related-issues-reply --> 🔍 **Related Issues Found** I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions: 1. 🟣 [#17034](https://github.com/open-webui/open-webui/issues/17034) **feat: Current RAG and Memory Behaviour breaks caching of LLM Providers and should be more flexible** *This issue is about changing how memory is handled in prompts, including making memory behavior more flexible. It is the closest match to an integration/hardening effort involving a local-first memory system like MemoryFeed.* *by Podden* 2. 🟣 [#23091](https://github.com/open-webui/open-webui/issues/23091) **feat: User Memory Injection During Function Call Enablement and Disablement** *This request focuses specifically on user memory injection during function calls, which is directly related to memory integration behavior and enabling/disabling memory use in Open WebUI.* *by ffyuhf* 3. 🟢 [#19313](https://github.com/open-webui/open-webui/issues/19313) **feat: User specific MCP headers** *Although centered on MCP headers, it is about improving MCP integration so each user can supply credentials for a globally configured MCP server. That is relevant if the proposed collaboration involves MCP-based integration work.* *by patrykkozuch* 4. 🟢 [#16940](https://github.com/open-webui/open-webui/issues/16940) **feat: Confirming inputs passed to MCP/tools** *This issue is about confirming or modifying data sent to MCP/tools before execution, which is a closely related MCP hardening and safety topic.* *by jayteaftw* --- 💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead. *This comment was generated automatically.* React with 👍 if helpful, 👎 if not.
GiteaMirror commented 2026-05-15 16:21:57 -05:00
Author
Owner
Copy Link

@hieuchaydi commented on GitHub (May 12, 2026):

Quick close option so we can move now:

I can start immediately on a fixed $10 mini-scope and deliver first output in under 2 hours:

  • concrete diagnosis + fix path, OR
  • setup/integration mini runbook + patch scope

If this works for your team, reply with the first task and preferred payment method, and I will begin right away.

<!-- gh-comment-id:4428782343 --> @hieuchaydi commented on GitHub (May 12, 2026): Quick close option so we can move now: I can start immediately on a fixed $10 mini-scope and deliver first output in under 2 hours: - concrete diagnosis + fix path, OR - setup/integration mini runbook + patch scope If this works for your team, reply with the first task and preferred payment method, and I will begin right away.
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#91092
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?