Skip to main content
Dure uses your installed coding-agent CLIs and provider accounts. The provider supplies the models, authentication and billing; Dure keeps the working context and views together.

Prepare and select a provider

Open Settings → Agent CLI to inspect detection and setup information. Start with a CLI that works in your regular terminal. In the Basic interface, the launcher offers Claude Code, Codex and Kimi Code. Choose Beta in Settings → General → Interface mode to add Pi, Gemini CLI, OpenCode and the other registered tools. Choose the provider in ⌘N → New agent. New agents open as native terminal panes. In Beta, Settings → General → Default agent pane can open supported new agents in Chat instead. A registered command is not a promise that every model, account feature or conversation operation is available.

Understand the available capabilities

In Beta, Claude Code, Codex, OpenCode and Pi have structured-chat integrations; availability also depends on the installed tool and runtime. Other tools can remain in their native terminal interface. An agent’s status (working, waiting for your input or approval, or idle) comes from the tool’s own lifecycle events. Claude Code and Codex report it on every platform; Gemini CLI, Qwen Code, Pi, OpenClaude, OpenCode and Kilo Code terminal panes report it on macOS and Linux. An OpenCode or Kilo Code launch with OPENCODE_CONFIG_CONTENT or KILO_CONFIG_CONTENT already set keeps your value and does not report. A Kilo Code pane does not report while it is attached to a kilo daemon you started, because its turns run in the daemon. Other tools show only whether their process is running, so they can look idle while they work.

An example Codex conversation in a Dure pane.

Choose an account

Open Settings → AI provider accounts to add supported account profiles. Select the intended account when starting an agent or from its account control. Providers without this integration use their normal configured login. Account switching may restart the provider process and resume its conversation. Review the pending switch and any sign-in requirement; moving a pane does not switch its account. Remote projects also need provider setup on the remote host. On a headless backend, sign in on that host with the provider’s own CLI, pointed at a directory like codex-work under ~/.dure/accounts, with both folders closed to other users (chmod 700). Then run dure accounts register codex --dir codex-work --backend SERVER. The directory name becomes the account ID, and running the command again keeps it. Dure does not run the sign-in or copy credentials between machines, and these accounts do not appear in the desktop account list yet. dure accounts help has the exact sign-in commands. To use the provider’s default login on a backend without registering it, run dure runs switch-account RUN --account default --confirm-restart.

Read usage and limits

Claude and Codex usage controls show available provider-reported limits and reset times. Show or hide their top-bar indicators in Settings → Appearance → Status bar and inspect broader activity in Stats and usage. An absent or stale reading does not establish spare capacity. Settings → General → Automatic account recovery · Beta configures recovery on the selected server. Choose a provider, enable recovery, select the accounts that server may use, and save. The server can switch supported Chat conversations and continue their original request with every Dure window closed. Joining a shared workspace never offers your personal accounts automatically. Fresh available usage is preferred; unknown or stale usage does not prevent trying an allowed account. A failed or uncertain attempt remains visible and is not blindly resent. Later human input takes priority. Manual account switching remains available, and authentication failures still need attention. Use dure recovery get codex --backend SERVER --json to inspect the policy and registered profile handles, or dure recovery status AGENT_ID --backend SERVER --json to read a recovery outcome. dure recovery help describes revision-based edits and optional usage observations. These commands connect directly to the selected backend. Default provider and permission choices are under Settings → General. Choose permissions for the actual task; worktrees do not create a sandbox.