Windsurf

What it is

Windsurf is Codeium's flagship AI-native IDE — a VS Code fork released in 2024 that bet hard on Cascade, an autonomous coding mode that watches your work, runs commands, edits across files, and proactively suggests next steps. Where Cursor positioned itself around the Cmd-K composer and tab-completions, Windsurf went further into "agent driving the IDE for you" territory.

In mid-2025 OpenAI announced its acquisition of Windsurf (paired with the Codeium core enterprise business shifting separately), so the future trajectory is tied to OpenAI's product strategy. As of mid-2026 Windsurf still ships independently with strong pricing.

It is the tool to reach for when:

• You want a fully agent-driven IDE rather than a chat panel + completions.
• The free tier matters (Windsurf's Cascade free quota is meaningfully usable).
• You want IDE + autonomous agent in one binary, not VS Code + plugin.

Why it stands out

How to install

# Download for macOS / Linux / Windows
# https://windsurf.com/download

# Or via Homebrew on macOS
brew install --cask windsurf

After install, sign in with email or Google. Free tier kicks in immediately. Pro is around $15/mo (subject to change post-OpenAI). Drop a .windsurfrules in your repo root to give Cascade project-specific instructions.

What to install in Windsurf

Windsurf reads .windsurfrules (project) and Memories (workspace-persistent context). Three TokRepo packs to start:

• .windsurfrules Templates — project rules tuned for Cascade's planning style
• Cascade Memories Pack — bootstrap memories for popular framework conventions
• MCP Server Stack — Postgres / GitHub / Filesystem servers shared with Claude Code

Run tokrepo install and your .windsurfrules plus Memories light up with the same baseline Codeium showed in launch demos.

Common pitfalls

• Cascade going off-script on long tasks — without .windsurfrules constraints, Cascade will refactor more than you asked for. Always pin scope in rules.
• Free tier rate limits during agent loops — generous but not infinite. Mark long refactors for Pro plan or schedule chunks.
• Memories accumulating noise — Memories grow across sessions. Periodically prune via the Memories panel or Cascade starts referencing stale context.
• MCP server config location — Windsurf uses ~/.codeium/windsurf/mcp_config.json, not .claude/. Don't symlink; use tokrepo migrate.
• Post-acquisition uncertainty — pricing, free tier, and feature roadmap may shift as OpenAI integrates Windsurf with Codex CLI / ChatGPT. Avoid building team workflows that assume the current Pro tier features will persist unchanged.

Common misconceptions

People often confuse Windsurf with Cursor — they're both VS Code forks built around AI agents — but the design philosophies differ. Cursor leaned into explicit invocation (you press Cmd-K, you ask, you accept). Windsurf leaned into autonomy (Cascade keeps thinking and proposing). After 2 years of competition both have absorbed each other's ideas (Cursor added agent mode, Windsurf added explicit composer), so the gap is narrowing. The biggest differentiator now is the OpenAI acquisition: post-acquisition Windsurf will likely tighten its integration with OpenAI's models and the Codex CLI conventions, while Cursor remains independent and multi-vendor.