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

# Qoder Provider

> Use Qoder through CCS as a CLIProxy device-code provider

# Qoder Provider

CCS supports **Qoder** as a CLIProxy provider for AI coding workflows.

## Quick Start

```bash theme={null}
ccs qoder --auth
ccs qoder --accounts
ccs qoder --config
ccs qoder "review this change"
```

## Authentication Model

Qoder uses a **device-code flow**:

* no local callback port is required
* CCS opens or prints the Qoder device login URL
* CCS currently treats token refresh as unsupported, so re-run `ccs qoder --auth`
  if upstream auth expires

## Model Selection

Qoder supports the interactive model picker:

```bash theme={null}
ccs qoder --config
```

The default route is `qoder/auto`. The static fallback catalog also includes
Qoder tier routes such as `qoder/ultimate`, `qoder/performance`,
`qoder/efficient`, and `qoder/lite`.

## Backend Requirement

Qoder is a **plus-only** provider.

```yaml theme={null}
cliproxy:
  backend: plus
```

## Config And Storage

| Path                         | Purpose                                              |
| ---------------------------- | ---------------------------------------------------- |
| `~/.ccs/cliproxy/auth/`      | shared OAuth token directory                         |
| `~/.ccs/qoder.settings.json` | provider settings when a local settings file is used |

## Related

* [Provider Overview](/providers/concepts/overview)
* [CLIProxy API](/features/proxy/cliproxy-api)