Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 22:23:50 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #5773] [FEAT]: Domain Memories (Grouped Workspaces) #5567

New Issue
Open
opened 2026-06-07 16:36:41 -04:00 by yindo · 0 comments
yindo commented 2026-06-07 16:36:41 -04:00
Owner
Copy Link
Copy Source

Originally created by @KinuCyber on GitHub (Jun 7, 2026).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/5773

What would you like to see?

As of now, we have

[workspace system prompt]
- [global memories]    <--    up to 5, cross-workspace
- [workspace memories]    <--    up to 20, scoped to this workspace
--> sent to LLM

However, I often need to handle workspaces that are inter-connected, some related to my FOSS projects while others related to academia.
Global memories don't bridge this gap cleanly: scoping them broadly pollutes unrelated workspaces (academic curriculum bleeding into FOSS project context), while duplicating them per workspace is manual and highly error-prone.

A better way would be to have a dedicated Domain memory, and workspaces grouped under them

[workspace system prompt]
- [global memories]
- [domain memories]    <--    new layer, scoped to workspace's domain
- [workspace memories]
--> sent to LLM

This lets us relevant workspaces (various projects under "FOSS" domain, academic research under "Academia" domain, etc) relevant to related workspaces without polluting unrelated workspaces.

On the frontend note: The UI integration shouldn't be just another nesting of workspaces/threads under domain but rather a separate domain list to select from. This helps in remaining focused on the domain at work yet still be able to switch between domains while retaining focus

Originally created by @KinuCyber on GitHub (Jun 7, 2026). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/5773 ### What would you like to see? As of now, we have ``` [workspace system prompt] - [global memories] <-- up to 5, cross-workspace - [workspace memories] <-- up to 20, scoped to this workspace --> sent to LLM ``` However, I often need to handle workspaces that are inter-connected, some related to my FOSS projects while others related to academia. Global memories don't bridge this gap cleanly: scoping them broadly pollutes unrelated workspaces (academic curriculum bleeding into FOSS project context), while duplicating them per workspace is manual and highly error-prone. A better way would be to have a dedicated Domain memory, and workspaces grouped under them ``` [workspace system prompt] - [global memories] - [domain memories] <-- new layer, scoped to workspace's domain - [workspace memories] --> sent to LLM ``` This lets us relevant workspaces (various projects under "FOSS" domain, academic research under "Academia" domain, etc) relevant to related workspaces without polluting unrelated workspaces. On the frontend note: The UI integration shouldn't be just another nesting of workspaces/threads under domain but rather a separate domain list to select from. This helps in remaining focused on the domain at work yet still be able to switch between domains while retaining focus
yindo added the enhancementfeature request labels 2026-06-07 16:36:41 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label enhancement feature request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#5567
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?