If you turn on fast dictation, it will sometimes translate the language in which you dictate to English, which, in some cases, is not intended. Very often when I dictate something in another language than English, I want it to be transcribed in that language.
The developers know about this and are working for a solution. In general, I would say every bug or feature request that you share with them is acted on very diligently and with speed.
Willow Voice
@allan_guoΒ Where can I find a full list of supported IDEs for file/variable etc. recognition? Are Jetbrains IDEs supported as well?
@allan_guoΒ βYou take shortcuts when you typeβ is such a real observation.
Prompt quality is often limited by effort, not intelligence. Speaking naturally leading to richer context makes a lot of sense β especially for complex workflows.
Curious β how does Willow handle background noise or rapid context switching during coding sessions?
Congrats on the launch π
If it truly reduces correction cycles, thatβs where the value is. Speed gains only matter if accuracy stays high.
The file auto-tagging is the killer feature here. Having to manually type @filename in Cursor prompts always felt like unnecessary friction β if Willow can recognize my project context and handle that automatically, that's a legit workflow upgrade.
Product Hunt
The developer-focused features look promising. I use Claude Code in a terminal environment rather than a GUI-based IDE. Does Willow work with terminal-based coding workflows, or is the file/variable recognition specifically optimized for visual IDEs like Cursor?
Honestly, typing huge prompts is exhausting. Being able to just talk and have it understand your files and code feels like a much more natural way to work.