Skip to content

Model configuration (env variables) #408

Closed

Description

@anafucs

Background

Today we only allow a user-friendly experience to configure model provider and model through the CLI (#352). However there are several gaps

  • we don't have a similar experience in the Web UI, so users must pass through the CLI or use the settings tab
  • we only enable a single configuration globally at a time (1 LLM provider + 1 api key + 1 model)
  • if a users changes the model configuration, it overrides the previous one, so there is no toggling.

Discussion points

  • Can we enable users to have a similarly friendly first-time experience of setting up an LLM provider and selecting a model in the GUI that we have in the CLI?
  • The CLI currently is a "wizard" type experience. What if a user just wants to enter the three values?
  • Can we store multiple API keys so they can switch providers and models more easily?
  • Where does a user inspect their stored variables/configs? (CLI and GUI)
  • If we had multiple configurations stored, where would a user set default?
  • Can we store multiple API keys so they can switch models across providers?
  • Do we include a required (or optional) definition of recommended model for agents and reflect that in the UI (recommended tag or similar)
  • Can a user test different models (i.e. swap among saved configurations) at model runtime?
  • Do we allow manually changing the 3 environment variables related to the provider and model setup (as we currently have in the settings GUI)?
  • How do we create the equivalent experience CLI / GUI with transparency, simplifying the setup for single or multiple LLM providers (if possible)

Figma WIP exploring these concepts: https://www.figma.com/design/L4r1yLEAL2PsAqSn6XWj0s/Bee-JAM-4.0?node-id=2090-2

Activity

  1. self-assigned this
    on Mar 17, 2025
  2. added theissue type on Mar 17, 2025
  3. self-assigned this
    on Mar 18, 2025
  4. changed the title [-]UI – Provider and model configuration[/-] [+]UI – model configuration (env variables)[/+] on Mar 18, 2025
  5. geneknit commented on Mar 20, 2025

    @geneknit
    Member

    I think we need to blow this one out and turn it into a discussion vs. a feature. Lots to unpack here.

  6. changed the title [-]UI – model configuration (env variables)[/-] [+]Model configuration (env variables)[/+] on Mar 21, 2025
  7. removed theissue type on Mar 21, 2025
  8. locked and limited conversation to collaborators on Mar 21, 2025
  9. converted this issue into a discussion #444 on Mar 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions