Skip to main content
ADE can route chats, CTO work, and workers through multiple providers. Configure at least one provider before starting agent work.

Supported paths

ProviderTypical use
Claude / Claude CodeGeneral coding, planning, review, and worker tasks.
CodexOpenAI coding workflows and CLI-backed sessions.
CursorCursor agent sessions through the Cursor SDK.
OpenCodeLocal or provider-backed OpenCode workflows.
OpenRouter / local endpointsCost routing, experimentation, or local models.

Configure a provider

1

Open Settings -> AI Providers

Choose the provider you want to use.
2

Add credentials or sign in

Paste an API key, configure a local endpoint, or authenticate the provider CLI.
3

Verify

Run the provider check and make sure ADE can start a session.
4

Choose defaults

Set your default chat model and any role-specific overrides you need.

Permission presets

Providers expose different native permission models. ADE maps them into a small set of practical choices:
Preset styleUse it when
Plan / read-onlyYou want the agent to inspect and propose first.
Default / editYou trust the lane and want normal coding flow.
Full accessYou are in a trusted environment and want minimal prompts.
CustomYou want the provider’s own config to decide.

Cost control

Running several agents in parallel can spend quickly. Use cheaper models for routine follow-up and stronger models for planning, architecture, and hard debugging. Review usage from Settings -> Usage.
Provider calls go directly from your machine to the provider or local endpoint you configure. Keep keys out of committed files.