Before anything else — before the long test plans and the careful edge cases — there's a smaller question worth asking: is the thing alive? Smoke testing is the lightest possible check. Can I log in? Does the main page load? Does the central thing this product is supposed to do still do it? It's not glamorous. It catches none of the interesting bugs. But it catches the catastrophic ones — the ones where the build went out broken, and no one noticed for an hour. The first breath of a release isn't a deep test. It's a held one, briefly let out when nothing exploded.

Wispr Flow lets you dictate prompts, acceptance criteria, and bug reproductions inside Cursor or Warp — with automatic file name and variable recognition. Say user_id, get user_id. Say useEffect, get useEffect.

Paste directly into GitHub, Jira, or Linear. Give coding agents the full context they need without typing a novel.

89% of messages sent with zero edits. Millions of developers use Flow daily, including teams at OpenAI, Vercel, and Clay. Free on Mac, Windows, and iPhone.

Start flowing free

Last month, our team pushed a config change late on a Friday — a small thing, no UI impact, "absolutely nothing user-facing could break." Habit pulled me to the login page anyway. The page loaded; the login button didn't. The change had touched a shared dependency three layers down, and in production, it had quietly broken the auth flow. Total smoke test time: forty seconds. Total revert time: two minutes. If we'd waited for Monday morning, three thousand customers would have hit a broken login first.