SynaraProviders
Understand how Synara connects to the coding-agent runtimes and accounts already installed on your machine.
Synara does not host models or sell a separate model subscription. It operates supported coding-agent runtimes installed and authenticated on your machine, then presents them through one consistent workspace.
Supported providers
| Provider | What Synara connects to |
|---|---|
| Claude Code | Your installed Claude Code runtime and authenticated account |
| Codex | Your installed and authenticated Codex CLI |
| OpenCode | Your local OpenCode runtime and configured model providers |
| Cursor | Your local Cursor agent runtime and account |
| Antigravity | Your installed and authenticated Antigravity CLI |
| Grok Build | Your configured Grok Build runtime and access |
| Kilo Code | Your Kilo Code runtime and configured credentials |
| Pi | Pi and the model providers configured through it |
| Factory Droid | Your installed and authenticated Droid runtime |
Provider availability can differ between the current stable release and development builds. Use the provider settings in your installed Synara version as the authoritative list for that build.
What Synara manages
Synara provides the shared operating surface around each provider:
- Project and task ownership
- Provider and model selection
- Conversation and tool activity
- Approvals and user-input requests
- Terminal, browser, file, and diff surfaces
- Git environments and checkpoints
- Session continuation where supported
- Provider handoffs
- Usage information where the provider exposes it
What remains provider-owned
The provider still controls:
- Installation
- Authentication
- Account and subscription limits
- Model availability
- Tool behavior
- Permission semantics
- Service availability
- Provider-specific session features
A provider working in its own terminal is an important prerequisite, but not a guarantee that every provider feature is supported through Synara.
Connect a provider
Install the official runtime
Use the provider's official installation instructions.
Authenticate outside Synara
Complete the provider's normal sign-in or credential setup. Verify the runtime from a fresh terminal.
Open Synara provider settings
Confirm that the provider is detected and enabled. When necessary, configure a custom path to the provider executable.
Check model discovery
Open the model picker and confirm that the expected models and options appear.
Synara discovers many provider capabilities at runtime. The result can depend on the installed CLI version, account, subscription, and provider configuration.
Start a small test task
Use a harmless objective in a test repository before relying on a newly configured provider for important work.
Models and effort options
Providers expose different selection models:
- A fixed catalog
- A catalog discovered from the installed runtime
- User-configured custom models
- Reasoning, effort, mode, or variant options
- Account-dependent availability
Synara normalizes these choices into the composer where possible without pretending that every provider has identical capabilities.
Favorite models can be surfaced above larger catalogs, and supported provider executables can be pointed at custom binary locations.
Provider sessions
Each task owns a provider session.
The session may preserve provider-specific behavior such as:
- Plans
- Tool calls
- Approvals
- Reasoning summaries
- Context usage
- Model changes
- Resume or reconnect behavior
- Provider-native subagents or workflows
Capabilities vary. Do not assume a control available for one provider exists for all of them.
Switching providers
A provider handoff allows another provider to continue the task and work in the same environment with the context Synara passes to it.
Use handoffs deliberately. Review the working tree before and after changing providers so ownership remains clear.
When a provider is missing
Check these in order:
- Does the executable run from a fresh terminal?
- Is the provider authenticated?
- Is the expected executable on
PATH? - Is a custom binary path configured incorrectly?
- Does the installed runtime version support the required integration?
- Does restarting Synara refresh the provider status?
- Does the provider itself report a service or account error?
Continue with Troubleshooting when the runtime works independently but remains unavailable in Synara.
Open the Provider guides for exact installation, authentication, verification, capabilities, update paths, and provider-specific failure checks.