86 sources from practitioners, by month and sentiment.
The read is positive. Codebase context draws the most praise. Review burden draws the most concern, followed by agent reliability and usage limits after pricing changes. Of 30 sources comparing editors, 22 prefer another tool.
Positive, mixed and negative sources
282415
The score counts them as 26 positive, 22 mixed and 15 negative votes, one per author. See How the numbers work.
Their team moved to Windsurf from Copilot, and the author finds it most useful for answering questions about a monorepo of a bit over 1M LoC; the supertab feature was also very useful. Almost never asks it to do complex tasks, since describing them takes almost as long as implementing.
Published Dec 14, 2025self-described: Team working in a monorepo of over 1M lines of code, moved from Copilot to Windsurf
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Positive
Tripti Sheth, Senior Director of Software Engineering at Salesforce
Sheth's backend team built a migration tracking UI with Cursor, Windsurf and Claude in three days, work that typically takes about six weeks; Windsurf's rules and memories let it refactor unwieldy code into modular structures.
"Windsurf: We used rules and memories, allowing it to learn from previous context and refactor code into more manageable structures."
Excerpt, Tripti Sheth
Published Nov 17, 2025Monitoring Cloud Notification Management team; backend engineers building a migration tracking tool
Practitioner account, name and role on their organization's own page; direct use; counts toward Delivered outcomes
Testing all three on GPT-5 over a weekend, the author found Windsurf explained an existing codebase best, kept context across the session and scaffolded a project unprompted, with slower inline suggestions.
Published Sep 3, 2025self-described: Solo weekend test on greenfield and brownfield projects
Building a Next.js todo app with Gemini 2.5 Pro in Cascade, Ken saw it update the correct files without being told and import Lucide-react without installing it. After a planned theme change, the theming "seems to have broken somewhere" until a few more iterations fixed it.
Published Jul 31, 2025self-described: Solo, a Next.js to-do app built with Cascade
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Operational control, Cost predictability and limits, Adoption and upkeep
Uses Cursor until hitting a wall, then switches to Windsurf, which the commenter says solves issues Cursor fails on after 40 minutes of retries, though its plans are limited.
Published May 12, 2025self-described: Solo; uses Cursor and Windsurf
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Vibe coding a web app, the commenter found Cascade good at locating where to change the codebase, but it could not solve performance or CSS animation problems without their direction.
Published May 8, 2025self-described: Solo, a web app built with Windsurf
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Moving between Windsurf and GitHub Copilot, the commenter credits Windsurf's whole-codebase indexing for completions across files and Cascade's terminal handling, while rating Cursor's checkpoint undo higher.
Published May 7, 2025self-described: Evaluating Windsurf against GitHub Copilot
Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep
Comparing approaches, the commenter observes that Windsurf still loads more code into context than Cursor's search-tool approach, giving it an edge in some cases at a lower subscription price.
Published May 6, 2025self-described: Uses Cursor and Windsurf
Practitioner account, pseudonymous; opinion; not counted, repeats a stronger account
After a month with each, Bergholz chose Windsurf for better codebase understanding and a smoother UI, and uses memories and a .windsurfrules file to correct it on a niche Elixir stack.
Published Mar 10, 2025self-described: Solo side projects in Elixir, Phoenix, React and Inertia
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Cost predictability and limits
Recommends Cascade for agentic code writing and exploration, saying it saved them many hours understanding new codebases and tracing data flows; Claude 3.5 cost credits.
Published Feb 24, 2025self-described: Individual use on new codebases
Practitioner account, pseudonymous; direct use; counts toward Operational control
A senior engineer and 12-month user, the commenter says developers overlook Windsurf now that debate centers on Cursor, Claude Code and Codex, and praises Codemaps.
Published Nov 4, 2025self-described: Senior engineer mixing agentic and regular coding
Practitioner account, pseudonymous; direct use; not counted, takes no position
Using Windsurf at work alongside Claude Code, the commenter says its UX adds real value and Codemaps have been excellent for weeks, though code churn could make them harder to maintain.
Published Nov 4, 2025self-described: Uses Windsurf at work alongside Claude Code
Practitioner account, pseudonymous; direct use; not counted, takes no position
Positive
Kristin Foss, VP of Software Engineering for Customer Centric Engineering at Salesforce
Foss's escalation engineers use Cursor, Windsurf and Claude CLI to build working reproductions of customer problems from internal source code, finding issues in large codebases in minutes where setup once took hours or days.
"To streamline this process, our CCE engineers now leverage Cursor, Windsurf, and Claude CLI."
Excerpt, Kristin Foss
Published Sep 29, 2025180-person engineering team resolving customer escalations across Salesforce products
Practitioner account, name and role on their organization's own page; ran the rollout; counts toward Delivered outcomes
After switching between both, the commenter prefers Cursor's completions, credits Windsurf with better project awareness across files that is hard to trigger, and notes its lower price.
Published May 12, 2025self-described: Solo; switches between Cursor and Windsurf
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Positive
Matt Wolfe, founder of FutureTools and technology video creator
Trialling both editors on the same PHP codebases, the commenter got poorer results from Windsurf on existing code, saw it read files 50 lines at a time, and went back to PhpStorm.
Published May 12, 2025self-described: Trialled Cursor and Windsurf on the same PHP codebases
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Once ahead of Cursor on agentic coding in their view, Windsurf now frustrates them by gathering context 100 to 200 lines at a time. The commenter blames that for bugs and poor results.
Published May 12, 2025self-described: Solo, agentic coding
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Danilchenko measured Devin Local at roughly 18,000 tokens against about 24,000 for Cascade on a 14-file refactor and saw subagents split work "maybe 40% of the time on multi-step tasks". Calls Devin Local measurably better than Cascade, but says the acquisition story creates real trust risk.
Published Jun 6, 2026self-described: Hands-on review after the rename; personal blog
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Reliability, Operational control, Cost predictability and limits, Adoption and upkeep
Over three days Windsurf wrote multi-file game logic, refactored on request and fixed bugs that would take them half an hour; the commenter made 95% of changes by instructing it.
Published Aug 13, 2025self-described: Solo, a game project
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Chooses Windsurf, running parallel Cascade sessions, one investigating a bug while another builds a feature, and drops in later to review and accept the changes.
Published May 12, 2025self-described: Solo, parallel Cascade sessions
Practitioner account, pseudonymous; direct use; not counted, takes no position
A customer since launch, the commenter handed Windsurf a broken Alembic migration after an hour of manual debugging; it isolated the file, fixed it, added tests and opened a PR. The commenter now prefers Claude Code.
Published May 7, 2025self-described: Solo; Windsurf customer since launch
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Mixed
CSMastermind, Hacker News commenter who evaluates dev tooling for their teams
Evaluating tools for their teams, the commenter found Windsurf the one tool that raised their productivity beyond chat, especially on command-line work, but held back a team rollout over pricing.
Published Apr 22, 2025self-described: Evaluates tools for their engineering teams
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Runs Windsurf next to JetBrains IDEs because the commenter finds Cascade ahead of the 30-plus LLM plugins available for JetBrains, though juggling two editors is a pain.
Published Feb 12, 2025self-described: Uses JetBrains IDEs with Windsurf alongside
Practitioner account, pseudonymous; direct use; not counted, takes no position
Tried Windsurf's free tier for about a week when the Claude weekly quota ran out, and found tab completion fast and Cascade reliably executing small-to-medium refactors. Calls it good but didn't keep it: its target user isn't a solo agentic-AI shipper, and the paid tier adds Opus access already had directly.
Published May 25, 2026self-described: Solo founder; one-week trial on the free tier
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Reliability, Operational control, Cost predictability and limits
Testing all three on GPT-5 over a weekend, the author found Windsurf explained an existing codebase best, kept context across the session and scaffolded a project unprompted, with slower inline suggestions.
Published Sep 3, 2025self-described: Solo weekend test on greenfield and brownfield projects
Roff reports a personal productivity gain above 70% and similar gains across his engineering team, to the point that QA struggles to keep up, while every Windsurf change still goes through a senior engineer's review.
"Team-wide benefits: The entire engineering team has experienced similar productivity gains."
Excerpt, David Roff
Published Jul 14, 2025Full stack platform team: web, React Native mobile, APIs and databases; WWT also sells Windsurf adoption services
Practitioner account, name and role on their organization's own page; direct use; counts toward Delivered outcomes, Operational control
Mixed
Mark Winteringham, tester, toolsmith, author and instructor
Working in small tasks after a messy start in Cursor, Winteringham had the Windsurf agent fix each failing unit test quickly, though it wrote more code than he expected.
"After that, I worked with the Windsurf agent to fix each of the failing tests. This process worked well, and it didn’t take too much time to get them all to pass."
Excerpt, Mark Winteringham
Published Jun 10, 2025self-described: Solo; migrating his public restful-booker-platform front end to Next.js
Practitioner account; direct use; counts toward Delivered outcomes, Reliability, Cost predictability and limits
Moving between Windsurf and GitHub Copilot, the commenter credits Windsurf's whole-codebase indexing for completions across files and Cascade's terminal handling, while rating Cursor's checkpoint undo higher.
Published May 7, 2025self-described: Evaluating Windsurf against GitHub Copilot
Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep
Positive
John Hoestje, Software Architect and Developer at Keyhole Software
Hoestje built two apps from Cascade prompts without editing a line by hand, and says he fell short when he moved too fast to review Cascade's suggested changes.
"I fell short when I was trying to go too fast. I didn’t take the time to properly review the suggested changes by Cascade."
Excerpt, John Hoestje
Published Mar 20, 2025Software consultancy; solo experiments building a React site and a Flutter Sudoku game
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Reliability, Operational control, Adoption and upkeep
Tried agent workflows in Copilot and Windsurf on Claude 3.5 and 4; they got stuck or built themselves into corners, and the output was fragile enough to refactor immediately.
Published Jul 12, 2025self-described: Solo; tried agent workflows in Copilot and Windsurf
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Runs a spec-driven workflow in Devin Desktop over ACP: Claude Code for exploration, Devin's SWE model for building and GLM 5.2 for verification, with little extra effort.
Published Jul 8, 2026self-described: Solo, spec-driven workflow
Practitioner account, pseudonymous; direct use; counts toward Operational control
After more than a year on Windsurf, their move to Devin Desktop kept their extensions and settings, and Copilot CLI running over ACP picked up and resumed their existing sessions.
Published Jun 4, 2026self-described: Solo; more than a year on Windsurf
Practitioner account, self-described; direct use; counts toward Adoption and upkeep
A long-time VS Code user, Agrawal liked queuing several instructions while Cascade works and its persistent memory, but finds the overlap with VS Code agent mode significant.
Published Mar 4, 2026self-described: Solo; VS Code user trying Windsurf
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Reliability, Operational control
A senior engineer and 12-month user, the commenter says developers overlook Windsurf now that debate centers on Cursor, Claude Code and Codex, and praises Codemaps.
Published Nov 4, 2025self-described: Senior engineer mixing agentic and regular coding
Practitioner account, pseudonymous; direct use; not counted, takes no position
Using Windsurf at work alongside Claude Code, the commenter says its UX adds real value and Codemaps have been excellent for weeks, though code churn could make them harder to maintain.
Published Nov 4, 2025self-described: Uses Windsurf at work alongside Claude Code
Practitioner account, pseudonymous; direct use; not counted, takes no position
Their company has run it on an enterprise plan for about nine months. The commenter rates it above Copilot but now finds Claude and Codex better, and Devin's web and desktop harnesses inconsistent.
Published Sep 10, 2026self-described: Their company, on an enterprise plan for about nine months
Practitioner account, pseudonymous; direct use; not counted, takes no position
Saw Windsurf as slightly better than Cursor, with a nicer chat panel and autocomplete and a US$5 cheaper plan, until losing Anthropic model access cost it users.
Published Jul 11, 2025self-described: Former Windsurf user
Practitioner account, pseudonymous; opinion; not counted, repeats a stronger account
Adopted Windsurf at launch for its UX, then saw more issues with each update, including the agent hanging on shell commands, and moved back to GitHub Copilot.
Published Jul 11, 2025self-described: Solo; adopted Windsurf at launch
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Positive
tartieret, Hacker News commenter (a CTO, by their own account elsewhere)
Their company standardized on Windsurf after reviewing Cursor, because Windsurf handled dev containers and WSL development, which most of its developers use, with fewer rough edges.
Published Apr 22, 2025self-described: Their company, whose developers mostly work in dev containers and WSL
Practitioner account, pseudonymous; ran the rollout; counts toward Adoption and upkeep
After a month with each, Bergholz chose Windsurf for better codebase understanding and a smoother UI, and uses memories and a .windsurfrules file to correct it on a niche Elixir stack.
Published Mar 10, 2025self-described: Solo side projects in Elixir, Phoenix, React and Inertia
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Cost predictability and limits
Each time the commenter tried the Windsurf Editor and its Vim and IntelliJ plugins it felt unpolished, and autocomplete felt much snappier in Cursor and in GitHub Copilot.
Published May 6, 2025self-described: Tried the editor and the Vim and IntelliJ plugins
Practitioner account, pseudonymous; direct use; not counted, takes no position
When the product was still Windsurf, terminal runs hung or froze nearly every time until the commenter wired up a workaround skill; the commenter says its multi-agent UI lead has since disappeared.
Published Sep 10, 2026self-described: Former Windsurf user
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Danilchenko measured Devin Local at roughly 18,000 tokens against about 24,000 for Cascade on a 14-file refactor and saw subagents split work "maybe 40% of the time on multi-step tasks". Calls Devin Local measurably better than Cascade, but says the acquisition story creates real trust risk.
Published Jun 6, 2026self-described: Hands-on review after the rename; personal blog
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Reliability, Operational control, Cost predictability and limits, Adoption and upkeep
In their first week completions helped with repetitive renames across files but often mangled unrelated code, the UI felt noisy, and chat sometimes scanned files endlessly with no output.
Published Apr 21, 2025self-described: First week of individual use
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
On a US$50 monthly budget the commenter pays US$20 for Windsurf for access to nearly all models, reserving Claude Opus and Sonnet for tricky work once requirements are clear.
Published Mar 24, 2026self-described: Solo on a US$50 monthly tooling budget
Practitioner account, pseudonymous; direct use; counts toward Cost predictability and limits
Keeps Windsurf as their primary IDE because bring-your-own-key covers prompts, agents and autocomplete, including in Vim, which the commenter says Cursor and Zed do not offer.
Published Mar 20, 2026self-described: Solo; Windsurf is their primary IDE
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Saw Windsurf as slightly better than Cursor, with a nicer chat panel and autocomplete and a US$5 cheaper plan, until losing Anthropic model access cost it users.
Published Jul 11, 2025self-described: Former Windsurf user
Practitioner account, pseudonymous; opinion; not counted, repeats a stronger account
After switching between both, the commenter prefers Cursor's completions, credits Windsurf with better project awareness across files that is hard to trigger, and notes its lower price.
Published May 12, 2025self-described: Solo; switches between Cursor and Windsurf
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Comparing approaches, the commenter observes that Windsurf still loads more code into context than Cursor's search-tool approach, giving it an edge in some cases at a lower subscription price.
Published May 6, 2025self-described: Uses Cursor and Windsurf
Practitioner account, pseudonymous; opinion; not counted, repeats a stronger account
After under a month on Devin the commenter hits the US$20 plan's limits faster than with Claude Code or Codex, and rates Cursor's subscription the better value.
Published Jul 9, 2026self-described: Solo, under a month on Devin
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Found SWE-1.5 and 1.6 fine for grunt work and tests, but says paid-model usage has been cut sharply since the US$15 plan, and a Codex subscription is now better value.
Published Jul 8, 2026self-described: Solo; used Windsurf before the rename
Practitioner account, pseudonymous; direct use; counts toward Cost predictability and limits
Tried Windsurf's free tier for about a week when the Claude weekly quota ran out, and found tab completion fast and Cascade reliably executing small-to-medium refactors. Calls it good but didn't keep it: its target user isn't a solo agentic-AI shipper, and the paid tier adds Opus access already had directly.
Published May 25, 2026self-described: Solo founder; one-week trial on the free tier
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Reliability, Operational control, Cost predictability and limits
Their team moved to Windsurf from Copilot, and the author finds it most useful for answering questions about a monorepo of a bit over 1M LoC; the supertab feature was also very useful. Almost never asks it to do complex tasks, since describing them takes almost as long as implementing.
Published Dec 14, 2025self-described: Team working in a monorepo of over 1M lines of code, moved from Copilot to Windsurf
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Uses Windsurf mainly for completions that predict their next edit, keeping them in control of the codebase and writing everything themselves without delegating to an agent.
Published Jul 12, 2025self-described: Solo; completion-first use
Practitioner account, pseudonymous; direct use; not counted, takes no position
Tried Windsurf's free tier for about a week when the Claude weekly quota ran out, and found tab completion fast and Cascade reliably executing small-to-medium refactors. Calls it good but didn't keep it: its target user isn't a solo agentic-AI shipper, and the paid tier adds Opus access already had directly.
Published May 25, 2026self-described: Solo founder; one-week trial on the free tier
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Reliability, Operational control, Cost predictability and limits
Keeps Windsurf as their primary IDE because bring-your-own-key covers prompts, agents and autocomplete, including in Vim, which the commenter says Cursor and Zed do not offer.
Published Mar 20, 2026self-described: Solo; Windsurf is their primary IDE
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Moving between Windsurf and GitHub Copilot, the commenter credits Windsurf's whole-codebase indexing for completions across files and Cascade's terminal handling, while rating Cursor's checkpoint undo higher.
Published May 7, 2025self-described: Evaluating Windsurf against GitHub Copilot
Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep
Using their company's Windsurf license for staff-level Android tooling work, the commenter finds autocomplete distracting and the agent hallucinating answers for uncommon tasks.
Published May 18, 2025self-described: Staff-level Android tooling work on a company license
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
After switching between both, the commenter prefers Cursor's completions, credits Windsurf with better project awareness across files that is hard to trigger, and notes its lower price.
Published May 12, 2025self-described: Solo; switches between Cursor and Windsurf
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
In their first week completions helped with repetitive renames across files but often mangled unrelated code, the UI felt noisy, and chat sometimes scanned files endlessly with no output.
Published Apr 21, 2025self-described: First week of individual use
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Testing all three on GPT-5 over a weekend, the author found Windsurf explained an existing codebase best, kept context across the session and scaffolded a project unprompted, with slower inline suggestions.
Published Sep 3, 2025self-described: Solo weekend test on greenfield and brownfield projects
Trialling both editors on the same PHP codebases, the commenter got poorer results from Windsurf on existing code, saw it read files 50 lines at a time, and went back to PhpStorm.
Published May 12, 2025self-described: Trialled Cursor and Windsurf on the same PHP codebases
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Each time the commenter tried the Windsurf Editor and its Vim and IntelliJ plugins it felt unpolished, and autocomplete felt much snappier in Cursor and in GitHub Copilot.
Published May 6, 2025self-described: Tried the editor and the Vim and IntelliJ plugins
Practitioner account, pseudonymous; direct use; not counted, takes no position
Tried Windsurf's Arena Mode on a test-completion task, with AGENTS.md and rules files in place, and saw the same failure as in Claude Code; the commenter reviews every command it runs.
Published Mar 6, 2026self-described: Engineer at a company with AGENTS.md and rules files in place
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Positive
Darryn Dieken, Chief Availability Officer at Salesforce
Salesforce offers Cursor and Windsurf for code and test generation, with over 85% of eligible engineers using AI tools weekly; code in production rose 30%, which pushed the bottleneck to review and testing.
"A few tools in this portfolio include: Cursor and Windsurf for AI-assisted code and tests generation…"
Excerpt, Darryn Dieken
Published Dec 16, 2025Engineering productivity and reliability for thousands of Salesforce engineers across 25 Hyperforce regions
Practitioner account, name and role on their organization's own page; ran the rollout; not counted, takes no position
Reports that Windsurf's agent replaced their dashboard with its own component, removed files without approval despite their rules, and broke the app again after restoring it.
Published Jul 27, 2025self-described: Solo, a Next.js app
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability, Operational control
Their workplace still uses Windsurf, but the commenter canceled their personal plan because Claude Sonnet 3.7 output and issue analysis in it were too often wrong to justify paying.
Published Jul 16, 2025self-described: Their workplace uses Windsurf; the commenter canceled a personal plan
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Positive
David Roff, Software Engineer at World Wide Technology
Roff reports a personal productivity gain above 70% and similar gains across his engineering team, to the point that QA struggles to keep up, while every Windsurf change still goes through a senior engineer's review.
"Team-wide benefits: The entire engineering team has experienced similar productivity gains."
Excerpt, David Roff
Published Jul 14, 2025Full stack platform team: web, React Native mobile, APIs and databases; WWT also sells Windsurf adoption services
Practitioner account, name and role on their organization's own page; direct use; counts toward Delivered outcomes, Operational control
Testing Windsurf, the commenter found it installed dependencies into their global Python without a virtual environment and rewrote code the commenter had not asked it to change.
Published May 12, 2025self-described: Solo, a Python project
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Found the same models produced noticeably worse code in Windsurf than in Zed, Copilot or Cursor, with erratic tool use, so the commenter canceled and made Copilot their daily driver.
Published May 12, 2025self-described: Solo; former subscriber
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
The commenter likes Windsurf for exploration but writes code they want to keep by hand, warning that without deep review of every Windsurf change you lose understanding of the codebase.
Published May 6, 2025self-described: Solo; writes code the commenter keeps by hand in Vim
Practitioner account, pseudonymous; direct use; not counted, takes no position
In their first week completions helped with repetitive renames across files but often mangled unrelated code, the UI felt noisy, and chat sometimes scanned files endlessly with no output.
Published Apr 21, 2025self-described: First week of individual use
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Positive
John Hoestje, Software Architect and Developer at Keyhole Software
Hoestje built two apps from Cascade prompts without editing a line by hand, and says he fell short when he moved too fast to review Cascade's suggested changes.
"I fell short when I was trying to go too fast. I didn’t take the time to properly review the suggested changes by Cascade."
Excerpt, John Hoestje
Published Mar 20, 2025Software consultancy; solo experiments building a React site and a Flutter Sudoku game
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Reliability, Operational control, Adoption and upkeep
Built an Umbraco thumbnail tool with Windsurf in a few hours, but it reintroduced old bugs two or three times. The author did not read the code, so would not use it for supported work.
Published Mar 16, 2025self-described: Solo, a small web tool built in an afternoon
Practitioner account, self-described; direct use; counts toward Delivered outcomes
Danilchenko measured Devin Local at roughly 18,000 tokens against about 24,000 for Cascade on a 14-file refactor and saw subagents split work "maybe 40% of the time on multi-step tasks". Calls Devin Local measurably better than Cascade, but says the acquisition story creates real trust risk.
Published Jun 6, 2026self-described: Hands-on review after the rename; personal blog
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Reliability, Operational control, Cost predictability and limits, Adoption and upkeep
Positive
Chizaram Ken, frontend developer writing for LogRocket
Building a Next.js todo app with Gemini 2.5 Pro in Cascade, Ken saw it update the correct files without being told and import Lucide-react without installing it. After a planned theme change, the theming "seems to have broken somewhere" until a few more iterations fixed it.
Published Jul 31, 2025self-described: Solo, a Next.js to-do app built with Cascade
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Operational control, Cost predictability and limits, Adoption and upkeep
Tried agent workflows in Copilot and Windsurf on Claude 3.5 and 4; they got stuck or built themselves into corners, and the output was fragile enough to refactor immediately.
Published Jul 12, 2025self-described: Solo; tried agent workflows in Copilot and Windsurf
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Mixed
Mark Winteringham, tester, toolsmith, author and instructor
Working in small tasks after a messy start in Cursor, Winteringham had the Windsurf agent fix each failing unit test quickly, though it wrote more code than he expected.
"After that, I worked with the Windsurf agent to fix each of the failing tests. This process worked well, and it didn’t take too much time to get them all to pass."
Excerpt, Mark Winteringham
Published Jun 10, 2025self-described: Solo; migrating his public restful-booker-platform front end to Next.js
Practitioner account; direct use; counts toward Delivered outcomes, Reliability, Cost predictability and limits
Using their company's Windsurf license for staff-level Android tooling work, the commenter finds autocomplete distracting and the agent hallucinating answers for uncommon tasks.
Published May 18, 2025self-described: Staff-level Android tooling work on a company license
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Vibe coding a web app, the commenter found Cascade good at locating where to change the codebase, but it could not solve performance or CSS animation problems without their direction.
Published May 8, 2025self-described: Solo, a web app built with Windsurf
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
After a month with each, Bergholz chose Windsurf for better codebase understanding and a smoother UI, and uses memories and a .windsurfrules file to correct it on a niche Elixir stack.
Published Mar 10, 2025self-described: Solo side projects in Elixir, Phoenix, React and Inertia
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Cost predictability and limits
Discussed without concern, 1
Positive
Jason Valentino, Head of Software Engineering Strategy at BNY
Valentino reports that BNY engineers have Windsurf, Copilot and Claude Code. Today peer review means using the peer review agent in Windsurf or Claude Code, which "makes life better" but is still human driven; the goal is a deterministic evaluation when a merge request hits.
"Right now, peer review is something that like, “Hey, you got Windsurf or you have ClaudeCode installed, you used the peer review agent, it makes life better.” It’s still human driven."
Excerpt, Jason Valentino
Published Jun 8, 2026Bank with more than 8,000 engineers; owns developer tooling and DevEx
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.Quick Review runs a second agent over local Devin Local changes before commit, with the SWE-check model free on every plan. It is not available for the legacy Cascade agent and does not replace human review before merge. Quick Review
When the product was still Windsurf, terminal runs hung or froze nearly every time until the commenter wired up a workaround skill; the commenter says its multi-agent UI lead has since disappeared.
Published Sep 10, 2026self-described: Former Windsurf user
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Measured the editor freezing for about five minutes after every Cascade response on Linux, traced with strace to a blocked renderer thread and dozens of duplicate calls.
Published Feb 10, 2026self-described: Solo, Linux (Pop!_OS)
Practitioner account, pseudonymous; structured test; counts toward Reliability, Operational control
Reports that every terminal command the agent ran on Windows PowerShell stayed in a running state and never returned, while the same commands worked when run by hand.
Published Oct 10, 2025self-described: Solo, Windows with PowerShell
Practitioner account, pseudonymous; direct use; counts toward Reliability
Adopted Windsurf at launch for its UX, then saw more issues with each update, including the agent hanging on shell commands, and moved back to GitHub Copilot.
Published Jul 11, 2025self-described: Solo; adopted Windsurf at launch
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
After an update, every Cascade step failed with an invalid tool call and then an internal error, leaving the reporter unable to use a US$60 monthly subscription that had worked smoothly before.
"…i was coding smoothly without any issues before the update. Now i cannot use my 60 buck monthly subscription anymore."
Excerpt, Bwogi
Published Jan 30, 2025self-described: Solo; Next.js, TypeScript and Tailwind on macOS
Practitioner account, pseudonymous; direct use; counts toward Reliability
After a few months the commenter finds Windsurf useful when tired or in unfamiliar areas, but waiting and errors break flow. On familiar work the commenter puts it at half the speed of typing.
Published Jun 3, 2025self-described: Solo, a few months of use
Practitioner account, pseudonymous; direct use; counts toward Reliability
Found the same models produced noticeably worse code in Windsurf than in Zed, Copilot or Cursor, with erratic tool use, so the commenter canceled and made Copilot their daily driver.
Published May 12, 2025self-described: Solo; former subscriber
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
In their first week completions helped with repetitive renames across files but often mangled unrelated code, the UI felt noisy, and chat sometimes scanned files endlessly with no output.
Published Apr 21, 2025self-described: First week of individual use
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
3Vendor Direction9 of 12 sources on it raise it as a concernThe effect of ownership changes, the rename, model access, and support on buying decisions.
A long-time Windsurf user, the commenter says the product has fallen several features behind Cursor since becoming Devin, and has gone back to VS Code with Copilot Pro.
Published Sep 11, 2026self-described: Long-time Windsurf user
Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep
Enjoying Devin's cloud agents after comparing alternatives, the commenter calls the gap between Devin cloud and Devin Desktop embarrassing, describing Desktop as a thinly reskinned Windsurf.
Published Sep 11, 2026self-described: Solo; evaluated cloud agents after leaving Cursor
Practitioner account, pseudonymous; opinion; not counted, takes no position
Their organization was a Windsurf customer at the acquisition, then left after Cognition stopped offering support, raised prices twice and dismantled the brand.
Published Jul 8, 2026self-described: Their organization, a former Windsurf customer
Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep
Danilchenko measured Devin Local at roughly 18,000 tokens against about 24,000 for Cascade on a 14-file refactor and saw subagents split work "maybe 40% of the time on multi-step tasks". Calls Devin Local measurably better than Cascade, but says the acquisition story creates real trust risk.
Published Jun 6, 2026self-described: Hands-on review after the rename; personal blog
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Reliability, Operational control, Cost predictability and limits, Adoption and upkeep
Negative
cactca, Hacker News commenter and self-described Windsurf subscriber
Saw Windsurf as slightly better than Cursor, with a nicer chat panel and autocomplete and a US$5 cheaper plan, until losing Anthropic model access cost it users.
Published Jul 11, 2025self-described: Former Windsurf user
Practitioner account, pseudonymous; opinion; not counted, repeats a stronger account
A paid user, the commenter asks Windsurf to stop chasing frontier models and build predictable workflows: task boards, TDD, git branches without reliance on undo, and docs kept in sync with code.
Published May 19, 2025self-described: Paid individual user
Practitioner account, pseudonymous; direct use; not counted, takes no position
Their company has run it on an enterprise plan for about nine months. The commenter rates it above Copilot but now finds Claude and Codex better, and Devin's web and desktop harnesses inconsistent.
Published Sep 10, 2026self-described: Their company, on an enterprise plan for about nine months
Practitioner account, pseudonymous; direct use; not counted, takes no position
Anthropic cut Windsurf's direct Claude capacity with little notice in June 2025, and a Windsurf customer since late 2024 switched to Cursor to keep using Claude 4.
"Windsurf CEO Varun Mohan said in a post on X Tuesday that Anthropic gave Windsurf little notice for this change, and the startup now has to find other third-party compute providers to run several of Anthropic’s most popular AI models on its platform."
Excerpt, TechCrunch
Published Jun 3, 2025self-described: Windsurf subscribers using Claude models
Uses Cognition's SWE-1.6 model for grunt work alongside Opus for planning and harder problems, and is pleased with Cognition's progress since it took over Windsurf.
Published Jul 8, 2026self-described: Former Windsurf user, now on Devin Desktop
Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep
After more than a year on Windsurf, their move to Devin Desktop kept their extensions and settings, and Copilot CLI running over ACP picked up and resumed their existing sessions.
Published Jun 4, 2026self-described: Solo; more than a year on Windsurf
Practitioner account, self-described; direct use; counts toward Adoption and upkeep
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.Cognition's FAQ states that plans and pricing did not change with the June 2, 2026 rename. Existing settings carry over, and the Windsurf JetBrains plugin is in maintenance mode. Devin Desktop FAQ
Grandfathered on old pricing, the commenter used Windsurf as their main editor until the pricing model changed and now uses it only to spend their weekly tokens on frontier models.
Published Sep 10, 2026self-described: Grandfathered individual subscriber
Practitioner account, pseudonymous; direct use; not counted, takes no position
After under a month on Devin the commenter hits the US$20 plan's limits faster than with Claude Code or Codex, and rates Cursor's subscription the better value.
Published Jul 9, 2026self-described: Solo, under a month on Devin
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Found SWE-1.5 and 1.6 fine for grunt work and tests, but says paid-model usage has been cut sharply since the US$15 plan, and a Codex subscription is now better value.
Published Jul 8, 2026self-described: Solo; used Windsurf before the rename
Practitioner account, pseudonymous; direct use; counts toward Cost predictability and limits
Left Windsurf, and later Cursor, after each cut their usage quota within weeks or months of their paying for a plan; the commenter never returned to Windsurf.
Published Apr 4, 2026self-described: Former Windsurf subscriber
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Mixed
CSMastermind, Hacker News commenter who evaluates dev tooling for their company
Still rates Windsurf ahead of Cursor but has moved to Codex for its cloud environments; pricing kept them from rolling Windsurf out across their company.
Published Nov 5, 2025self-described: Decides tooling across their company
Practitioner account, pseudonymous; direct use; not counted, takes no position
Mixed
CSMastermind, Hacker News commenter who evaluates dev tooling for their teams
Evaluating tools for their teams, the commenter found Windsurf the one tool that raised their productivity beyond chat, especially on command-line work, but held back a team rollout over pricing.
Published Apr 22, 2025self-described: Evaluates tools for their engineering teams
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Their organization was a Windsurf customer at the acquisition, then left after Cognition stopped offering support, raised prices twice and dismantled the brand.
Published Jul 8, 2026self-described: Their organization, a former Windsurf customer
Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep
Uses Cursor until hitting a wall, then switches to Windsurf, which the commenter says solves issues Cursor fails on after 40 minutes of retries, though its plans are limited.
Published May 12, 2025self-described: Solo; uses Cursor and Windsurf
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
A daily full-time Windsurf user, the commenter calls it inferior to open-source agents such as Cline and Claude Code that use provider keys directly, without flow credits.
Published Apr 21, 2025self-described: Daily full-time use
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Danilchenko measured Devin Local at roughly 18,000 tokens against about 24,000 for Cascade on a 14-file refactor and saw subagents split work "maybe 40% of the time on multi-step tasks". Calls Devin Local measurably better than Cascade, but says the acquisition story creates real trust risk.
Published Jun 6, 2026self-described: Hands-on review after the rename; personal blog
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Reliability, Operational control, Cost predictability and limits, Adoption and upkeep
Mixed
zazibar, Hacker News commenter at a company with over 400 engineers
Their 400-engineer company canceled all IDE subscriptions, Windsurf included, and moved everyone to Claude Code as a cost-saving measure with no migration plan. Token spend then forced limits.
Published Apr 12, 2026self-described: Company of over 400 engineers that canceled its Windsurf subscriptions
Practitioner account, pseudonymous; second-hand; not counted, takes no position
On a US$50 monthly budget the commenter pays US$20 for Windsurf for access to nearly all models, reserving Claude Opus and Sonnet for tricky work once requirements are clear.
Published Mar 24, 2026self-described: Solo on a US$50 monthly tooling budget
Practitioner account, pseudonymous; direct use; counts toward Cost predictability and limits
Recommends Cascade for agentic code writing and exploration, saying it saved them many hours understanding new codebases and tracing data flows; Claude 3.5 cost credits.
Published Feb 24, 2025self-described: Individual use on new codebases
Practitioner account, pseudonymous; direct use; counts toward Operational control
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.Since March 2026, self-serve plans include a daily and weekly quota drawn down per token, with extra usage billed at API list prices. On Teams, admins set auto-reload thresholds and default session spending limits. Reports about credit plans describe a system that no longer applies. Quota-based usage
5Context Management6 of 9 sources on it raise it as a concernWhether the agent finds enough context in large files and retains it through long sessions.
Trialling both editors on the same PHP codebases, the commenter got poorer results from Windsurf on existing code, saw it read files 50 lines at a time, and went back to PhpStorm.
Published May 12, 2025self-described: Trialled Cursor and Windsurf on the same PHP codebases
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Once ahead of Cursor on agentic coding in their view, Windsurf now frustrates them by gathering context 100 to 200 lines at a time. The commenter blames that for bugs and poor results.
Published May 12, 2025self-described: Solo, agentic coding
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
After switching between both, the commenter prefers Cursor's completions, credits Windsurf with better project awareness across files that is hard to trigger, and notes its lower price.
Published May 12, 2025self-described: Solo; switches between Cursor and Windsurf
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Asks Windsurf to lift Cascade's limit of 20 saved conversations, since the oldest is lost for good when a 21st starts and past conversations are worth revisiting.
Published Feb 18, 2025self-described: Solo, Cascade conversations
Practitioner account, pseudonymous; direct use; counts toward Operational control
A paid user, the commenter asks Windsurf to stop chasing frontier models and build predictable workflows: task boards, TDD, git branches without reliance on undo, and docs kept in sync with code.
Published May 19, 2025self-described: Paid individual user
Practitioner account, pseudonymous; direct use; not counted, takes no position
Built an Umbraco thumbnail tool with Windsurf in a few hours, but it reintroduced old bugs two or three times. The author did not read the code, so would not use it for supported work.
Published Mar 16, 2025self-described: Solo, a small web tool built in an afternoon
Practitioner account, self-described; direct use; counts toward Delivered outcomes
A long-time VS Code user, Agrawal liked queuing several instructions while Cascade works and its persistent memory, but finds the overlap with VS Code agent mode significant.
Published Mar 4, 2026self-described: Solo; VS Code user trying Windsurf
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Reliability, Operational control
Using Windsurf at work alongside Claude Code, the commenter says its UX adds real value and Codemaps have been excellent for weeks, though code churn could make them harder to maintain.
Published Nov 4, 2025self-described: Uses Windsurf at work alongside Claude Code
Practitioner account, pseudonymous; direct use; not counted, takes no position
Testing all three on GPT-5 over a weekend, the author found Windsurf explained an existing codebase best, kept context across the session and scaffolded a project unprompted, with slower inline suggestions.
Published Sep 3, 2025self-described: Solo weekend test on greenfield and brownfield projects
Checked Oct 12, 2026.Memories apply only to the legacy Cascade agent; Devin Local reads rules in .devin/rules and AGENTS.md files, and Cognition recommends moving memories to skills with the Cascade Migration Wizard. Memories and rules
6Needs Close Steering3 of 8 sources on it raise it as a concernSupervision the Cascade or Devin Local agent needs to stay on task, such as stalling on a search or changing code outside the request.
Tried agent workflows in Copilot and Windsurf on Claude 3.5 and 4; they got stuck or built themselves into corners, and the output was fragile enough to refactor immediately.
Published Jul 12, 2025self-described: Solo; tried agent workflows in Copilot and Windsurf
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Testing Windsurf, the commenter found it installed dependencies into their global Python without a virtual environment and rewrote code the commenter had not asked it to change.
Published May 12, 2025self-described: Solo, a Python project
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
In their first week completions helped with repetitive renames across files but often mangled unrelated code, the UI felt noisy, and chat sometimes scanned files endlessly with no output.
Published Apr 21, 2025self-described: First week of individual use
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Testing all three on GPT-5 over a weekend, the author found Windsurf explained an existing codebase best, kept context across the session and scaffolded a project unprompted, with slower inline suggestions.
Published Sep 3, 2025self-described: Solo weekend test on greenfield and brownfield projects
Over three days Windsurf wrote multi-file game logic, refactored on request and fixed bugs that would take them half an hour; the commenter made 95% of changes by instructing it.
Published Aug 13, 2025self-described: Solo, a game project
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Positive
Steve Lewis, Lead Software Engineer at World Wide Technology
Lewis reports that the team has used Windsurf for a few months. Planning the architecture with it, Lewis built S3 and CloudFront hosting in Terraform plus a Node.js upload script in less than 1 day against an estimated 2-3 days, and argues such tools need someone to drive them and provide context.
"Our team has been using Windsurf as an AI-powered development environment for a few months now."
Excerpt, Steve Lewis
Published Jul 23, 2025Team building a mobile app backend on AWS with Terraform; WWT also sells Windsurf adoption services
Practitioner account, name and role on their organization's own page; direct use; counts toward Delivered outcomes
Chooses Windsurf, running parallel Cascade sessions, one investigating a bug while another builds a feature, and drops in later to review and accept the changes.
Published May 12, 2025self-described: Solo, parallel Cascade sessions
Practitioner account, pseudonymous; direct use; not counted, takes no position
Positive
Matt Wolfe, founder of FutureTools and technology video creator
Questions the sources split on, with the count on each side.
Evidence remains mixed
After trying it next to other tools, do practitioners keep Devin Desktop (formerly Windsurf)?
822
Kept it, 8 sources
Some chose it over Cursor or Copilot for codebase awareness, a cleaner editor, dev container and WSL support, or price.
Moved to another tool, 22 sources
Others moved to Cursor, GitHub Copilot, Claude Code, or Codex, citing output quality, reliability, pricing changes, or the change in ownership.
Evidence remains mixed
Once review and rework are counted, does it save engineering time?
82
Net time saved, 8 sources
Some report clear gains, from a migration bug fixed after an hour of manual debugging to tasks finished well ahead of hand coding.
Absorbed by review, 2 sources
Others find waiting, errors, and fragile output cancel the gain on work they know well.
Evidence remains mixed
How much work should the agent complete before a human checkpoint?
45
Broader delegation, 4 sources
Some run parallel agent sessions or describe most changes in prose and let the agent make them.
Tighter steering, 5 sources
Others write the outline themselves, or use it mainly for completions, so they stay in control of the code.
The evidence
Whose experience this is
The three groups, then every practitioner by the context they work in, and how emphasis changes with scale.
Three groups drawn from the same sources. Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. Signals open on All practitioners. Leaders and teams have 14 accounts; GILD prints their sentiment from 20.
Engineering leaders and teams
23 sources. Leaders' accounts cover rollout decisions, pricing, vendor stability, and what changes when Devin Desktop moves from individual use to a team standard.
Individual builders
63 sources. Individual builders' accounts cover codebase context, completions, agent reliability, and usage limits in self-directed work.
All practitioners
86 sources. All accounts together give the broadest read. They combine individual and team settings that can reach different conclusions.
86 sources from practitioners, by the context they work in. Filled rows count for this group.
Individual practitionerSolo developers and independent builders63 sources, counted here
Emphasizes Codebase context and usage limits
Very small team2 to 10 engineersNo sources from this setting yet
Professional team11 to 50 engineers, or a named company's team7 sources, counted here
Emphasizes Company licenses and output quality
Technical leadershipLeaders setting adoption across teams11 sources, counted here
Emphasizes Standardizing on an editor and pricing for a rollout
Organization-wideEnterprise or company-wide rollout5 sources, counted here
Emphasizes Company-wide seats and whether engineers use them
What changes with scale. Individual builders write most about how well it understands their codebase and about usage limits. Team and leadership accounts focus on the rollout decision: two CTOs standardized on the editor, ServiceNow's across about 7,000 engineers, while other companies canceled seats or moved to Claude Code.
Where the sources come from
Where this group's sources were published.
Counted for All practitioners, from 86 sources. Change group
106 sources for this group, 20 of them documentation
Developer Communities64, 60% of 106 sources
Product Documentation20, 19% of 106 sources
Engineering Blogs & Reviews17, 16% of 106 sources
Podcasts, Talks & Videos5, 5% of 106 sources
Older evidence stays when it still applies. Sources tied to Cascade, credit pricing, or a replaced model remain marked Needs a recheck or Out of date.
Nov 1, 2026: by the owner's decision, a record whose own words state no overall view of Devin Desktop now casts no vote; it still counts toward its topics and is listed, and 11 records that counted leave the vote this way. Leaders and teams stay unscored, individual builders move from +13 to +12 and all practitioners stay at +17.
Oct 31, 2026: rewrote 9 summaries that two blind coders found overstated their sources, so each says what its source says. Indeed's talk states no view of Windsurf, so it carries no sentiment and no editor-choice side. Leaders and teams fall to 19 counted sources, one short of the 20 a reading needs, so the page opens on all practitioners, who move from +29 to +30.
Oct 30, 2026: a second-model check corrected four comparison accounts and one record. TechCrunch's report on the Claude capacity cut is filed with individual builders, since its reporter speaks for no team. ServiceNow's Copilot comparison account now quotes the article's 10% measurement, Indeed's accounts name the talk DX published in June 2026, since DX's page prints no day, ServiceNow's account says Windsurf, as The New Stack does, and notes its rename to Devin Desktop, Disney's Copilot account reports the plan and the employees' comments as separate facts, and its Codex account reads as an evaluation, since Disney has only announced a plan.
Oct 28, 2026: added 4 records from GILD's research ledger: a Hacker News subscriber who cancelled after Cognition's acquisition, C3 AI's survey of coding agents, TechCrunch's report that Windsurf lost direct Claude capacity, and Brex on Latent Space, and quoted ServiceNow's account already listed. Three state no view of Devin Desktop and count toward no figure. Leaders and teams stay at +49 on 20 counted sources, individual builders move from +20 to +18 on 59, and all practitioners from +31 to +29 on 79.
Builds the evidence base from public sources only: every source links to the page it comes from and names its author and publication date.
Counts sources written under the Windsurf name when they describe the same editor, and marks each one for whether it still applies after the move to Devin Desktop and Devin Local.
Shows a finding for a group only when at least 5 sources from 3 different authors discuss it, and a disagreement only with at least 2 sources on each side.
Adds 4 team, leadership, and organization-wide accounts found on October 12, 2026: Hacker News comments that state the team or company behind them.
Admits English-language sources published in 2025 or later only. This removed 6 sources: 4 written before 2025, a non-English company post, and an IT services firm's setup guide. The evidence window now ends at the newest source, September 11, 2026.
Drops the Permissions & Safety concern and the written-conventions statement, which the public sources do not support at those minimums.
Oct 25, 2026: added Needs Close Steering from what existing accounts state. Here, 3 report the agent stalling or changing code they did not ask about. Also, 3 say it carried work through with little direction.
Oct 25, 2026: added 5 sources from outside Hacker News, each with a verbatim quote. These include ServiceNow CTO Pat Casey on a 7,000-engineer rollout and a Ministry of Testing article. Others are a Keyhole Software blog post, an X post, and a GitHub issue.
Method
A running review of what engineering teams report about Devin Desktop (formerly Windsurf), from individual builders to company-wide rollouts. Each finding links to its sources, and each conflict shows both sides.
Counts cover only the sources GILD reviewed.
Who counts
Engineering leaders and teams
Very small team, Professional team, Technical leadership, Organization-wide
Individual builders
Individual practitioner
All practitioners
Everyone in the leaders and teams and individual builders groups
Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. GILD files each source in a group from how the account describes its author. A role or employer marked self-described is what the source states about themselves. Documentation checks facts for every group and never counts toward sentiment.
How the numbers work
Overall signal. Positive votes minus negative ones, per 100 votes from the sources that take a side. Each author counts once, with their latest view, whoever they are and wherever they posted. The older weighted reading, where accounts GILD matched to a named person count three times when GILD lists the author among engineering leaders and twice otherwise, is shown beside it as a second view. Where an author wrote more than one source, the line beside the split gives the votes, one per author, so the score follows from it. When one author's sources from the same day disagree, that author counts as mixed, and a half point rounds away from zero. On the AI coding agent hubs, each account's overall stance comes from GILD's blind coding: two models from different families read the source's own words without seeing each other's codes, and a third settled where they differed. An account that states no overall view there, such as a bug report, casts no vote and still counts toward its topics. Other hubs count the stance stored on each record. Sources with no opinion are listed and not counted. Strong positive is +50 or higher, positive +20 to +49, mixed −19 to +19, negative −20 to −49, strong negative −50 or lower.
Weighted reading, second view. Counted the older way, where an account GILD matched to a named person counts two or three times, all practitioners read +30 positive (method sentiment/S1). GILD printed that number as "GILD score" until October 29, 2026; most of those matches rest on a name or a self-described role.
Method change, Oct 30, 2026. GILD changed how practitioner sentiment counts, to one vote per author. Weighted, it read +49 Positive; with one vote per author it read +28 Positive. No evidence changed.
Correction, Nov 1, 2026. GILD now takes each account's overall stance from its blind two-model coding, and accounts that state no overall view cast no vote. It still reads +17 Mixed.
Unscored. A group gets a score only with 20 sources from 15 authors. Below that, one source moves the score about 5 points, so the read says "Unscored until 20 sources from 15 authors" and shows its counts.
Independence. A source whose author works for the vendor, for one of its partners or programs, or for a competitor, and a page the vendor published or ran, is listed with that tie and counts toward nothing. One author counts on at most two records per product. The line under the score says how many authors and how many separate discussions the counted sources come from: comments in one thread are one discussion.
Praise and concerns. How many of the sources that discuss a theme praise it or raise it.
Consensus. A statement joins when 20% of the group's sources support it and fewer contradict it. Contradicting sources are counted separately. Below that line a statement shows as building. At 40% or more it reads Strong agreement; below, Recurring point.
Disagreements. The count on each side. GILD names no winner and gives no share of all users.
Minimum evidence. A finding needs 5 sources from 3 authors; a disagreement also needs 2 on each side. Smaller counts stay in the table below, marked under the minimum.
Labels on a source
A source's date and whether it still applies are separate: a recent post can describe an old version, and an old one can still hold.
Documented
Stated in official documentation.
Reported
A practitioner's account of their own use.
Measured
Backed by the source's own measurements, such as a comparative test or tracked team metrics.
GILD analysis
GILD's check of a claim against official documentation.
Current
Describes the product as it is now.
Still applicable
Older, and the behavior or lesson still holds.
Needs a recheck
May depend on a plan, version or setting that changed since it was written. It keeps counting until GILD rechecks it, since the rest of the account usually holds, and its card says so.
Out of date
No longer accurate. Kept in the record; counts toward nothing current.
Flagged for a recheck, of the sources that take a side: leaders and teams 7 of 14, individual builders 41 of 53, all practitioners 48 of 67.
Limits
The figures come from 86 reviewed sources. They do not represent all Devin Desktop or Windsurf users. Hacker News comments account for 57 and GitHub issues for 6. Named developers' blogs and reviews account for 9, company blogs for 6, recorded talks and podcasts for 5, and an organization write-up, a news report and an X post for 1 each. A GitHub issue counts as mixed unless its author rejects the product, since a bug report from someone still using it is not a verdict. 23 sources speak for a team, leader, or organization: 12 Hacker News comments, ServiceNow's CTO, who reports a measured 10% gain after rolling Windsurf out to about 7,000 engineers, and engineering leaders and teams at Salesforce, World Wide Technology, Indeed, BNY, Every, C3 AI and Brex. Review burden and the choice to keep or leave the editor are the leaders' findings that reach 5 sources from 3 authors. Cognition publishes its customer stories on its official domain, so they appear as Operator Insights and are not counted here.
Most sources predate the June 2, 2026 rename and describe Windsurf with Cascade. Sources tied to Cascade behavior, credit pricing, or a replaced model carry the Needs a recheck label. Sources about discontinued credit plans carry the Out of date label.
Every count, and the sources behind it
19 findings for 3 groups
Each row opens its sources for the group you are reading.
GILD's checks of claims against official documentation, kept apart from the source counts.
Usage / Cost. Since March 2026, self-serve plans include a daily and weekly quota drawn down per token, with extra usage billed at API list prices. On Teams, admins set auto-reload thresholds and default session spending limits. Reports about credit plans describe a system that no longer applies. Quota-based usage, checked Oct 12, 2026
Requires Strong Review. Quick Review runs a second agent over local Devin Local changes before commit, with the SWE-check model free on every plan. It is not available for the legacy Cascade agent and does not replace human review before merge. Quick Review, checked Oct 12, 2026
Context Management. Memories apply only to the legacy Cascade agent; Devin Local reads rules in .devin/rules and AGENTS.md files, and Cognition recommends moving memories to skills with the Cascade Migration Wizard. Memories and rules, checked Oct 12, 2026
Vendor Direction. Cognition's FAQ states that plans and pricing did not change with the June 2, 2026 rename. Existing settings carry over, and the Windsurf JetBrains plugin is in maintenance mode. Devin Desktop FAQ, checked Oct 12, 2026