Integrate Windsurf with VS Code and IntelliJ Easily

The windsurf vscode intellij integration confuses most developers on first approach because the product relationship is not what it appears. Windsurf is not a plugin you install inside VS Code, and its IntelliJ offering is a completely separate product from the main IDE.

Getting that mental model wrong at the start produces a broken install, missing AI features, and hours spent troubleshooting a setup that was never going to work. This guide corrects the model before you touch an installer.

Key Takeaways

• Windsurf is a VS Code fork: It is not a plugin inside VS Code, it is a standalone IDE that ships with all VS Code features plus Cascade on top.
• Migration from VS Code takes one click: Windsurf imports your settings, extensions, themes, and keybindings automatically on first launch, so switching does not mean starting over.
• The JetBrains integration is a separate product: Windsurf's IntelliJ support is a dedicated plugin that runs inside your existing JetBrains IDE, not part of the Windsurf IDE itself.
• VS Code and Windsurf can run side by side: Both applications can be open simultaneously on the same machine and the same project, which is useful during a trial period before committing fully.
• The plugin gives you AI, not the full IDE: The Windsurf JetBrains plugin delivers Cascade and AI chat inside IntelliJ, but extensions, debugging, and project management stay in IntelliJ.
• Setup complexity differs by path: The VS Code migration is largely automated; the JetBrains plugin requires a manual install and Codeium account authentication.

Claude for Small Business

Claude for SMBs Founders

Most people open Claude and start typing. That works for one-off questions. It doesn't work for running a business. Do this once — this weekend.

Free Claude course for SMBs

How Does Windsurf Relate to VS Code. Is It a Plugin or a Separate IDE?

Windsurf is a full standalone IDE built on a VS Code fork. It is not a plugin or extension that runs inside VS Code. Installing Windsurf creates a second, independent application on your machine. The two share an architecture but do not share a process, settings file, or extension store.

Understanding this distinction before you start prevents the most common installation mistake.

• VS Code fork means shared architecture, not shared application: Windsurf uses the same extension API and interface conventions as VS Code but runs as a completely separate program with its own process and data directory.
• Installing Windsurf does not modify VS Code: Nothing changes in your existing VS Code installation. Windsurf appears as a new application alongside it, not embedded within it.
• Three distinct products exist in this space: The Windsurf IDE (the full fork), the Windsurf JetBrains plugin (runs inside IntelliJ), and the Codeium VS Code extension (a true plugin that stays inside VS Code without replacing it).
• Cascade lives in the IDE, not in the fork layer: The agentic AI system that defines Windsurf's capabilities is built on top of the VS Code fork, it is not something you can extract and add to a standard VS Code install.

If you are new to Windsurf entirely, reading up on what Windsurf actually is before starting the setup will prevent the most common installation mistakes.

How Do You Migrate From VS Code to Windsurf?

Download the Windsurf installer from the Codeium website, run it on macOS, Windows, or Linux, and follow the first-launch prompt to import your VS Code settings automatically. The process takes under five minutes and does not touch your existing VS Code installation.

The migration path is designed to reduce friction for VS Code users.

• The installer creates a new application, not a VS Code modification: Windsurf appears as a separate entry in your applications folder and dock. VS Code remains intact and unmodified after the install completes.
• The one-click import covers settings, extensions, themes, keybindings, and snippets: On first launch, Windsurf detects your VS Code installation and offers to copy the entire environment in a single step.
• Some extensions may not activate correctly after import: Extensions published exclusively to the VS Code Marketplace and not to the Open VSX Registry will appear installed but may fail to activate, check these individually after migration.
• AI features require a Codeium account: The IDE shell migrates automatically, but Cascade activation requires signing in to a Codeium account during first launch, the free tier is available with no credit card required.
• Verify the environment before treating migration as complete: Confirm that language servers, linters, formatters, and terminal behavior match your VS Code setup before switching over fully.

Run one real task from your current project in Windsurf before decommissioning your VS Code setup for that project.

How Do You Run Windsurf's AI Features Inside VS Code Without Switching?

Windsurf does not offer a VS Code plugin. The Codeium VS Code extension exists and provides AI completions and chat, but it does not include Cascade or the full agentic workflow that defines the Windsurf product. Staying in VS Code means accepting a meaningful capability difference.

This is the honest answer for developers who want to avoid switching editors.

• The Codeium VS Code extension provides autocomplete and basic chat: These are useful features, but they are categorically different from Cascade's multi-file agentic sessions, terminal access, and autonomous task execution.
• Staying in VS Code preserves your current setup at the cost of Cascade: Developers with VS Code-specific extensions that have no Open VSX equivalent may find this trade-off worthwhile for continuity.
• IDE standardization policies may make switching impossible: Teams where editor choice is governed by a policy or security requirement may be limited to the Codeium extension regardless of capability preference.
• Trialing Windsurf alongside VS Code is the recommended path before deciding: Running both editors simultaneously lets you evaluate Cascade on real tasks without committing to or disrupting your existing setup.

The trial approach is covered in the side-by-side section below, and it requires no configuration changes to your current VS Code environment.

How Do You Use Windsurf With IntelliJ or JetBrains IDEs?

The Windsurf JetBrains plugin installs from the JetBrains Marketplace inside your existing IDE. It adds Cascade-powered AI chat and inline completions to IntelliJ IDEA, PyCharm, WebStorm, GoLand, and other JetBrains products. It does not replace the host IDE or require the Windsurf IDE to be installed.

JetBrains users install a plugin, not a second IDE.

• Find the plugin by searching "Windsurf" or "Codeium" in the JetBrains Marketplace: Open your IDE, go to Settings > Plugins > Marketplace, search for the plugin, and click Install, then restart the IDE to activate it.
• Authentication happens via browser OAuth during first activation: The plugin opens a Codeium login page in your browser, signing in links the plugin to your account and activates your credit pool for AI operations.
• The plugin delivers Cascade chat, inline completions, and multi-file context awareness: These features integrate into IntelliJ's existing tool window and editor pane system without disrupting the native IDE layout.
• All JetBrains-native functionality stays in IntelliJ: Debugging, profiling, run configurations, version control UI, and project management remain the host IDE's responsibility, the plugin adds AI on top without replacing any of it.
• Supported on recent IntelliJ platform versions: Older JetBrains IDE releases may not support the latest plugin version, check the plugin's compatibility range in the Marketplace listing before installing on legacy installations.

The plugin is the correct integration path for any developer whose primary workflow depends on JetBrains tooling and has no intention of switching to a VS Code-based environment.

What Breaks When You Move From VS Code to Windsurf?

The most common migration friction comes from extensions that exist only in the VS Code Marketplace, settings sync tied to a Microsoft account, and keybindings that reference VS Code-internal commands. None of these are blockers, but all of them require attention before the migration is complete.

Knowing what to check prevents post-migration surprises.

• Microsoft-owned extensions may not be available in Windsurf: Tools like certain Azure extensions and some GitHub-specific integrations are published exclusively to the VS Code Marketplace and will not install through Windsurf's Open VSX-based extension system.
• VS Code Settings Sync does not extend to Windsurf: If you use Settings Sync tied to a Microsoft or GitHub account, that sync stops at VS Code. Windsurf maintains its own separate settings store that you manage independently.
• Custom keybindings referencing VS Code-internal commands need remapping: Most keybindings import cleanly, but any binding that calls a command specific to VS Code's internal API will need to be updated manually inside Windsurf's keyboard shortcuts editor.
• Some language servers initialize differently in Windsurf: Less common languages in particular may require a brief reconfiguration period, expect to spend time on language server settings if your stack goes beyond the major web and systems languages.

Before migrating, the full Windsurf feature list clarifies which capabilities are built into Windsurf natively and which depend on extension compatibility.

Which Setup Is Better. Windsurf IDE or Windsurf Plugin?

The Windsurf IDE delivers the full Cascade agentic workflow with terminal access, multi-file editing, and MCP server support. The JetBrains plugin adds a capable AI layer inside IntelliJ but operates within the constraints of the plugin architecture. The right choice depends on your primary language ecosystem and how deeply you want to use Cascade.

The decision comes down to ecosystem fit and workflow depth.

• Choose the JetBrains plugin if your stack depends on JetBrains tooling: Java, Kotlin, Scala, and C# development benefits from IntelliJ's native debugger and build system support in ways that the VS Code ecosystem does not fully replicate.
• Choose the full IDE if you work primarily in JavaScript, TypeScript, Python, or Go: The VS Code ecosystem is strongest for these languages, and the full Windsurf IDE gives you Cascade's complete agentic capability on top of that foundation.
• Both the IDE and the plugin draw from the same Codeium account and credit pool: Switching between them does not reset usage or require a separate subscription, your plan tier and Flow Action balance apply to both.
• The plugin has a capability ceiling the IDE does not: Complex agentic workflows, MCP server integrations, and terminal-driven Cascade tasks are available in the full IDE but are limited or unavailable through the plugin architecture.

Reviewing Windsurf plans and pricing before choosing a path helps teams understand whether the full IDE's capabilities justify the switch for their team size and usage pattern.

How Do You Run Both VS Code and Windsurf Side by Side?

Windsurf and VS Code are independent applications that can run simultaneously on macOS, Windows, and Linux. They do not share processes, settings, or extension state. Both can have the same project folder open at the same time without conflicts.

The side-by-side setup is the recommended evaluation approach.

• File system changes in one editor appear immediately in the other: There is no lock mechanism preventing concurrent access to the same folder, edits made in VS Code are visible in Windsurf's file tree in real time and vice versa.
• Use VS Code as primary and Windsurf for specific tasks during the trial: Keep VS Code as your main editor for the first one to two weeks, and open Windsurf specifically for refactors, feature scaffolding, and test generation to compare the experience directly.
• Settings in each editor stay separate and do not interfere: Windsurf stores its settings at a different path from VS Code's user settings, changes in one never bleed into the other, so the trial has no risk of destabilizing your current VS Code environment.
• The side-by-side setup also works as a permanent long-term arrangement: Some developers keep both editors open indefinitely, using VS Code for quick edits and Windsurf for Cascade-heavy sessions where the full agentic workflow is worth the context switch.

The guide to projects you can ship with Windsurf is a good reference for identifying which tasks in your backlog are best suited for a Cascade session in the full IDE.

Conclusion

Windsurf's relationship to VS Code and IntelliJ is not a plugin story. It is a choice between a full IDE migration, a parallel setup, or a plugin layer added to your existing JetBrains environment. Each path has a different capability ceiling, and getting that mental model right at the start determines whether the setup delivers on what Windsurf actually promises.

Download the Windsurf IDE if you are currently on VS Code, or install the JetBrains plugin if IntelliJ is your primary environment. Give Cascade one real task from your current project to verify the setup works before reconfiguring anything else.

Claude for Small Business

Claude for SMBs Founders

Most people open Claude and start typing. That works for one-off questions. It doesn't work for running a business. Do this once — this weekend.

Free Claude course for SMBs

Want Expert Help Integrating AI Tools Into Your Development Workflow?

At LowCode Agency, we are a strategic product team, not a dev shop. We design, build, and scale AI-powered products with a focus on architecture, performance, and shipping on time.

• AI-first product design: We build systems with AI at the core architecture layer, not added as an afterthought after launch.
• Full-stack delivery: Our team handles design, engineering, QA, and deployment end to end without gaps between handoffs.
• Agentic tooling expertise: We use Windsurf, Cursor, and agentic coding pipelines on real client projects, not just prototypes.
• Model selection guidance: We match the right AI model to each task, balancing cost, latency, and accuracy for the specific build.
• Code quality and review: Every deliverable goes through structured review before shipping, catching issues before they reach production.
• Scalable architecture: We build on foundations designed for growth so teams avoid rebuilding from scratch at the next inflection point.
• Flexible engagements: We engage on defined scopes, giving teams senior engineering capacity without the overhead of full-time hires.

We have built 350+ products for clients including Coca-Cola, American Express, Sotheby's, Medtronic, Zapier, and Dataiku.

Start a conversation with LowCode Agency to scope your project.