Windsurf AI marketing: can your IDE agent launch your SaaS?

What Windsurf can do for a launch, according to its docs

We read the docs, the changelog and the pricing page on September 29, 2026. The product changed name and agent this year, so check the linked source before you rely on a detail.

Who makes it

Cognition, the company behind the Devin agent, signed a definitive agreement to acquire Windsurf in July 2025.cognition.com ↗ · Checked on September 29, 2026

The new name

On 2 June 2026 Windsurf became Devin Desktop, shipped as a normal update. Plans, pricing, settings and extensions carried over; the app is now called Devin.docs.devin.ai ↗ · Checked on September 29, 2026

Cascade is gone

Since release 3.9.19 on 8 September 2026, Cascade has been removed. Devin Local is now the only agent in Devin Desktop, and old Cascade conversations can be continued there.docs.devin.ai ↗ · Checked on September 29, 2026

AGENTS.md and rules

Devin Local reads AGENTS.md at the project root at the start of every session. It also loads legacy .windsurfrules and .windsurf/rules files, CLAUDE.md, and rules in .devin/rules.docs.devin.ai ↗ · Checked on September 29, 2026

MCP

MCP servers are added with devin mcp add or in mcp_config.json, per user (~/.config/devin/) or per project (.devin/). Local stdio servers, Streamable HTTP and SSE are supported.docs.devin.ai ↗ · Checked on September 29, 2026

Permissions

Devin Local replaces Cascade’s auto-execution levels, Turbo included, with allow, ask and deny rules. They cover file reads and writes, shell commands, web fetches and MCP tools, per project, user or organisation.docs.devin.ai ↗ · Checked on September 29, 2026

Built-in browser

Previews open your local dev server in a browser pane next to the agent, so you can send elements and console errors back to it. They are built for your own app.docs.devin.ai ↗ · Checked on September 29, 2026

Plans

Free at $0 with a light agent quota, Pro at $20 a month and Max at $200 a month, plus Teams and Enterprise plans. Extra usage beyond the quota is billed at API rates.devin.ai ↗ · Checked on September 29, 2026

Attaching to your Chrome

Chrome DevTools MCP with --autoConnect attaches to the Chrome you already use: Chrome 144 or newer, remote debugging switched on at chrome://inspect/#remote-debugging, and a click on Allow.github.com ↗ · Checked on September 29, 2026

Where Windsurf AI marketing automation needs a human

None of this is a flaw in Windsurf. Directories are built to stop unattended bots, and an IDE agent is still a coding tool first. Plan for these stops before you start:

A real browser

Out of the box the agent can fetch web pages and preview your own app, but it has no browser for signing in to third-party sites. For directories you add Chrome DevTools MCP and connect it to your Chrome.

Sign-ins

Most directories need an account. Sign in yourself in your own Chrome, once per platform.

CAPTCHA and bot checks

Cloudflare, reCAPTCHA and hCaptcha show up on many submit forms. You solve them in the same window. LaunchRepo’s playbooks never try to evade a challenge.

2FA and email codes

Verification links land in your mailbox. If that mailbox is not open in the same Chrome, you click the link or pass on the code yourself.

Paid upsells

Many launch platforms push a paid fast track. An agent must be told plainly that it may not buy anything.

Knowing what “live” means

A thank-you page is not a listing. Some platforms queue for weeks, some review by hand. Someone has to record what actually happened on each one and when to check again.

LaunchRepo with a browser agent →

Rules, skills and MCP for launch work

Search for Windsurf rules or skills for marketing and you mostly find prompts for copy, SEO and landing pages. They help with launch text. They do not tell your agent which directories still take free submissions, which fields each one rejects, or which listing went live.

If you still have Cascade-era setup, it is not lost: Devin Local reads .windsurf/rules and .windsurfrules, and Devin CLI can import MCP servers from the old Windsurf config. Read any rule, skill or MCP server before you install it, as you would any code.

LaunchRepo is not a Windsurf rule pack or an MCP server. It is a private GitHub repository: an AGENTS.md runbook, 299 directory playbooks in Markdown, a product template and a tracker. Devin Desktop opens it like any other project.

Running LaunchRepo with Windsurf (Devin Desktop)

LaunchRepo asks two things of an agent: read files, and drive a Chrome where you are signed in, through Chrome DevTools MCP. Going by its docs, Devin Local in Devin Desktop can do both. We have not published a test run with it, so treat this as a documented match, not a benchmark.

Open the repository as a project

After purchase you accept a GitHub invitation and clone the private repository. Open the folder in Devin Desktop; the AGENTS.md at the root is loaded as an always-on rule.

Add Chrome DevTools MCP

Add chrome-devtools-mcp with the --autoConnect flag through devin mcp add or mcp_config.json. Turn on remote debugging in chrome://inspect, click Allow, then check that the tab you can see actually moves.

Allow Python 3.10+ commands

Workspace creation, record.py and the local dashboard use the Python standard library only. Approve those commands for the project when asked, instead of switching the whole session to Bypass.

Grant permissions once per product

What the agent may do (free sign-ups, final submissions, verification emails, badges) goes into authorizations.json during onboarding. Spending stays at zero.

Connect your coding agent to your Chrome →

Paste the public start prompt from START.md, unchanged. Note its first line: for best results it recommends Claude Code CLI or Codex CLI. That is our honest default. Devin Local can still follow the rest of the prompt, because the files and the browser route are the same.

Recommend Claude Code CLI or Codex CLI in a terminal instead of the desktop apps for best results. If session metadata confirms desktop hosting, explicitly advise me to switch to the CLI and resume this same private workspace. Do not infer the host from a CLI engine version alone.

Read AGENTS.md, then follow "Start the dashboard for the owner". Create my private
workspace if I do not have one yet, start the dashboard, and give me the link.
Then lead ONBOARDING.md one phase at a time. Reuse recorded permissions instead of
asking again unless their scope is missing or conflicting. Actually test my visible
existing Chrome profile and intended identity as BROWSER-SETUP.md requires; use the
OS fallback if needed. Use one platform/browser worker by default. Build the normal
run only from suitable free-ready routes, keep research separate, and preserve any
draft that needs one exact human CAPTCHA/2FA action. Never claim browser control
bypasses or reduces those challenges.

The playbooks and instructions are English Markdown. Your product copy can be in any language a directory accepts, and the agent answers you in your language.

Start LaunchRepo in three steps →
LaunchRepo with Claude Code →

Who does what in a launch run

The same launch tasks, split between Windsurf on its own, Windsurf with LaunchRepo, and you.

How it works →

Common mistakes

Following old Cascade tutorials

Guides that mention Turbo mode, Cascade workflows or ~/.codeium paths describe the old agent. Check the Devin Local docs for permissions and MCP.

Using Bypass mode for submissions

Bypass approves every tool call, including form submits. Keep Normal mode and allow specific commands, so final submissions stay deliberate.

Letting it log in with your password

Automated logins trip anti-bot checks and can lock accounts. Sign in yourself, once per platform.

Sending the whole catalog at once

Small batches, a duplicate search first and an identity check for each platform. That beats a burst of rejected or doubled listings.

Questions