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 #796] [FEAT]: API Key foreach workspace instead unique for platform #464

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

Originally created by @Mirgiacomo on GitHub (Feb 26, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/796

What would you like to see?

Hello,
might it make sense to have the ability to set an API_KEY (of OpenAI but also mistral etc in case) at the workspace level instead of the whole platform?

So for example you can better differentiate what costs one workspace had over another.

Currently instead you can set a unique api key in LLM Preference that all workspaces will use.

What do you think is the time frame for implementing this small change?

Originally created by @Mirgiacomo on GitHub (Feb 26, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/796 ### What would you like to see? Hello, might it make sense to have the ability to set an API_KEY (of OpenAI but also mistral etc in case) at the workspace level instead of the whole platform? So for example you can better differentiate what costs one workspace had over another. Currently instead you can set a unique api key in LLM Preference that all workspaces will use. What do you think is the time frame for implementing this small change?
yindo added the enhancementfeature request labels 2026-02-22 18:19:37 -05:00
yindo closed this issue 2026-02-22 18:19:37 -05:00
yindo commented 2026-02-22 18:19:38 -05:00
Author
Owner
Copy Link
Copy Source

@Mirgiacomo commented on GitHub (Feb 26, 2024):

Or it would be very convenient to be able to set variables at the workspace level to be able to integrate with LangSmith and keep track of processed tokens, timing, cost, etc.

I did a quick test on another project and all I had to do was put these three variables in the .env file:
LANGCHAIN_TRACING_V2=true
LANGCHAIN_API_KEY="ls__xxx"
LANGCHAIN_PROJECT="xxx"

Here is the docs:
https://docs.smith.langchain.com/tracing

@Mirgiacomo commented on GitHub (Feb 26, 2024): Or it would be very convenient to be able to set variables at the workspace level to be able to integrate with LangSmith and keep track of processed tokens, timing, cost, etc. I did a quick test on another project and all I had to do was put these three variables in the .env file: LANGCHAIN_TRACING_V2=true LANGCHAIN_API_KEY="ls__xxx" LANGCHAIN_PROJECT="xxx" Here is the docs: https://docs.smith.langchain.com/tracing
yindo commented 2026-02-22 18:19:38 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Feb 26, 2024):

https://github.com/Mintplex-Labs/anything-llm/issues/698

We don't use Langchain objects in every provider because it's easier to manage our own context and do calls than rely on a third-party wrapper. What provider are you using though? We use it for some providers just for ease of use.

@timothycarambat commented on GitHub (Feb 26, 2024): https://github.com/Mintplex-Labs/anything-llm/issues/698 We don't use Langchain objects in every provider because it's easier to manage our own context and do calls than rely on a third-party wrapper. What provider are you using though? We use it for some providers just for ease of use.
yindo commented 2026-02-22 18:19:38 -05:00
Author
Owner
Copy Link
Copy Source

@Mirgiacomo commented on GitHub (Feb 26, 2024):

@timothycarambat But the functionality of being able to enter a different api key (openai in this case) for each workspace is not feasible?
From the way the code is structured, this should not be a big problem.
Then maybe I am wrong...
But in my opinion it could also be useful to do usage statistics broken down by api key

@Mirgiacomo commented on GitHub (Feb 26, 2024): @timothycarambat But the functionality of being able to enter a different api key (openai in this case) for each workspace is not feasible? From the way the code is structured, this should not be a big problem. Then maybe I am wrong... But in my opinion it could also be useful to do usage statistics broken down by api key
yindo changed title from [FEAT]: API Key foreach workspace instead unique for platform to [GH-ISSUE #796] [FEAT]: API Key foreach workspace instead unique for platform 2026-06-05 14:35:27 -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#464
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?