for Windsurf + Cascade users

Cascade writes the feature. A human walks it like your user will.

Cascade is fluent at multi-file changes. Multi-file changes mean multi-place regressions. TestMyVibes puts a verified human on your staging URL after every Cascade session β€” full video, severity-ranked bugs, fixes Cascade can apply next session.

QA my Windsurf build → See how it works

5 free credits · No card required · Same-day reports

Why human QA

Why Windsurf users need human QA in the loop

Cascade's superpower is touching ten files at once. That same superpower means the bug surface is ten files wide. Type checks won't catch what a human will.

Cascade refactors silently

A small Cascade prompt can rewrite a hook used in 12 places. Static analysis says fine. The runtime says broken. Humans walk the flows.

Flow tests, not assertion tests

Your unit tests run in milliseconds and prove nothing about UX. Humans run the actual flow your user runs and tell you where it breaks.

Mobile + accessibility regressions

Tab order, focus rings, screen reader labels β€” Cascade can quietly remove them when refactoring components. We catch it.

Apply fixes through Cascade itself

Drop our `.windsurfrules` file in your repo. Cascade reads our bug reports and patches the code in the next iteration.

Real human checkers testing Windsurf-built apps across desktop and mobile browsers
How to set it up

How to wire TestMyVibes into Windsurf

Add `.windsurfrules` to your repo root, set your API key, then ask Cascade to run the loop.

  1. Get your TestMyVibes API key

    Sign up (5 free credits, no card) and copy your key from Dashboard β†’ API Keys.

  2. Save .windsurfrules

    Download from /agent-skills/windsurf and commit it to your repo root. Set `TMV_API_KEY` in your shell env or a Windsurf secret.

  3. Run the loop after Cascade ships a feature

    Ask Cascade: "Run the TestMyVibes auto-test loop." Cascade deploys, calls our API, waits for the human report, applies the suggested fixes, redeploys, repeats.

  4. Review what your tester saw

    Screen recording, pass/fail checklist, severity-ranked bugs, AI health score. Same-day delivery during business hours.

.windsurfrules Download .windsurfrules 
# 1. Save the rule file
#    Download from https://testmyvibes.com/agent-skills/windsurf
#    Save this file as `.

# 2. Set your TestMyVibes API key as a secret named TMV_API_KEY.

# 3. Prompt the agent:
#    "Run the TestMyVibes auto-test loop."

# Under the hood, the agent calls:
curl -X POST https://testmyvibes.com/v1/replit/test \
  -H "Authorization: Bearer $TMV_API_KEY" \
  -H "Content-Type: application/json" \
  -H "X-Agent-Skill: windsurf" \
  -H "X-Agent-Iteration: 1" \
  -d '{ "url": "https://your-app.example.com",
        "feature": "what you just built" }'

Drop this in your repo root. Cascade reads it on demand.

Looking for the deeper API integration? See the Windsurf integration page →

Proof

What we catch on Windsurf-built apps

Cascade refactor broke focus order A hook rewrite removed the autoFocus on the first input. Keyboard users land in the wrong field.
Race in the new optimistic update Optimistic UI shows success then reverts when the API actually fails. User thinks the save worked.
Modal close button vanished on mobile Tailwind class change hid the close X under the safe-area inset on iOS.
Pagination off-by-one Page 2 skips a record. Cascade rewrote the offset math; tests didn't cover the edge.
  • Verified human checkers β€” every tester passes a background QA test before joining.
  • Real browsers on real devices (desktop, mobile, tablet) β€” no headless emulation.
  • Full screen recording of every session β€” replay exactly what your tester saw.
  • Average response time under 30 minutes during business hours.
Pricing

$1 per credit. 5 free to start.

1 credit = 2 minutes of human testing = $1.00. You only pay for time used. 5 free credits when you sign up β€” no card required. Compare that to one angry-user support ticket.

See full pricing →
FAQ

Windsurf + TestMyVibes FAQ

Will Cascade actually follow the rule file?

Yes. `.windsurfrules` is Cascade's standard config β€” it reads it like any project rule. Our file just adds the loop.

Can I cap credit spend?

Yes. The rule file ships with MAX_ITERATIONS and CREDIT_BUDGET. Both are enforced server-side too.

What if I'm not deploying anywhere yet?

We need a URL a tester can open. Use a tunnel (ngrok, cloudflared) or any free hosting β€” Vercel, Netlify, Render all work.

Can I trigger from CI as well?

Yes. Same API call works from any CI step. See /docs/ci.

Cascade ships fast. Catch what it ships broken.

5 free credits. No card. One rule file, full loop.

QA my Windsurf build →