Devin Desktop (formerly Windsurf) Setup

Windsurf is now Devin Desktop and is built around ACP: attach Claude Code as an ACP agent with its environment pointed at QCode

Devin Desktop (formerly Windsurf) Setup¶

⚠️ Windsurf was renamed. On 2026-06-02 Cognition renamed Windsurf to Devin Desktop and shipped it as an over-the-air update; plans, pricing, settings, extensions, keybindings and MCP connections all carried over with no user action. The original Cascade agent was deprecated on 2026-07-01.

Devin Desktop is now built around ACP (Agent Client Protocol): it acts as the host, and you attach any ACP-speaking agent — Claude Code, Codex CLI, OpenCode and others. New capabilities include a Kanban-style Command Center, Spaces for grouping tasks, a local Rust agent (Devin Local) and Codemaps.

The right way to use QCode: go through ACP, not the built-in BYOK¶

Devin Desktop does offer built-in BYOK, but it covers only select cloud models and still routes to that provider's own cloud API. To use your QCode key and quota, take the ACP route:

🔑 ACP hosts launch the agent as a child process, so it inherits your environment. Configure the Claude Code CLI against QCode once, and sessions inside Devin Desktop follow.

Step 1: point Claude Code at QCode¶

export ANTHROPIC_BASE_URL="https://api.qcode.cc/api"
export ANTHROPIC_AUTH_TOKEN="cr_your_qcode_key"

From mainland China, use https://asia.qcode.cc/api.

More robust: put these in the env block of ~/.claude/settings.json rather than a shell profile — a GUI app launched from an icon does not read ~/.zshrc, which is the most common failure. See ACP Overview and Environment Variables.

Confirm the CLI works from a terminal first:

claude -p "reply with exactly: OK"

Step 2: attach the agent inside Devin Desktop¶

Devin Desktop ships with Codex CLI, Claude Agent and OpenCode; individual users can also add custom agents by editing the local ACP agent registry file. Menu locations and the registry path follow Devin's official docs — the product is still moving quickly.

Once attached, open a session in Devin Desktop. A normal reply means it is spending your QCode quota.

Verify traffic really goes to QCode¶

Open probe.qcode.cc and enter your API key. The session you just ran should appear in the request list (with model, tokens and context length). If it does not, the agent did not inherit your environment — go back to step 1 and use the ~/.claude/settings.json form.

Troubleshooting¶

Related¶

• ACP Overview — the same setup also covers Zed and JetBrains
• Environment Variables
• Endpoints & API Paths