Skip to main content
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: 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.
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.

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 for the difference between a provider conversation and a Dure-managed runtime session.