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 #5313] [FEAT]: Model router #5015

New Issue
Closed
opened 2026-06-05 14:51:31 -04:00 by yindo · 1 comment
yindo commented 2026-06-05 14:51:31 -04:00
Owner
Copy Link
Copy Source

Originally created by @shatfield4 on GitHub (Mar 31, 2026).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/5313

Originally assigned to: @shatfield4 on GitHub.

What would you like to see?

  • Build an intelligent prompt routing layer that intercepts user prompts before they reach LLM to dynamically select the model that would provide the best result for the costs
  • Main idea is to use calculated (deterministic) rules such as: keyword triggers, token count, message counts, date/time periods (some models have peak pricing times) etc
  • See if we can get semantic routing working by allowing users to configure a specific model used for routing chats inside admin settings for model router and using that model to do a tool call to route to the correct model each time
  • Follow backend design per internal spec on Notion
Originally created by @shatfield4 on GitHub (Mar 31, 2026). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/5313 Originally assigned to: @shatfield4 on GitHub. ### What would you like to see? - Build an intelligent prompt routing layer that intercepts user prompts before they reach LLM to dynamically select the model that would provide the best result for the costs - Main idea is to use calculated (deterministic) rules such as: keyword triggers, token count, message counts, date/time periods (some models have peak pricing times) etc - See if we can get semantic routing working by allowing users to configure a specific model used for routing chats inside admin settings for model router and using that model to do a tool call to route to the correct model each time - Follow backend design per internal spec on Notion
yindo added the enhancementfeature request labels 2026-06-05 14:51:31 -04:00
yindo closed this issue 2026-06-05 14:51:31 -04:00
yindo commented 2026-06-05 14:51:32 -04:00
Author
Owner
Copy Link
Copy Source

@PikkonMG commented on GitHub (Apr 2, 2026):

In the works I asked a few weeks ago #5209

<!-- gh-comment-id:4178196655 --> @PikkonMG commented on GitHub (Apr 2, 2026): In the works I asked a few weeks ago [#5209](https://github.com/Mintplex-Labs/anything-llm/issues/5209#issuecomment-4068839506)
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#5015
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?