Model Providers
Configure cloud and local model providers in Msty Claw
Providers determine how Claw resolves model calls for chats, bots, playbooks, and tasks. A stable provider setup is the baseline for reliable execution quality.
Open Settings > Providers to configure and manage them.
Provider strategy
Most teams use one of these patterns:
- Single-provider baseline for simplicity
- Primary + fallback provider for resilience
- Local provider for privacy-sensitive workflows
Provider configuration
For each provider, configure:
- Type
- Display name
- Base URL
- API key (when required)
- Model list behavior
Local vs cloud
- Cloud providers use credentials and remote endpoints
- Local providers use local service endpoints
Guidance:
- Validate local endpoint health before assigning bots
- Test at least one fallback path for critical workflows
Model catalog and custom models
For non-managed providers, you can add custom model entries manually.
Optional model metadata:
- Context window tokens
- Reserved output tokens
Use metadata to reduce truncation and improve routing predictability.
Managed model downloads
For managed-compatible local providers, Claw can expose in-app model download controls after provider save.
In-chat model controls
Recent releases added faster model listing/switching controls in chat flows. Use this to recover quickly from model-specific failures during active sessions.
Practical recommendations
- Start with one well-tested default model
- Add specialized models only for clear use cases
- Re-test critical bots after provider/model default changes