# Supported agents and switching

> AI agents: read the [complete documentation index](https://chiefisnext.com/llms.txt). Append `.md` to any docs URL for its Markdown version.

Chief uses local CLI agents through the relay. The **Chief** provider handles planning and reasoning; **Agents** selects the project's default worker for tasks. You can use different ready providers for the two roles.

## Install and authenticate on the relay computer

Open [Tutorial](https://chiefisnext.com/app/onboarding) in Chief for installation commands for your operating system and readiness checks. Install and sign in on the same computer that runs `chief-relay`. Provider subscriptions, API billing and permissions are separate from your Chief account.

| Agent | Local command or credential setup |
| --- | --- |
| Claude Code | Run `claude` and follow its browser sign-in prompts. |
| OpenAI Codex | Run `codex` and choose Sign in with ChatGPT. |
| Gemini (Antigravity CLI) | Run `agy` and sign in with your Google account. |
| Muse Code | Run `muse login` with your Muse subscription. |
| Kimi Code | Run `kimi`, then `/login`. |
| Qwen Code | Run `qwen`, then `/auth` for your Coding Plan or API provider. |
| OpenCode | Run `opencode`, then `/connect` for a model provider. |
| DeepSeek Harness | Install `dsh` and configure `DEEPSEEK_API_KEY` in the local credentials file using Tutorial's instructions. |

Keep API keys on the relay computer; do not paste them into project chat. For DeepSeek Harness, the local health check checks configuration rather than validating the key or balance. An API rejection during execution still needs attention even if the local check passed.

**Expected result:** Tutorial shows a ready agent. If you installed an agent after starting the relay, restart `chief-relay` so it can discover the command and updated environment.

## Switch the project providers

1. Open the project and check that the intended provider is ready.
2. Use **Chief** in the header to change the planning provider.
3. Use **Agents** in the header to change the default worker for subsequent work. On a narrow screen, the selectors show provider names without the prefixes.
4. Confirm the selector retains the new choice. If saving is rejected, read the error; the prior saved selection remains in effect.

Project settings offer the same roles as **Brain provider** and **Default provider**, with a save action. Changing a default does not move an already-running process to another agent.

During [auto mode](https://chiefisnext.com/docs/auto-mode), the worker remains fixed and the **Agents** selector is locked, including while paused. Disable auto mode before changing the default worker, then enable a new run if desired.

## Choose an agent for one proposal

Before approving a proposal, use its provider selector. **Default (provider)** uses the project default; selecting another ready provider overrides it for that task. Check the selected agent and [definition of done](https://chiefisnext.com/docs/milestones) before pressing **Go** or **Queue**.

## OpenCode model families

When a healthy OpenCode installation reports available model families, the selectors show those families, such as **Claude (OpenCode)** or **OpenAI (OpenCode)**. The choices depend on your local OpenCode connections. If those choices are missing, check OpenCode's `/connect` setup on the relay computer and its health before trying again.

## Recover agent readiness

If credentials have expired, sign in again using the relevant local command above, then check readiness in Tutorial. A health-check timeout or unknown status alone does not establish that credentials expired; retry the check and read its guidance before signing in again or switching providers.

See [credential troubleshooting](https://chiefisnext.com/docs/troubleshooting#expired-agent-credentials) for recovery and [MCP connector setup](https://chiefisnext.com/docs/mcp) if you want your assistant to query Chief. Choosing a task agent and connecting an assistant to Chief are separate setup steps.