-
Notifications
You must be signed in to change notification settings - Fork 6.3k
feat: add Atomic Chat as declarative OpenAI-compatible provider #9210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
alexhancock
merged 6 commits into
aaif-goose:main
from
yanalialiuk:feat/atomic-agent-declarative-provider
May 14, 2026
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
bab92ec
feat: add Atomic Chat as declarative OpenAI-compatible provider
ef89648
fmt
1e62df2
docs: align Atomic Chat with LM Studio table and Local LLMs tab
yanalialiuk c7e275c
feat(catalog): add Atomic Chat to provider setup metadata
yanalialiuk 5a83d33
chore: shorten atomic_chat declarative description
yanalialiuk 68db8ee
chore: align Atomic Chat declarative copy with LM Studio
yanalialiuk File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,23 @@ | ||
| { | ||
| "name": "atomic_chat", | ||
| "engine": "openai", | ||
| "display_name": "Atomic Chat", | ||
| "description": "Local models through Atomic Chat\u2019s OpenAI-compatible server", | ||
| "api_key_env": "", | ||
| "base_url": "${ATOMIC_CHAT_HOST}/v1/chat/completions", | ||
| "env_vars": [ | ||
| { | ||
| "name": "ATOMIC_CHAT_HOST", | ||
| "required": false, | ||
| "secret": false, | ||
| "primary": true, | ||
| "default": "http://localhost:1337", | ||
| "description": "Base URL of the Atomic Chat server (default: http://localhost:1337)" | ||
| } | ||
| ], | ||
| "dynamic_models": true, | ||
| "models": [], | ||
| "supports_streaming": true, | ||
| "requires_auth": false, | ||
| "skip_canonical_filtering": true | ||
| } | ||
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding the declarative JSON registers
atomic_chatfor the backend/CLI, but the desktop provider picker is populated fromSETUP_METADATAincrates/goose/src/providers/catalog.rs, and there is noprovider_id: "atomic_chat"entry there. After the catalog loads,ui/goose2/src/features/providers/hooks/useProviderInventory.tsfilters model providers to catalog IDs, so this new provider will not appear in the desktop Configure Providers flow that the docs advertise and its inventory entry can be filtered out; add aCuratedSetupMetadataentry foratomic_chatwith theATOMIC_CHAT_HOSTfield.Useful? React with 👍 / 👎.