Provider guides
Use the built-in Tejus agent, or install, authenticate, verify, and connect every coding-agent CLI supported by Tejus on Windows.
Tejus works with two kinds of agents:
- Tejus, the agent built into the app. It needs no install and runs on Tejus Cloud models after you sign in with Google, or on your own API keys.
- CLI agents such as Claude Code, Codex, and Cursor, which you install and sign in to on your machine. Tejus finds the CLI, checks its status, and runs it for you.
These guides explain what each agent owns, how to check it on its own, and what Tejus adds around the provider session.
For CLI agents, sign-in, subscriptions, API keys, model access, and service availability stay with the provider. Tejus supplies the shared workspace, task lifecycle, Git environment, terminal, browser, diff, and review surfaces around that runtime.
Supported agents
| Provider | Default executable | Typical authentication | Steer an active turn |
|---|---|---|---|
| Tejus | Built in (no CLI) | Google sign-in for Tejus Cloud, or your own API keys | No |
| Claude Code | claude | Claude account, Console, Bedrock, Vertex, or Foundry | Yes |
| Codex | codex | ChatGPT account, API key, or configured model provider | Yes |
| OpenCode | opencode | Credentials configured inside OpenCode | No |
| Cursor | cursor-agent | Cursor browser login or CURSOR_API_KEY | No |
| Antigravity | agy | Google sign-in stored by Antigravity | No |
| Grok | grok | grok login session or XAI_API_KEY | No |
| Devin | devin | devin auth login or WINDSURF_API_KEY | No |
| Pi | pi | Pi /login or a model-provider API key | Yes |
| Factory Droid | droid | Browser device pairing or FACTORY_API_KEY | No |
| Oh My Pi | omp | Oh My Pi /login (credentials under its agent directory) | No |
“Steer an active turn” means Tejus can send a follow-up into the provider while its current turn is still running. It does not mean the provider will always act on the message immediately.
Choose a provider
New to Tejus? Start with the built-in Tejus agent: it works as soon as you sign in. Add CLI agents for the accounts and runtimes you already trust; they do not all behave the same.
- Account access: confirm a CLI works in its own terminal before debugging Tejus.
- Models: Tejus shows what the installed runtime and account expose.
- Permissions: approval and autonomy rules stay provider-specific even though Tejus presents them consistently.
- Session behavior: resume, compaction, plan mode, subagents, and live steering vary by provider.
- Updates: an old CLI can be installed and signed in while still being too old for the integration Tejus expects.
Connect a CLI agent
Install the official CLI
Use the provider's official Windows install method (usually npm or a PowerShell installer). Avoid similarly named third-party packages.
Sign in
Open Settings → Agent providers, expand the provider under Provider tools, and click Sign in. Tejus opens the provider's own login command in a terminal window; follow its prompts, then click Check authentication. You can also sign in from a normal terminal.
Verify the executable
Run its version command from a new PowerShell window. Tejus reads your saved user and system PATH from Windows when it starts, so restart Tejus after installing a CLI while it is open.
Enable it in Tejus
Under Provider activity, keep the provider enabled and click Refresh status. Set a binary path (expand the provider under Provider tools, then Runtime) only when automatic discovery does not find the installation you want.
Run a bounded test task
Use a disposable repository or a harmless read-only request before granting broad permissions in important work.
Windows notes
- CLIs installed with npm (
.cmdshims) and PowerShell (.ps1) launchers are supported. - To give a CLI an API key without changing your Windows environment, add it under the provider's Environment section in Provider tools and turn on the secret switch so the value is stored redacted. These variables apply only to that provider account's processes.
- If you open a project from a WSL path such as
\\wsl.localhost\Ubuntu\home\you\repo, Tejus launches provider CLIs inside that WSL distribution, so the CLI must be installed and signed in there. - Settings → Agent providers → Updates checks installed CLIs for newer versions and offers Update when Tejus can safely run the provider's own update command; otherwise it shows Manual update.
Provider guides
When a provider is missing
Start with the provider's guide, then continue to Provider troubleshooting. When you report a problem, include the executable path, version, sign-in state, and the exact Tejus message. Remove tokens, keys, account identifiers, and private paths before sharing diagnostics.