
Windsurf just shipped Voice Mode for Cascade

As Cascade has gotten better, we noticed that the tasks users are giving it have gotten more complex. Instead of just asking Cascade to make simple edits, users are relying on Cascade to build out entire features, perform large refactors, and implement PRs end to end. More complex tasks mean longer prompts with more information which can often be laborious to type out. In this wave, we’re bringing voice support to Cascade. This means that users can just speak to Cascade rather than having to type things out (though it doesn’t talk back…yet)
Replies
Product Hunt
This compelled me to upgrade and try it out. Here's my first thoughts.
It's slower than using @Wispr Flow , and I found it to be a little buggy (not toggling with hotkeys consistently.)
But I personally only use Wispr Flow for vibe coding.
It's good enough that I'd be happy using it 100% of the time, but I don't see a reason to switch from my current workflow.
Product Hunt
Pretty cool! If I'm being honest though, I've already been using @Aqua Voice for this and I don't see myself switching over. I definitely see the usefulness for someone who's not already using something like that or @Wispr Flow.
It is funny how different my commands are voiced vs written. Curious to play with more voice driven direction. I have been slow to do this: too much time in shared environments. I would love to hear how people use voice in dev environments.
It's good to see Cascade tackling the ‘prompt tax’ issue. I've noticed that sometimes my prompts actually evolve into mini-specs, so it would be interesting to try switching from text to voice. There are some concerns though.
Quite impressed by the first tests I'm doing on it.
This has been one of my initial requests to @Windsurf (https://www.producthunt.com/products/windsurf/reviews?review=1236033) . Kudos to them for finally deploying it.
Still slower than @Wispr Flow and with some limitations in terms of the length. If they solve it, this might be the end of my paid plan with Wispr, because I'm mostly using it with AI agent-powered IDEs.
In my opinion, killer function for me and all of the vibe coders/marketeers out there