<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Wave-13 on RockB</title><link>https://baeseokjae.github.io/tags/wave-13/</link><description>Recent content in Wave-13 on RockB</description><image><title>RockB</title><url>https://baeseokjae.github.io/images/og-default.png</url><link>https://baeseokjae.github.io/images/og-default.png</link></image><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 09 May 2026 03:05:17 +0000</lastBuildDate><atom:link href="https://baeseokjae.github.io/tags/wave-13/index.xml" rel="self" type="application/rss+xml"/><item><title>Windsurf Wave 13 Guide: Arena Mode, Plan Mode and SWE-1.5 (2026)</title><link>https://baeseokjae.github.io/posts/windsurf-wave-13-arena-mode-guide-2026/</link><pubDate>Sat, 09 May 2026 03:05:17 +0000</pubDate><guid>https://baeseokjae.github.io/posts/windsurf-wave-13-arena-mode-guide-2026/</guid><description>Complete guide to Windsurf Wave 13 and Wave 14 features: SWE-1.5 free model, parallel Git worktree agents, Arena Mode, and Plan Mode.</description><content:encoded><![CDATA[<p>Windsurf Wave 13 (the &ldquo;Shipmas Edition,&rdquo; released December 24, 2025) introduced three production-ready capabilities that reshaped the AI IDE landscape: the SWE-1.5 model free for all users, true parallel agents running in isolated Git worktrees, and a dedicated Cascade terminal with interactive zsh support. Wave 14 followed with Arena Mode for blind model comparison and Plan Mode for structured task planning. Together, these two releases represent the largest capability jump Windsurf has shipped to date.</p>
<h2 id="what-is-windsurf-wave-13-shipmas-edition-overview">What Is Windsurf Wave 13? (Shipmas Edition Overview)</h2>
<p>Windsurf Wave 13 is a major update to the Windsurf AI IDE released on December 24, 2025, under the name &ldquo;Shipmas Edition.&rdquo; It delivered four headline features simultaneously: SWE-1.5 as the free default model, true parallel Cascade agents backed by Git worktrees (up to 5 simultaneous sessions), a dedicated Cascade terminal with interactive zsh support on macOS, and a real-time context window indicator with prompt cache timer. Before Wave 13, running multiple Cascade agents meant working in the same directory, creating file conflicts and unpredictable merge states. Wave 13 eliminated that problem entirely by giving each agent its own isolated working directory backed by a separate Git branch. The release positioned Windsurf as the strongest alternative to Cursor in early 2026, particularly for developers who need to parallelize long-running agentic tasks. Wave 14, released in April/May 2026, built on this foundation by adding Arena Mode (blind model head-to-head comparison) and Plan Mode (structured planning before code execution).</p>
<h2 id="swe-15-windsurfs-free-frontier-coding-model">SWE-1.5: Windsurf&rsquo;s Free Frontier Coding Model</h2>
<p>SWE-1.5 is Windsurf&rsquo;s proprietary coding model, achieving 40.08% accuracy on SWE-Bench-Pro — a real-world benchmark of GitHub issue resolution — matching Claude Sonnet 3.5-level performance on actual software engineering tasks. It runs at approximately 950 tokens per second, which is 13–14x faster than Claude Sonnet 4.5 at comparable capability levels. For the three months following Wave 13&rsquo;s release (through March 2026), SWE-1.5 was free for all Windsurf users and set as the default Cascade model. This eliminated the credit-drain concern that had previously made power users hesitant to use frontier models on exploratory tasks. SWE-1.5 is optimized specifically for code generation, bug fixing, and agentic tool-use workflows — not general reasoning. For tasks requiring broad contextual understanding or non-coding domains, Claude Opus 4.6 or GPT-5.4 remain stronger choices. On the Fast Arena leaderboard (May 2026), SWE-1.5 ranks first among speed-optimized models, above Haiku 4.5 and Gemini 3 Flash Low.</p>
<h3 id="why-swe-15-speed-matters-for-parallel-agents">Why SWE-1.5 Speed Matters for Parallel Agents</h3>
<p>When running 5 parallel Cascade agents, model latency compounds. At 950 tokens/second, SWE-1.5 completes typical coding subtasks in seconds rather than tens of seconds — making the parallel agent workflow feel genuinely snappy rather than a monitoring exercise.</p>
<h3 id="how-to-select-swe-15-in-cascade">How to Select SWE-1.5 in Cascade</h3>
<p>Open a Cascade chat, click the model selector in the top-right corner, and choose <code>SWE-1.5</code>. If you&rsquo;re on a plan with quota limits, monitor usage via the new context window indicator. SWE-1.5 consumes fewer credits than frontier models, so it&rsquo;s a cost-effective default for most coding tasks.</p>
<h2 id="true-parallel-agents-with-git-worktrees">True Parallel Agents with Git Worktrees</h2>
<p>Wave 13&rsquo;s parallel agent feature is the most structurally significant capability Windsurf has shipped. It allows developers to run up to 5 Cascade agents simultaneously, each operating in its own isolated Git worktree — a separate directory that shares the same repository history but maintains an independent working tree and branch. Before this feature existed, running two agents on the same codebase risked file conflicts when both attempted to modify overlapping files. With Git worktrees, each agent works on its own branch (e.g., <code>feature/auth-refactor</code>, <code>feature/api-v2-migration</code>) and conflicts only surface at intentional merge time. This matches how senior engineering teams actually structure parallel work: independent branches, deliberate integration. The multi-pane Cascade interface lets you monitor all 5 agents in a single view, with each panel showing the agent&rsquo;s current task, tool calls in progress, and branch status. This is the first commercial IDE feature that genuinely enables autonomous multi-task parallel coding at a production-useful scale.</p>
<h3 id="setting-up-git-worktrees-in-windsurf">Setting Up Git Worktrees in Windsurf</h3>
<p>Git worktrees are created automatically when you launch a parallel Cascade agent. You don&rsquo;t need to run <code>git worktree add</code> manually. In the Cascade panel, click the <strong>+ New Agent</strong> button (or the parallel agent icon in the top-right), assign a task description, and Windsurf creates the worktree and branch in the background. Each agent panel shows the active branch name so you always know where changes are landing.</p>
<h3 id="when-to-use-parallel-agents-vs-a-single-agent">When to Use Parallel Agents vs a Single Agent</h3>
<p>Use parallel agents when tasks are genuinely independent: separate features, independent bug fixes across different modules, or test suite generation for isolated components. Avoid parallel agents for tasks with shared state — two agents modifying the same config file or database migration sequence will create conflicts at merge time regardless of worktree isolation.</p>
<h2 id="wave-14-continuation-arena-mode-and-plan-mode">Wave 14 Continuation: Arena Mode and Plan Mode</h2>
<p>Wave 14, released in April/May 2026, extended the Wave 13 foundation with two new Cascade modes: Arena Mode and Plan Mode. Arena Mode enables blind head-to-head comparison of AI models using an Elo rating system — developers submit a prompt and two models respond in parallel, with identities hidden until the user votes on the better response. Plan Mode introduces a structured planning phase before code execution, letting developers review and edit a task plan before Cascade begins making file changes. Together, these additions address two persistent frustrations in AI-assisted coding: uncertainty about which model to use for a given task, and the loss of control when an agent immediately starts modifying files without showing its reasoning first. Wave 14 features were initially free for one week after launch and then became part of the standard Pro and advanced tier quotas.</p>
<h2 id="arena-mode--blind-head-to-head-model-comparison">Arena Mode — Blind Head-to-Head Model Comparison</h2>
<p>Arena Mode is a Windsurf Cascade feature that runs two AI models simultaneously on the same prompt, hides their identities during response generation, and asks the developer to vote on which response is better. Votes feed into a personal Elo leaderboard and a global Windsurf Elo ranking — structurally similar to the chess rating system used by FIDE. According to the May 2026 Windsurf Arena leaderboard, the Frontier Arena top models are Opus 4.6, Opus 4.5, and Sonnet 4.5; the Fast Arena leaders are SWE-1.5, Haiku 4.5, and Gemini 3 Flash Low. Arena Mode supports up to 5 models for expanded comparison sets. Credits are consumed based on the models selected, not the number of rounds. Arena Mode is particularly useful for establishing personal calibration: most developers find their intuitions about &ldquo;which model is best&rdquo; are significantly revised after 20–30 real Arena votes on their own actual tasks.</p>
<h3 id="arena-battle-groups-explained">Arena Battle Groups Explained</h3>
<p>Windsurf organizes Arena Mode into three battle groups:</p>
<ul>
<li><strong>Frontier Arena</strong>: Highest-capability models (Opus 4.6, GPT-5.4, Gemini 2 Ultra). Best for complex reasoning, architecture decisions, and multi-file refactors.</li>
<li><strong>Fast Arena</strong>: Speed-optimized models (SWE-1.5, Haiku 4.5, Gemini 3 Flash Low). Best for autocomplete, small bug fixes, and test generation where latency matters.</li>
<li><strong>Hybrid Arena</strong>: Mixed-tier comparisons for developers calibrating cost vs. capability tradeoffs.</li>
</ul>
<h3 id="how-to-enable-arena-mode">How to Enable Arena Mode</h3>
<p>In Cascade, click the <strong>Arena</strong> icon in the model selector dropdown. Select your battle group, choose up to 5 models to include in the rotation, and submit a prompt. Two models respond in parallel. Review both responses — model identities are hidden behind Model A/B labels — then click <strong>Vote</strong> on the better response. After voting, identities are revealed and your vote updates both your personal leaderboard and the global ranking.</p>
<h2 id="plan-mode--think-before-you-code">Plan Mode — Think Before You Code</h2>
<p>Plan Mode is a Windsurf Cascade feature that inserts a structured planning phase between task input and code execution. When Plan Mode is active, Cascade generates a step-by-step implementation plan — including which files it will modify, what logic changes it will make, and the expected sequence of actions — before writing a single line of code. The developer reviews this plan, can edit it directly, and only then triggers execution. This addresses the most common complaint about agentic coding: agents immediately start making changes without showing their work, making it difficult to course-correct before damage is done. Plan Mode adds a friction-by-design checkpoint that mirrors how senior engineers actually work — think first, code second. For extra-thorough planning on complex tasks, Windsurf added a <strong>megaplan</strong> shortcut (accessible via <code>/megaplan</code> in the Cascade input) that generates more detailed sub-task breakdowns before execution.</p>
<h3 id="when-plan-mode-saves-you-time">When Plan Mode Saves You Time</h3>
<p>Plan Mode is most valuable for: large refactors across multiple files, database schema migrations, API breaking changes, or any task where a wrong first step cascades into significant rework. For small bug fixes or autocomplete-style tasks, Plan Mode adds unnecessary latency — disable it and use standard Cascade for quick edits.</p>
<h3 id="enabling-and-disabling-plan-mode">Enabling and Disabling Plan Mode</h3>
<p>Toggle Plan Mode in the Cascade toolbar using the <strong>Plan</strong> button (or via <code>Cmd+Shift+P</code> on macOS). When enabled, Cascade displays a plan card before execution. You can approve the plan as-is, edit individual steps, or reject it and re-describe the task to generate a different plan. The plan card is not read-only: click any step to modify the approach before committing to execution.</p>
<h2 id="windsurf-vs-cursor-in-2026-how-wave-1314-changes-the-race">Windsurf vs Cursor in 2026: How Wave 13/14 Changes the Race</h2>
<p>The competitive dynamic between Windsurf and Cursor shifted significantly with Wave 13 and 14. Cursor&rsquo;s core strength remains its VS Code-native integration and the Tab autocomplete model, which has no direct Windsurf equivalent. Windsurf&rsquo;s Wave 13/14 advantages are: broader IDE support (40+ IDE plugins vs. Cursor&rsquo;s VS Code-only focus), parallel agents with true Git worktree isolation (Cursor&rsquo;s parallel features share the same working directory), Arena Mode for data-driven model selection (no Cursor equivalent), and Plan Mode for pre-execution review (Cursor&rsquo;s equivalent is less structured). On pricing, Windsurf shifted from credit-based to flat quota tiers in March 2026 ($20/month basic, $40/month Pro with Claude Opus 4.6 and GPT-5.4 access, $200/month enterprise). Cursor&rsquo;s pricing remained credit-anchored through early 2026, making cost-per-task comparisons favor Windsurf for heavy parallel agent workflows. The strategic divide is depth vs. breadth: Cursor dominates VS Code, Windsurf runs everywhere. For solo developers on VS Code, the choice remains close. For teams using JetBrains, Neovim, or mixed editor environments, Windsurf&rsquo;s breadth makes it the practical default.</p>
<h2 id="how-to-get-started-with-all-wave-13-and-wave-14-features">How to Get Started with All Wave 13 and Wave 14 Features</h2>
<p>Getting access to all Wave 13 and Wave 14 features requires Windsurf version 1.13 or later. Update via the in-app notification or by downloading the latest build from windsurf.com. After updating:</p>
<ol>
<li><strong>Enable SWE-1.5</strong>: Open Cascade → Model selector → Choose <code>SWE-1.5</code>. No additional configuration needed.</li>
<li><strong>Launch parallel agents</strong>: In the Cascade panel header, click <strong>+ Agent</strong>. Assign a task. Windsurf creates a Git worktree automatically. Repeat for additional agents (up to 5).</li>
<li><strong>Monitor via multi-pane view</strong>: Use the split-pane button in the Cascade toolbar to display all active agents side by side.</li>
<li><strong>Enable dedicated terminal</strong>: In Preferences → Cascade → Terminal, toggle <strong>Use Dedicated Cascade Terminal (Beta)</strong>. This uses an interactive zsh session and sources your <code>.zshrc</code>, fixing environment variable issues in shell-heavy workflows.</li>
<li><strong>Try Arena Mode</strong>: Click the model selector → Arena → Select battle group → Submit a prompt and vote.</li>
<li><strong>Enable Plan Mode</strong>: Click the <strong>Plan</strong> toggle in the Cascade toolbar before submitting complex tasks.</li>
<li><strong>Check context window</strong>: The indicator appears in the bottom of each Cascade panel. When usage exceeds 80%, consider starting a new conversation to avoid context degradation.</li>
</ol>
<h2 id="should-you-switch-to-windsurf-in-2026">Should You Switch to Windsurf in 2026?</h2>
<p>Windsurf Wave 13 and Wave 14 make it the strongest AI IDE for teams running parallel agentic workflows, developers who work across multiple editor environments, and anyone who wants data-driven model selection via Arena Mode rather than relying on benchmark marketing. The SWE-1.5 model free period democratized frontier AI coding assistance in a way that meaningfully differentiated Windsurf from Cursor during Q1 2026. Plan Mode addresses a real workflow problem — agents that act before thinking — without adding prohibitive friction. The weakest argument for Windsurf is for developers who are deeply invested in VS Code&rsquo;s extension ecosystem and rely heavily on Tab autocomplete, where Cursor&rsquo;s integration remains tighter. The strongest argument for Windsurf is running 5 parallel agents on a large codebase refactor without file conflicts — a capability that has no production-equivalent in any other AI IDE as of May 2026. For most professional developers doing serious multi-task AI-assisted work, Wave 13/14 represents a genuinely persuasive upgrade path.</p>
<h2 id="faq">FAQ</h2>
<p><strong>What is Windsurf Wave 13?</strong>
Windsurf Wave 13 (Shipmas Edition) is a major AI IDE update released December 24, 2025, introducing SWE-1.5 as a free default model, true parallel agents with Git worktree isolation (up to 5 simultaneously), a dedicated zsh Cascade terminal, and a real-time context window indicator.</p>
<p><strong>What is Arena Mode in Windsurf?</strong>
Arena Mode is a Windsurf Cascade feature that runs two AI models simultaneously on the same prompt with hidden identities. After both respond, you vote on the better output, feeding a personal and global Elo leaderboard — enabling data-driven model selection over relying on marketing benchmarks.</p>
<p><strong>What is Plan Mode in Windsurf?</strong>
Plan Mode is a Windsurf Cascade feature that generates a step-by-step implementation plan before executing any code changes. Developers review, edit, or reject the plan before Cascade begins modifying files — preventing premature or misdirected changes on complex tasks.</p>
<p><strong>How fast is SWE-1.5?</strong>
SWE-1.5 runs at approximately 950 tokens per second, making it 13–14x faster than Claude Sonnet 4.5. It achieves 40.08% accuracy on SWE-Bench-Pro, positioning it at Claude Sonnet 3.5-level capability for real-world software engineering tasks.</p>
<p><strong>How does Windsurf compare to Cursor in 2026?</strong>
Windsurf leads in multi-agent parallel workflows (Git worktree isolation, up to 5 agents), IDE breadth (40+ plugins vs. VS Code only), Arena Mode for model benchmarking, and flat quota pricing. Cursor leads in VS Code-native depth and Tab autocomplete quality. For solo VS Code developers, the choice is close. For teams or mixed-editor environments, Windsurf&rsquo;s breadth wins.</p>
]]></content:encoded></item></channel></rss>