Cursor

Use Cursor with AutoDo

AutoDo adaptation

partial

Cursor behavior changes over time. AutoDo exposes the standard OpenAI-compatible /v1 endpoint; provider-specific /cursor normalization is not currently an AutoDo endpoint.

Beta: The Cursor integration is currently in beta. Behavior may change as Cursor updates their client.

What is Cursor?

Cursor is an AI-powered code editor built on VS Code. It features an agent mode for autonomous coding, tab completions, inline edits, a CLI, and cloud agents. Cursor ships its own in-house models (like Composer) alongside frontier models from OpenAI, Anthropic, Google, and more.

By routing Cursor through AutoDo, you get access to hundreds of models through a single API key, automatic provider failover, and centralized usage tracking.

Quick Start

Cursor supports AutoDo through its Override OpenAI Base URL feature. This routes requests from Cursor's OpenAI provider override through AutoDo's standard OpenAI-compatible endpoint.

Step 1: Get Your AutoDo API Key

Sign up or log in at AutoDo
Navigate to your API Keys page
Create a new API key
Copy your key (starts with sk-***)

Step 2: Configure Cursor

Open Cursor Settings (gear icon or Cmd/Ctrl + ,)
Navigate to Models, then expand the API Keys section
Toggle on OpenAI API Key, then:
- Paste your AutoDo API key into the OpenAI API Key field
- Toggle on Override OpenAI Base URL and set it to:
```
https://autodo.work/v1
```

Warning: Use https://autodo.work/v1 for AutoDo. The original provider-specific /api/v1/cursor endpoint is not currently an AutoDo endpoint.

Step 3: Add Models

After connecting, add the models you want to use. In the Models section, click + Add model and enter an AutoDo model ID:

~anthropic/claude-opus-latest
~openai/gpt-latest
~moonshotai/kimi-latest
deepseek/deepseek-v4-flash

Step 4: Select a Model

Open the model picker in the chat or agent panel and select one of the models you added. Your requests will now route through AutoDo.

How It Works

AutoDo exposes the standard OpenAI-compatible /v1 endpoint. If Cursor requires provider-specific request normalization for a feature, that feature may need a dedicated AutoDo compatibility endpoint before it works.

Why Use AutoDo with Cursor?

Access to Hundreds of Models

Cursor's built-in BYOK only supports a handful of providers. With AutoDo, you get access to hundreds of models across dozens of providers, all through the single OpenAI provider override.

Provider Failover

If one provider is unavailable or rate-limited, AutoDo automatically routes to another, keeping your coding sessions uninterrupted.

Organizational Controls

For teams, AutoDo provides centralized budget management. Set spending limits, allocate credits, and monitor usage across developers using Cursor from your AutoDo Activity Dashboard.

Usage Visibility

Track which models your team uses, monitor costs in real-time, and understand usage patterns from a single dashboard, regardless of the underlying provider. See the Activity page for a breakdown by model, user, and cost.

You can also control which upstream providers handle your requests. See the Provider Routing docs for details on routing suffixes like :nitro and :floor.

Limitations

Tab completions are not affected by BYOK settings; they always use Cursor's built-in models.
Auto and Composer 2 modes may not be routed through your API key. Check Cursor's docs for current behavior.
Only models accessible via AutoDo's OpenAI-compatible endpoint will work. Most chat and reasoning models are supported.

Troubleshooting

"Invalid API key": Make sure you're using your AutoDo API key (starts with sk-***), not an OpenAI key.
Model not found: Ensure the model ID exactly matches the format on autodo.work/models. Router model aliases need the ~ prefix (e.g., ~anthropic/claude-sonnet-latest, not anthropic/claude-sonnet-latest).
Base URL: The override URL must be https://autodo.work/v1. If a Cursor feature sends a provider-specific request shape, it may not work until AutoDo adds an equivalent compatibility endpoint.
Tool errors: If you see unexpected tool call failures, double-check whether you're pointed at the /cursor endpoint. AutoDo currently documents the generic /v1 endpoint; verify Cursor tool-call behavior before relying on it in production.