Providers
Understand how Tejus runs the built-in Tejus agent and connects to the coding-agent runtimes already installed on your machine.
Tejus can run coding agents in two ways. The built-in Tejus agent needs nothing installed: it uses Tejus Cloud models after you sign in with Google, or models from your own API keys. Tejus also operates supported coding-agent CLIs that are installed and authenticated on your machine, and presents every provider through one consistent workspace.
Supported providers
| Provider | What Tejus connects to |
|---|---|
| Tejus (built-in) | Tejus Cloud models through your Tejus account, or your own API keys. Nothing to install |
| 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 |
| Devin CLI | Your installed and authenticated Devin CLI runtime |
| Pi | Pi and the model providers configured through it |
| Factory Droid | Your installed and authenticated Droid runtime |
| Oh My Pi | Your installed omp runtime and ~/.omp credentials |
The provider list in Settings → Agent providers is the authoritative list for your installed version.
The built-in Tejus agent
New chats start with the Tejus agent. It has two sources of models:
- Tejus Cloud: sign in with Google under Settings → Account and activate your account from the e-mail Tejus sends. The free plan includes a daily allowance of cloud tokens; Settings → Plan & Usage shows what you used and when it resets.
- Your own API keys: add keys for OpenAI, Anthropic, Google Gemini, DeepSeek, xAI Grok, Mistral, Groq, Cerebras, Moonshot (Kimi), or OpenRouter under Settings → Your API keys. Keys are stored in Windows Credential Manager, requests go directly to that provider, and these models work without a Tejus account.
Both appear under the Tejus tab of the model picker. See Tejus Cloud for setup, plans, and usage.
What Tejus manages
Tejus 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, IDE, file, and diff surfaces
- Git environments and checkpoints
- Security review of the files an agent changed
- Session continuation where supported
- Provider handoffs
- Usage information where the provider exposes it
What remains provider-owned
For a coding-agent CLI, 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 Tejus.
Connect a coding-agent CLI
Install the official runtime
Use the provider's official installation instructions for Windows.
Authenticate outside Tejus
Complete the provider's normal sign-in or credential setup. Verify the runtime from a fresh terminal.
Open Settings → Agent providers
Confirm that the provider is detected and enabled. When necessary, configure a custom path to the provider executable.
The switch beside each provider allows background checks and new turns; it does not install the runtime or sign you in. Check the setup status beneath each provider, open its Setup guide for installation and authentication instructions, then select Refresh status after completing setup.
Some providers, including OpenCode, do not expose an authentication check to Tejus. Installed · sign-in not verified means the runtime was detected, but you still need to configure and verify your model-provider credentials in that runtime.
Check model discovery
Open the model picker and confirm that the expected models and options appear.
Tejus 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 or your account
- User-configured custom models
- Reasoning, effort, mode, or variant options
- Account-dependent availability
Tejus 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 Tejus passes to it.
Use handoffs deliberately. Review the working tree before and after changing providers so ownership remains clear.
When a provider is missing
For the Tejus agent, check that you are signed in and activated under Settings → Account, or that a key is saved under Settings → Your API keys.
For a coding-agent CLI, 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 Refresh status or restarting Tejus update 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 Tejus.
Open the Provider guides for exact installation, authentication, verification, capabilities, update paths, and provider-specific failure checks.