Connect Agent Providers

Every agent runs under your own provider account, so you must connect a provider before running a task with it — including the default agent, Codex. Each provider has its own connect flow — a device OAuth, an API key, a setup token, or an uploaded auth file. Connections live at the account level and apply to every project. Connect from the web app under Settings → Connections, or with the CLI. Each provider’s CLI commands share the same shape: connect, status, and a disconnect command.

Codex

Codex supports two methods: a ChatGPT-subscription device login, or an API key.

In Settings → Connections, choose Codex and either start the device login or paste an API key.

Connect with your ChatGPT subscription using the device flow. The command prints a verification URL and a code, opens your browser, and polls until you authorize:

aether codex connect

Or store an API key instead (prompted if you omit --api-key):

aether codex api-key --api-key sk-...

Check or remove the connection:

aether codex status
aether codex logout

The device flow stores subscription tokens that Aether refreshes as needed. The underlying endpoints are POST /codex/device-auth/start, POST /codex/device-auth/poll, PUT /codex/auth/api-key, and GET/DELETE /codex/auth — see the Codex auth API.

Claude Code

Claude Code authenticates with a setup token generated by the Claude CLI.

In Settings → Connections, choose Claude Code and paste the setup token printed by claude setup-token.

aether claude-code connect runs claude setup-token for you, captures the resulting token, and stores it:

aether claude-code connect

This requires the Claude Code CLI. If it’s missing, install it with npm install -g @anthropic-ai/claude-code and rerun the command.Check or remove the connection:

aether claude-code status
aether claude-code disconnect

The token is sent to PUT /claude-code/auth/setup-token — see the Claude Code auth API.

Cursor

Cursor imports the OAuth subscription tokens written by your local Cursor login (cursor-agent login).

In Settings → Connections, choose Cursor and provide your Cursor subscription tokens.

aether cursor connect

On macOS this reads the access and refresh tokens from the login keychain (cursor-access-token / cursor-refresh-token). On Linux it reads ${XDG_CONFIG_HOME:-~/.config}/cursor/auth.json.Check or remove the connection:

aether cursor status
aether cursor disconnect

Aether stores both tokens and rotates them as Cursor refreshes them. The import posts to PUT /cursor/auth/subscription — see the Cursor auth API.

OpenCode

OpenCode authenticates with the auth.json file written by your local OpenCode login (opencode auth login). The file is uploaded verbatim and materialized into each task’s config directory at session start.

In Settings → Connections, choose OpenCode and upload your auth.json.

aether opencode connect

This reads ${XDG_DATA_HOME:-~/.local/share}/opencode/auth.json.Check or remove the connection:

aether opencode status
aether opencode disconnect

The file is sent to PUT /opencode/auth/file — see the OpenCode auth API.

OpenCode models routed through OpenRouter can additionally use your own OpenRouter API key (aether apikey add --provider openrouter). See Agents and models.

Getting Started

Using Aether

Connect Agent Providers

Codex

Claude Code

Cursor

OpenCode

Next Steps

Agents and Models

Tasks

​Codex

​Claude Code

​Cursor

​OpenCode

​Next Steps

Agents and Models

Tasks

Codex

Claude Code

Cursor

OpenCode

Next Steps