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

[GH-ISSUE #4179] [FEAT]: consortium-based units #2658

New Issue
Closed
opened 2026-02-22 18:30:38 -05:00 by yindo · 3 comments
yindo commented 2026-02-22 18:30:38 -05:00
Owner
Copy Link
Copy Source

Originally created by @ghost on GitHub (Jul 20, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4179

What would you like to see?

Could you add consortium-based units to better define the nuances in incoming user queries and capture a smarter approach? These units could be responsible for functions such as extracting emotional nuances from user history, real-time reactions, emotional scoring, personality traits, and enabling image understanding. Simply defining a workflow without the units to perform it is meaningless, and placing too many tasks on a single unit is an overwhelming burden.

Originally created by @ghost on GitHub (Jul 20, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4179 ### What would you like to see? Could you add consortium-based units to better define the nuances in incoming user queries and capture a smarter approach? These units could be responsible for functions such as extracting emotional nuances from user history, real-time reactions, emotional scoring, personality traits, and enabling image understanding. Simply defining a workflow without the units to perform it is meaningless, and placing too many tasks on a single unit is an overwhelming burden.
yindo added the enhancementfeature requestneeds info / can't replicate labels 2026-02-22 18:30:38 -05:00
yindo closed this issue 2026-02-22 18:30:38 -05:00
yindo commented 2026-02-22 18:30:39 -05:00
Author
Owner
Copy Link
Copy Source

@ghost commented on GitHub (Jul 20, 2025):

For example, I could turn this application into an assistant that controls my desktop through a workflow. But which unit will talk to me and track history? Which one will grab an instant screenshot or execute an action? To break out of this dead end, I believe a consortium is essential. Looking at other tasks under development—say, delegating PowerShell control to a unit via an MCP—it becomes clear that on its own it would be insufficient

@ghost commented on GitHub (Jul 20, 2025): For example, I could turn this application into an assistant that controls my desktop through a workflow. But which unit will talk to me and track history? Which one will grab an instant screenshot or execute an action? To break out of this dead end, I believe a consortium is essential. Looking at other tasks under development—say, delegating PowerShell control to a unit via an MCP—it becomes clear that on its own it would be insufficient
yindo commented 2026-02-22 18:30:39 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jul 20, 2025):

I am guessing you are referring to what people call "multi-agent" workflows? Using a bunch of smaller models together vs one larger model to accomplish some end goal? I am currently unclear on what the actual request is since this just sounds like multi-agent execution to me at this time

@timothycarambat commented on GitHub (Jul 20, 2025): I am guessing you are referring to what people call "multi-agent" workflows? Using a bunch of smaller models together vs one larger model to accomplish some end goal? I am currently unclear on what the actual request is since this just sounds like multi-agent execution to me at this time
yindo commented 2026-02-22 18:30:39 -05:00
Author
Owner
Copy Link
Copy Source

@ghost commented on GitHub (Jul 29, 2025):

Could you take a look at the example in my profile? Please run it and see.

@ghost commented on GitHub (Jul 29, 2025): Could you take a look at the example in my profile? Please run it and see.
yindo changed title from [FEAT]: consortium-based units to [GH-ISSUE #4179] [FEAT]: consortium-based units 2026-06-05 14:47:48 -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 needs info / can't replicate
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#2658
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?