AI Providers

MeghaOS works with 25+ built-in providers, any OpenAI-compatible API, and local models.

The MeghaOS assistant is provider-agnostic. You pick the AI that powers it in Settings β†’ AI, and every request routes to your chosen provider. Switching is live β€” the next request uses the new provider/model with no restart.

Any OpenAI-compatible API

The important part: most providers speak the OpenAI-compatible chat-completions format, so MeghaOS works with almost any model service β€” including ones not in the built-in list. There's a dedicated Custom OpenAI-compatible API option where you supply the endpoint URL, key, and model, so you can point MeghaOS at any compatible gateway or self-hosted server.

A few providers use their own native formats (Anthropic, Google Vertex AI, Amazon Bedrock); MeghaOS handles those directly.

Built-in providers

Choose any of these in Settings β€” the preset fills in the right endpoint for you.

How routing works

All calls are non-blocking, so MeghaOS stays responsive while the model thinks.

Live configuration

AI settings apply on the next request β€” no restart. Change provider, key, or model in Settings β†’ AI, or via POST /api/settings for scripting:

bash
curl -X POST http://127.0.0.1:8000/api/settings \
  -H "Content-Type: application/json" \
  -d '{"provider": "anthropic", "model": "claude-sonnet-4-6"}'

Vision (multimodal)

Providers that support image input power MeghaOS's vision features β€” screen analysis and camera/screenshot understanding. MeghaOS sends images in the right format for your provider (Anthropic vs. OpenAI-compatible).

Where the AI is used

Every intelligent step uses your configured model:

Choosing a model

Tip

For the richest generated UIs and reliable tool planning, use a strong instruction-following model. Capable models from any of the providers above work well; local providers (Ollama, LM Studio, vLLM) keep everything on-device with no API key and no data leaving your machine.