Providers
TatsuCode supports multiple provider types so you can choose the best tradeoff between cost, speed, privacy, and model variety.
Independent product. TatsuCode is not affiliated with, endorsed by, or sponsored by Anthropic, OpenAI, Google, GitHub/Microsoft, OpenRouter, or any other provider listed below. All product names and trademarks belong to their respective owners. See Third-Party Services for full attributions.
Primary command:/connectAlias:/providersSee also: CLI vs API/Subscription Providers — when to use which, what each can and cannot do as a Task Agent or SubAgent, and how Cross-Agent Relay fits in.
Provider Options at a Glance
| Provider Type | Cost Model | Best For |
|---|---|---|
| OAuth Subscriptions | Usually $0 extra | Reusing plans you already pay for |
| OpenRouter API | Pay-per-use | Maximum model variety in one place |
| Local Providers | Free after setup | Privacy, offline work, fixed cost hardware |
| CLI Providers (Claude Code, Gemini CLI on roadmap) | Subscription-backed | Delegated, archived agent runs with Cross-Agent Relay |
OAuth Providers (Use Existing Subscriptions)
If you already pay for AI subscriptions, connect supported routes directly and use that quota inside TatsuCode.
OpenAI Plus / Pro
Subscription: chatgpt.com
To connect:
- Run
/connect - Select OpenAI Plus/Pro
- Sign in and approve access
- Complete sign-in and return to TatsuCode when prompted
GitHub Copilot
Subscription: github.com/features/copilot/plans
To connect:
- Run
/connect - Select GitHub Copilot
- Sign in and approve access
- Complete sign-in and return to TatsuCode when prompted
For broader model coverage, use OpenRouter API key access.
Claude Agent (Claude Code)
Subscription: Claude Pro, Max, Team, or Enterprise on claude.ai
To connect:
- Run
/connect - Select Claude Agent (Claude Code)
- Sign in to your Anthropic account in the browser and approve access
- Return to TatsuCode — the Claude Code models appear in
/models
Claude Code runs as a CLI provider — it brings its own auth and tool loop, and produces archived report.md artifacts on every run. For deep details, see Claude Code and the CLI Providers overview.
Free Claude.ai accounts can't run Claude Code; an active paid subscription is required.
OpenRouter (API Key)
OpenRouter gives you access to a large cross-provider catalog from one key.
Why OpenRouter
- One API key for many model families
- Fast switching between providers
- Pay only for usage
- Easy fallback when one provider is unavailable
Setup
- Create account: openrouter.ai
- Add credits
- Create API key: openrouter.ai/keys
- Run
/connect - Open OpenRouter
- Paste key and save
Quota and Spend Monitoring
Use:
/usage
/usage-quota
/usage-quota now includes clearer subscription/quota visibility and OpenRouter balance/usage summaries in recent builds.
Local Providers (Ollama, LM Studio, etc.)
For local/private workflows, add a custom OpenAI-compatible endpoint.
Local Endpoint Setup
Use the endpoint URL provided by your local model server.
Examples depend on your local server configuration and should be taken from your server's own documentation.
Setup Flow
- Start your local server
- Run
/connect - Choose Add Custom Provider
- Enter name + URL
- Save and test
- Run
/modelsto pick a model
Web Search Providers
TatsuCode can be configured with your own search API keys.
- Google Programmable Search
- Brave Search API
Configure them inside /connect under the Web Search section.
Connection Management Tips
Inside Provider Connections you can:
- Connect/disconnect providers
- Verify API keys
- View available model counts
- Switch fallback providers if one is down
If a provider is removed, TatsuCode now handles model fallback more gracefully so you can keep working.
Troubleshooting
Invalid API Key
- Re-copy key from provider dashboard
- Remove leading/trailing spaces
- Confirm key is active
OAuth Won't Complete
- Try disconnect + reconnect
- Retry promptly if the sign-in step expires
- Retry from a fresh browser session
Local Provider Not Reachable
- Confirm your local server is running
- Re-check the configured endpoint
- Validate local network/firewall policy
Next Steps
- Models — choose the best model per task
- Settings — tune behavior and defaults
- Troubleshooting — common issues and fixes