← Back to docs

Securely connect your Cursor, Windsurf and other AI IDE accounts to Dawvia — the first step to a shared account pool.

Connect Cursor and Windsurf accounts

Picking up from Getting Started, this guide walks you through connecting multiple Cursor multi-account and Windsurf multi-account logins — plus any other AI IDE — to Dawvia, so you are ready to build a shared account pool. Credentials are encrypted end to end, so teammates never pass passwords around again.

Before you begin

  • You have installed the extension and signed in per Getting Started.
  • You have at least one working Cursor or Windsurf account; see free trial limits on the pricing page.
  • To host the site standalone on a server, see the deployment guide.

Step 1: Open the account wizard

Run the connect wizard from the command palette:

dawvia accounts add

The wizard lets you pick a platform (Cursor / Windsurf / other compatible AI IDE) and stores the credential encrypted. Credentials stay local and inside your domain — keys never land or leak. See Security & compliance for details.

Step 2: Register account credentials

Paste a credential or complete OAuth per platform:

dawvia accounts add --platform cursor --label cursor-pro-01
dawvia accounts add --platform windsurf --label windsurf-team
  • --label is a readable alias inside the pool. Name accounts like platform-plan-index

for easier observability.

  • Register many accounts per platform; together they take part in

quota balancing.

Step 3: Verify the connection

Confirm each account's health and login state:

dawvia accounts list

The output lists alias, platform, remaining quota and health. If an account misbehaves, Dawvia isolates it automatically without affecting the rest of the pool.

Step 4: Pool and allocate

Once accounts are ready, build a shared pool and allocate by team, department or member:

  • Read Account pool for the pooling model and on-demand allocation.
  • Read Team & organization management for seats, roles and department grants.
  • To route requests across accounts and fail over on rate limits, continue to

Quota balancing and Autopilot orchestration.

FAQ

Does connecting expose my account password?

No. Credentials are encrypted end to end and keys never land; every call and change is auditable. See Security & compliance and the privacy policy.

How many accounts can a team connect?

The Free plan supports single-account pooling; balancing, orchestration and MCP start on Pro, and enterprise governance starts on Team. Compare tiers on the features overview and the pricing page.

Next steps