How to Use Windsurf

Windsurf is a code editor built around an AI agent called Cascade that doesn't just answer coding questions, it reads your whole codebase, plans multi-step changes, and executes them: creating files, editing existing code, and running terminal commands on its own. It's a fork of VS Code, so if you already know that editor, the layout and shortcuts will feel immediately familiar.

Step 1: Install and import your setup

Download Windsurf for Mac, Windows, or Linux. During setup, it offers to import your settings, extensions, and keybindings directly from VS Code or Cursor, so you land in a configured environment instead of a blank one.

Step 2: Open the Cascade sidebar

Press Cmd+L on Mac or Ctrl+L on Windows to open Cascade. This is where you describe what you want built or changed, in plain English, rather than writing the code yourself line by line.

Step 3: Describe the task and review the plan

Type what you want (a new feature, a bug fix, a refactor). Cascade analyzes your codebase first, then proposes a plan before touching anything. Read the plan; it's your chance to catch a misunderstanding before Cascade starts editing files.

Step 4: Let Cascade execute, then review the diff

Once you approve, Cascade makes the actual changes, which can span multiple files, and can run terminal commands (installing a package, running tests) as part of completing the task. Review the diff it produces the same way you'd review a colleague's pull request, since an agent that can execute multi-step plans can also compound a wrong assumption across several files.

Where the free plan runs out

The free plan includes a fixed monthly allotment of Supercompletes (inline autocomplete) and Cascade Flow responses (agent actions). Light, occasional use fits comfortably; using Cascade as your primary way of writing code will burn through the free allotment well before the month is over.

Frequently asked questions

Can I use Windsurf with my existing VS Code extensions?

Yes, since Windsurf is a VS Code fork, most extensions from the VS Code marketplace work, and your existing ones can be imported during setup.

Does Cascade have access to my entire codebase, or just the open file?

Cascade indexes your whole codebase, not just the open file, which is how it can plan changes that span multiple files rather than only editing what's currently on screen.

Can I undo a change Cascade makes?

Yes, changes appear as a normal diff you can reject before applying, and once applied they behave like any other file edit, so your regular version control (Git) is still your safety net.