add custom AI providers in config #7771
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
bot
added
documentation
Light2Dark
force-pushed
the
sham/add-custom-providers
branch
from
c5b975d to
4784f31
Compare
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds support for configuring multiple custom OpenAI-compatible AI providers through the settings UI and configuration files. Users can now define custom providers (like Groq, Together AI, DeepSeek, etc.) with distinct names instead of being limited to a single open_ai_compatible provider.
Changes:
- Added
custom_providersfield to AI configuration as a dictionary mapping provider names to OpenAI-compatible configs - Implemented deep merge utility with selective replacement for managing provider configurations
- Extended frontend UI to allow adding, editing, and removing custom providers
- Updated documentation with examples for popular OpenAI-compatible providers
Reviewed changes
Copilot reviewed 21 out of 23 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
marimo/_utils/deep_merge.py |
New deep merge utility with replace_paths feature for selective replacement during config merging |
marimo/_config/config.py |
Added custom_providers field to AiConfig and configured it as a replace path in merge_config |
marimo/_config/secrets.py |
Extended secrets masking to handle api_keys in custom_providers |
marimo/_server/ai/config.py |
Added for_custom_provider method to handle provider configs by name and updated for_model to check custom providers |
frontend/src/core/ai/ids/ids.ts |
Extended ProviderId type to accept both known providers and custom strings while maintaining autocomplete |
frontend/src/core/config/config-schema.ts |
Added custom_providers schema field with default empty object |
frontend/src/components/app-config/ai-config.tsx |
Added CustomProvidersConfig component with UI for adding, editing, and removing custom providers |
frontend/src/components/app-config/user-config-form.tsx |
Updated getDirtyValues to handle undefined values when providers are deleted |
tests/_utils/test_deep_merge.py |
Comprehensive tests for deep merge functionality including replace_paths behavior |
tests/_config/test_config.py |
Tests for custom_providers replacement behavior in config merging |
tests/_config/test_secrets_config.py |
Tests for masking and removing secrets in custom_providers |
tests/_server/templates/snapshots/*.txt |
Updated snapshots to include custom_providers in config |
docs/guides/configuration/llm_providers.md |
Updated documentation with custom providers section and provider-specific examples |
packages/openapi/api.yaml |
Added custom_providers to AiConfig schema |
packages/openapi/src/api.ts |
TypeScript types updated for custom_providers |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
akshayka
reviewed
Jan 14, 2026
Contributor
akshayka
left a comment
akshayka
left a comment
There was a problem hiding this comment.
This is really nice! One clarification may be needed in the docs (see my comment), otherwise looks good to me
| </video> | ||
| </div> | ||
|
|
||
| Once added, use your custom provider with the prefix you chose: |
Contributor
There was a problem hiding this comment.
Should users specify their models directly in the marimo.toml file, or in the settings UI? As written it seems like the recommendation is the marimo.toml since that is what follows this sentence
mscolnick
previously approved these changes
Jan 15, 2026
Light2Dark
force-pushed
the
sham/add-custom-providers
branch
from
8be0a49 to
e18290c
Compare
mscolnick
approved these changes
Jan 15, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📝 Summary
Fixes #7243.
🔍 Description of Changes
📋 Checklist