Skip to content

feat(providers): add Atomic Chat local OpenAI-compatible provider - #90

Open
yanalialiuk wants to merge 1 commit into
cosmicstack-labs:mainfrom
yanalialiuk:feat/atomic-chat-provider
Open

feat(providers): add Atomic Chat local OpenAI-compatible provider#90
yanalialiuk wants to merge 1 commit into
cosmicstack-labs:mainfrom
yanalialiuk:feat/atomic-chat-provider

Conversation

@yanalialiuk

Copy link
Copy Markdown

Summary

  • Add Atomic Chat as a first-class local provider (atomicChat) with default http://127.0.0.1:1337/v1.
  • Discover models via GET /v1/models (OpenAI-compatible path, same as LM Studio/Ollama Local routing).
  • Wire setup into mercury doctor / first-run wizard — no API key required.
  • Document env vars: ATOMIC_CHAT_ENABLED, ATOMIC_CHAT_BASE_URL, ATOMIC_CHAT_MODEL.

Why

Atomic Chat runs local models behind a standard OpenAI-compatible API. Mercury users should be able to select it like Ollama Local without manually configuring the generic OpenAI Compatible provider.

Test plan

  • npm test -- src/utils/provider-models.test.ts
  • Start Atomic Chat with a loaded model
  • Run mercury doctor, choose Atomic Chat, confirm model list populates
  • Send a prompt via CLI/Telegram and verify responses

Made with Cursor

Add first-class Atomic Chat support with default http://127.0.0.1:1337/v1, /v1/models discovery, doctor setup flow, and docs alongside Ollama Local.

Co-authored-by: Cursor <cursoragent@cursor.com>
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.

1 participant