> ## 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.

# Cursor Provider

> Authenticate Cursor through the current CLIProxy provider path in CCS

# Cursor Provider

CCS now treats **Cursor** as a first-class CLIProxy OAuth provider. Use this
page for the current `ccs cursor` auth and account-management flow.

<Warning>
  The older local Cursor daemon bridge is still available only as deprecated
  compatibility under [`ccs legacy cursor`](/features/workflow/cursor). Do not use
  the old `ccs cursor auth/status/start/...` examples from earlier docs for new
  setups.
</Warning>

## Quick Start

```bash theme={null}
# Authenticate the current provider path
ccs cursor --auth

# Inspect accounts
ccs cursor --accounts

# Open provider config flow
ccs cursor --config

# Run a task through Cursor's CLIProxy route
ccs cursor "review this diff"
```

## Authentication Model

Cursor uses a **browser-driven polling flow** through CLIProxyAPIPlus:

* no local callback port is required
* CCS opens the upstream Cursor login page and polls for completion
* token refresh is delegated to CLIProxy

## Backend Requirement

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

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

If you force `--backend original`, Cursor auth will not be available.

## Config And Storage

Cursor is the only CLIProxy provider that stores its provider settings in a
dedicated namespace so it does not collide with the deprecated local bridge
files:

| Path                                             | Purpose                                     |
| ------------------------------------------------ | ------------------------------------------- |
| `~/.ccs/cliproxy/auth/`                          | shared OAuth token directory                |
| `~/.ccs/cliproxy/providers/cursor.settings.json` | current Cursor provider settings            |
| `~/.ccs/cursor.settings.json`                    | deprecated local Cursor IDE bridge settings |

## Commands You Will Actually Use

```bash theme={null}
ccs cursor --auth
ccs cursor --accounts
ccs cursor --use <account>
ccs cursor --nickname <name>
ccs cursor --config
ccs cursor --logout
```

## Current Scope

CCS documents Cursor here as a **provider-auth and routing surface**. The
provider is current and supported, but it does **not** currently participate in
the same local static model-catalog sync flow used by `agy`, `claude`,
`codex`, `gemini`, `ghcp`, `iflow`, `kimi`, and `kiro`.

Use the legacy bridge page only if you still need the reverse-engineered local
Cursor daemon compatibility path.

## Related

* [Provider Overview](/providers/concepts/overview)
* [CLIProxy API](/features/proxy/cliproxy-api)
* [Cursor IDE Bridge (Legacy)](/features/workflow/cursor)