> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dureai.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Provider support

> How Dure detects coding-agent CLIs and why resume, history, accounts, and migration support differ by provider.

Dure uses the provider CLI already installed on your machine. Provider names in
the app are adapters around those commands, not hosted model access.

## Capability levels

Provider support is capability-based. A provider may be launchable without
having every deeper integration:

| Capability        | Meaning                                                                                      |
| ----------------- | -------------------------------------------------------------------------------------------- |
| Launch            | Dure detects the executable and can start a fresh session.                                   |
| Continue          | A reviewed provider command continues the latest session.                                    |
| Exact resume      | Dure can restart one recorded provider-native conversation ID.                               |
| Conversation list | Dure can enumerate provider-owned records for a picker.                                      |
| Account profile   | Credentials can be selected per agent through a reviewed adapter.                            |
| Live adoption     | An existing ordinary terminal process can be replaced without losing the exact conversation. |

The UI only offers an action when the adapter declares and implements its
capability. Dure does not invent unsupported flags.

## Current reviewed integrations

The catalog includes Claude Code, Codex, Kimi Code, Gemini CLI, Cursor CLI,
GitHub Copilot CLI, OpenCode, Grok Build, Pi, and other installed coding-agent
commands.

Claude Code, Codex, and Kimi Code have the deepest account and resume integration
today. Gemini CLI, Cursor CLI, GitHub Copilot CLI, OpenCode, Grok Build, and Pi
also have reviewed continue and exact-resume commands. Conversation pickers,
forking, account isolation, credential copying, and live adoption remain
separate capabilities and are not implied by launch support.

<Note>
  Provider CLIs change independently of Dure. If a provider removes or changes a
  session command, Dure fails closed instead of guessing which conversation to
  open.
</Note>

## Installation and login

Install and log in to each provider with its official instructions. Restart Dure
after changing your login-shell `PATH` so provider detection sees the same
environment as a new terminal.

See [the session model](/en/session-model) for the difference between a provider
conversation and a Dure-managed runtime session.