Cursor Editor Setup

Connect QCode.cc to Cursor IDE through custom Anthropic / OpenAI endpoints, with support for Cursor v3's Agents Window and Design Mode

Cursor Editor Setup¶

Cursor is an AI-native editor built on top of VS Code. Cursor v3 (released 2026-04) introduces three major new capabilities: Agents Window (multi-agent coordination), Design Mode (visual design synced with code), and CLI agents (sub-agents inside the terminal). This guide shows how to configure QCode.cc as the upstream model source for Cursor.

Why Use Cursor¶

• Agents Window (new in v3): run multiple AI agents in parallel in the sidebar without interference
• Cursor Composer: multi-file editing with context-aware refactoring, better suited than Cursor Chat for large changes
• Inline Edit (Cmd+K): select code and issue an instruction inline — the fastest iteration loop
• Built on VS Code: inherits the entire VS Code extension ecosystem (including the Claude Code VS Code extension)

Prerequisites¶

• Cursor installed (macOS / Windows / Linux)
• A QCode.cc API Key (starts with cr_), available from the dashboard

Configuration Steps¶

Cursor offers two integration paths — pick the one that fits your scenario.

Path A: Custom OpenAI-compatible endpoint (recommended)¶

Use the OpenAI protocol to talk to QCode's /openai/v1 path, giving you access to GPT-5.5 / GPT-5.4 / Gemini and other model families.

1. Open Cursor settings: Cmd + , (macOS) / Ctrl + , (Windows/Linux)
2. Models → scroll to the bottom and find Override OpenAI Base URL
3. Fill in:

1. In the Models list, check the models you want to enable (e.g., gpt-5.5, gpt-5.4-codex); for any model not listed, click + Add model and enter the model id manually
2. Click Verify to test connectivity; once it passes, you can use it from Cursor Chat / Composer

Path B: Custom Anthropic endpoint (for Claude)¶

⚠️ Known limitation: Cursor's Anthropic integration uses an OpenAI Responses API style under Agent mode, which is incompatible with QCode's Anthropic protocol path in certain scenarios (manifesting as failed schema conversion for some tool calls). We recommend Path A (OpenAI protocol). To use Claude models, add model ids such as claude-opus-4-7 under Path A — QCode passes Claude models through transparently at the OpenAI protocol layer.

Fallback Endpoints¶

For the full endpoint reference (including North America, Europe, and Asia fallbacks), see Endpoints and API Paths.

Using Alongside Claude Code¶

Cursor's built-in AI does not conflict with the standalone Claude Code CLI — both can run side-by-side in the same Cursor window:

• Cursor Chat / Composer: in-editor AI that uses the endpoint configured in Cursor settings
• Claude Code CLI: run claude in Cursor's integrated terminal (Ctrl + `); it uses the CLI's own ANTHROPIC_BASE_URL environment variable

The two paths authenticate independently, but using the same QCode API Key on both means shared quota (see Billing for details).

Limitations and Notes¶

• Privacy Mode: Cursor sends code snippets to the configured endpoint by default. If you have Privacy Mode enabled in Cursor settings, confirm that the API Key configuration still lets you reach QCode; Privacy Mode does not affect outbound traffic, it only blocks Cursor itself from storing your prompts
• A Cursor Pro subscription and a QCode API Key are two independent systems — Cursor Pro grants you Cursor's built-in quota (using Cursor's own GPT-4 pool), while the QCode API Key uses our gateway pool. When both are active, routing follows the priority configured in Cursor
• Cursor v3 Agents Window has the most stable compatibility with the OpenAI / Anthropic protocols today; support for non-mainstream providers (such as self-hosted OSS models) varies

FAQ¶

Cursor reports "API key not valid"¶

1. Verify the API Key is complete, starts with cr_, and has no leading or trailing whitespace
2. Click Verify in Cursor settings to see the specific error
3. Test connectivity from the command line: bash curl -H "Authorization: Bearer YOUR_KEY" \ http://103.236.53.153/openai/v1/models If the response is a JSON list, both the endpoint and the API Key are OK

Composer cannot use Claude models¶

Since Cursor v2, Composer defaults to the OpenAI protocol; to select Claude, you must manually add model ids such as claude-opus-4-7 to the Models list (even though QCode passes Claude models through over the OpenAI protocol, Cursor still needs to recognize the model id before it shows up in the dropdown).

Inline Edit (Cmd+K) is slow¶

Cursor's Cmd+K defaults to Cursor's own fast model; switching to QCode routes through the configured base URL, so first-token latency is slightly higher than Cursor's built-in option (one extra hop). In settings, you can keep Cursor Tab on Cursor's default while routing Chat / Composer through the QCode endpoint.

Next Steps¶

• VS Code Integration — same-family editor with shared configuration patterns
• Endpoints and API Paths — full reference for QCode.cc's three protocols and four ingress domains
• Claude Code Tutorial — CLI workflow reference
• Billing — shared quota rules