Skip to content

Conversation

ArmDaniel
Copy link

  • Adds OpenRouter as a selectable LLM provider alongside OpenAI.
  • Users can choose the provider and select specific models from OpenRouter.
  • Includes UI for managing OpenRouter API keys, similar to Firecrawl keys.
  • Updates backend API to handle requests to OpenRouter.
  • Modifies API key checking to include OpenRouter keys.
  • Updates README with new features and environment variables.

- Adds OpenRouter as a selectable LLM provider alongside OpenAI.
- Users can choose the provider and select specific models from OpenRouter.
- Includes UI for managing OpenRouter API keys, similar to Firecrawl keys.
- Updates backend API to handle requests to OpenRouter.
- Modifies API key checking to include OpenRouter keys.
- Updates README with new features and environment variables.
- Adds `components/ui/select.tsx` and `components/ui/label.tsx` to resolve compilation errors.
- These components were used by the new OpenRouter configuration UI but were not explicitly added to the project.
- Replaces OpenRouter model selection dropdown with a searchable Combobox.
- Removes client-side 'chat' model filtering, displaying all models from OpenRouter.
- Adds `cmdk` and necessary Shadcn UI components (Combobox, Command, Popover) for the new model selector.
- Updates UI for theme consistency: configuration section and search input now use light backgrounds (bg-gray-50 and bg-white respectively) with dark text, removing specific dark-mode styling for these elements to align with the overall light theme.
Copy link

@anthonywu anthonywu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the v2 Fireplexity refactoring is gonna require a re-write of this PR. However I'm here to +1 OpenRouter as a model provider.

IMO the maintainers probably don't want to add every provider, but OpenRouter and Ollama in my #10 are good placeholders for most use cases without too much scope creep.

I think for most prod use cases that want to use this framework, they would just fork the repo and implement their specific providers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants