Team hubs
QA by the tool your team writes with
What each tool changes in a codebase, read from its docs with dates; the failure patterns most associated; how the checklist adapts; which plan fits.
Anysphere
QA for teams writing with Cursor
Cursor's Agent edits files and runs commands on the developer's machine. The code it produces needs the same release checks as any other; the run modes decide how much of that has to happen in CI instead of the editor.
5 verified defaults
GitHub
QA for teams writing with GitHub Copilot
Copilot completes code in the editor and, as a cloud agent, opens pull requests from its own branches in a GitHub Actions environment. The platform enforces a second reviewer; the checklist is what that reviewer runs.
5 verified defaults
Anthropic
QA for teams writing with Claude Code
Claude Code runs in the terminal with a permission system: read-only by default, approval for edits and commands, and settings files that enforce deny rules. What it cannot enforce is whether the release passes.
5 verified defaults
Cognition
QA for teams writing with Windsurf
Windsurf's Cascade agent edits the codebase and runs commands under auto-execution levels from manual approval to Turbo mode. The docs now live under Devin Desktop; the release checks are the same.
5 verified defaults
Lovable
From a Lovable app to production
Lovable generates the front end and connects it to a Supabase project you own. Its publish scan lints row-level security policies. What it does not do is run the two-user test, check payments, or watch the release after the first one.
5 verified defaults
StackBlitz
From a Bolt app to production
Bolt builds the app, hosts it or publishes to Netlify, and offers a security audit from the Publish menu that covers secrets, access control, input validation and authentication. It runs when you run it.
5 verified defaults