[FEAT]: Per-Thread Settings

Mintplex-Labs / anything-llm

The all-in-one Desktop & Docker AI application with built-in RAG, AI agents, and more.

https://anythingllm.com

MIT License

22.4k stars 2.26k forks source link

[FEAT]: Per-Thread Settings #2181

Open ericthomas1 opened 2 weeks ago

ericthomas1 commented 2 weeks ago

What would you like to see?

It would be quite powerful to set temperature, prompt, chat history to include, etc. per-thread rather than per-Workspace.

Use-case:

Using the same Workspace and document set
- Request "Creative" tasks of the LLM (aka: temp closer to 1, more creative system prompt) in one thread
- Request "More Probable" tasks of the LLM (aka: temp closer to 0, more deterministic system prompt) in another thread

As of now, one has to create separate Workspaces to change temperature and system_prompt.

timothycarambat commented 2 weeks ago

Would being able to easily duplicate a workspace benefit you? This would be pretty complex to add just for threads, believe it or not, and it kind of breaks our mental model for workspaces.

Its not impossible by any means, but I dont want to overload people with too much possible config!

ericthomas1 commented 2 weeks ago

Hm...we've been framing Workspaces as a flexible way to segment a Team's instance by doc type / role / position / tenure / individual, etc.

If a team has 10 people and each teammate has their own individual Workspace + their collective workspaces, I could see the leftnav getting busy.

Whereas the way threads collapse when not used keeps the leftnav clean.

So making more Workspaces (easily duplicating) may make things busy...hm...have to think about it some more / test out with more teams.

ericthomas1 commented 2 weeks ago

I know its possible to control Workspace visibility using AnythingLLM's built in auth, but this isn't something thats allowed in our org (non-centralized UAC/mgmt.). We're waiting for AAD/EntraID implementation. Maybe at that point authorization could control visibility in a clean way.