[GH-ISSUE #27] Define temperature as environment variable #17

Closed
opened 2026-02-22 18:17:28 -05:00 by yindo · 2 comments
Owner

Originally created by @jwaltz on GitHub (Jun 11, 2023).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/27

Would it be a reasonable feature to allow temperature to be a user-defined environment variable instead of hardcoded as 0.7? I ask because when using the app as an internal knowledgebase I think a lower value or even a temperature of 0 would be beneficial.

I'd be happy to create a PR for this.

Originally created by @jwaltz on GitHub (Jun 11, 2023). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/27 Would it be a reasonable feature to allow temperature to be a user-defined environment variable instead of hardcoded as 0.7? I ask because when using the app as an internal knowledgebase I think a lower value or even a temperature of 0 would be beneficial. I'd be happy to create a PR for this.
yindo added the enhancementstage: specifications labels 2026-02-22 18:17:28 -05:00
yindo closed this issue 2026-02-22 18:17:28 -05:00
Author
Owner

@timothycarambat commented on GitHub (Jun 11, 2023):

I like this a lot, maybe as a workspace setting so its defined per workspace

  • Click on the settings icon, tab for workspace config
  • Temperature as setting
  • Push all settings into a column on the workspaces table as stringified JSON. This is tricky because if someone pulls in changes and has a table we need a way to do a migration for the new column if not found. Even if its a special API endpoint the user can invoke to migrate all tables to the expected table format.
  • The just read that in when calling query. Would be a huge QOL update.

or
We make ENV variable and if not set just falls back to 0.7 🤷

Thoughts?

@timothycarambat commented on GitHub (Jun 11, 2023): I like this a lot, maybe as a workspace setting so its defined per workspace - Click on the settings icon, tab for workspace config - Temperature as setting - Push all settings into a column on the workspaces table as stringified JSON. This is tricky because if someone pulls in changes and has a table we need a way to do a migration for the new column if not found. Even if its a special API endpoint the user can invoke to migrate all tables to the expected table format. - The just read that in when calling `query`. Would be a huge QOL update. **or** We make ENV variable and if not set just falls back to 0.7 🤷 Thoughts?
Author
Owner

@jwaltz commented on GitHub (Jun 11, 2023):

That is an excellent idea. I can see the value in configuring temperature on a per-workspace basis. Maybe a combination of both, so that a user can define a default temperature as a fallback?

@jwaltz commented on GitHub (Jun 11, 2023): That is an excellent idea. I can see the value in configuring temperature on a per-workspace basis. Maybe a combination of both, so that a user can define a default temperature as a fallback?
yindo changed title from Define temperature as environment variable to [GH-ISSUE #27] Define temperature as environment variable 2026-06-05 14:33:01 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#17