Voice to Text for VS Code

Your hands are on the keyboard writing code. But now you need to write a commit message, a code comment, or update the README. Switching mental gears from code to prose is jarring. Blurt lets you speak your documentation, comments, and commit messages directly into VS Code. Hold a button, say what you need, release. Text appears at your cursor. Your hands stay in position. Your flow stays intact. Works everywhere in VS Code — code files, terminal, source control, settings, anywhere you can type.

First 1,000 words free Works in all VS Code contexts macOS only
Download Blurt Free

The Typing Problem

Commit messages interrupt your coding flow

You just finished a focused coding session. Now git is asking for a commit message. Your brain is still in code mode, but you need to switch to writing mode. You stare at the input field, trying to summarize what you just spent two hours building. The mental context switch costs more than the actual typing. You end up writing 'fix bug' just to move on.

Code comments you know you should write but never do

That clever workaround deserves an explanation. Future you will have no idea why this code exists. But after writing the implementation, typing out a paragraph of explanation feels exhausting. So you skip it. Six months later, you're debugging your own code wondering what past-you was thinking. The comment never gets written because typing it requires too much mental energy.

README updates that keep getting postponed

The API changed. The README is now lying to anyone who reads it. You know exactly what to write — you could explain the changes in 30 seconds out loud. But opening the file and typing it out will take 10 minutes. There's a feature to ship. The docs can wait. The docs always wait. The README stays wrong for months.

Terminal commands that need documentation

You just figured out the exact command sequence to fix that deployment issue. It should go in the runbook. But you're in the terminal, in the zone, and switching to write docs means losing momentum. So you move on. Next time the issue happens, you'll figure it out again. And again. The tribal knowledge stays in your head.

Search queries typed letter by letter

You need to find that function across the codebase. You know what you're looking for. But typing 'handleUserAuthenticationWithRefreshToken' character by character is tedious. You could just say it. Instead you type 'handleUser' and hope autocomplete saves you. Search should be as fast as thinking. It's not.

How It Works

Blurt works in every context within VS Code — your code files, the integrated terminal, source control panel, settings, extensions, everywhere you can place a cursor.

1

Hold your hotkey

Press your chosen shortcut anywhere in VS Code. A small indicator shows Blurt is listening.

2

Talk naturally

Say your commit message, code comment, or search query. Blurt handles punctuation and capitalization.

3

Release and done

Text appears at your cursor in VS Code. No extra steps. Keep coding.

Real Scenarios

Dictating code comments without breaking flow

You just wrote a function that handles a tricky edge case. Cursor above the function, hold button: 'This handles the race condition where multiple sessions attempt to refresh the same token simultaneously. We use a mutex to ensure only one refresh happens at a time.' Comment written in 8 seconds. The explanation exists. Future developers will understand. Keep coding.

Speaking documentation while the code is fresh

You finished implementing the new endpoint. The README needs updating. Instead of postponing it, hold the button: 'The new slash API slash users slash refresh endpoint accepts a POST request with the refresh token in the body. Returns a new access token and refresh token pair. Rate limited to 10 requests per minute per user.' Documentation done before you forget the details.

Search queries at the speed of thought

You need to find where that authentication helper is defined. Hold button, say 'validate user session token', release. The search box fills instantly. No character-by-character typing. No hoping autocomplete guesses right. Search as fast as you can think of what you're looking for.

Terminal commands and notes

You're in VS Code's integrated terminal documenting a deployment fix. Hold button: 'Run this command to clear the Redis cache when users report stale session data. Safe to run in production. Takes about 30 seconds to complete.' The runbook gets updated while you're still in context. Tribal knowledge becomes shared knowledge.

Inline documentation during debugging

You just spent an hour figuring out why this code behaves unexpectedly. The answer should be documented. Hold button above the confusing line: 'This looks wrong but is intentional. The API returns timestamps in seconds, not milliseconds, despite the documentation claiming otherwise. See issue 2847.' Future debuggers will thank you. The context is captured before you forget it.

Settings and configuration notes

You're adjusting VS Code settings and want to remember why. Open settings.json, hold button: 'Disable format on save for Python files because the project uses a custom formatter in the CI pipeline. See team Confluence page for details.' The reason behind the setting is documented. You won't wonder why it's disabled in six months.

Why VS Code users choose Blurt over built-in dictation

Blurt macOS Dictation
Activation Single hotkey, instant start Double-tap Fn or menu bar click
Speed Text appears in under 500ms 2-3 second delay before transcription starts
Technical vocabulary Handles programming terms accurately Often misinterprets function names and jargon
Reliability Works consistently in all VS Code contexts Sometimes fails silently in terminal or panels
Price $10/month or $99/year Free (built into macOS)
Free tier First 1,000 words free Unlimited but unreliable

Frequently Asked Questions

Does Blurt work in all parts of VS Code?
Yes. Blurt works anywhere you can place a cursor in VS Code — code files, the integrated terminal, source control commit messages, search boxes, settings, extension panels, everything. If you can type there, you can dictate there.
Can Blurt handle programming terms and function names?
Blurt handles programming vocabulary well. Terms like 'async', 'middleware', 'refactor', and common function patterns transcribe accurately. For highly specialized terms unique to your codebase, occasional edits may be needed. Most developers find the accuracy sufficient for comments, docs, and commit messages.
Will Blurt conflict with my VS Code keyboard shortcuts?
No. You choose your own hotkey during Blurt setup. Pick any key combination that doesn't conflict with your existing VS Code bindings. Most developers use a modifier combination they're not already using, like Ctrl+Shift+Space or a function key.
Is Blurt good for writing actual code syntax?
Blurt is best for prose — comments, documentation, commit messages, notes. Dictating code syntax like 'function parenthesis argument colon string close parenthesis' is awkward and slower than typing. Use Blurt for the English around your code, not the code itself.
Does Blurt work while I'm on a video call?
Yes. Blurt captures audio through your microphone independently of Zoom, Meet, or any call software. You can be muted on your call and still dictate into VS Code. Just don't unmute while speaking to Blurt, or your teammates will hear your commit message.
What if I use VS Code on Windows or Linux?
Blurt is macOS only right now. If you're on Windows or Linux, Blurt won't work for you yet. We're focused on doing one platform really well before expanding.

Start Typing Faster Today

Free to try — no credit card required

Download Blurt