Voice to Text for Developers
Your hands belong on the keyboard writing code, not typing Slack messages or PR descriptions. Blurt lets you speak your code comments, documentation, and quick replies while your fingers stay in position. Hold a button, say what you need, release. Text appears wherever your cursor is — in VS Code, GitHub, Slack, anywhere. No context switching. No flow interruption. Just talk and type.
The Typing Problem
Writing PR descriptions after finishing a feature
You just spent three hours in deep focus building something. Now you need to write a detailed PR description explaining what you did and why. Your brain is in code mode, not writing mode. The context switch feels like mental whiplash. You stare at the blank description field, trying to remember why you made that one decision an hour ago.
Slack messages during deep coding sessions
You're debugging a tricky issue when a teammate asks a quick question. You could type a reply, but moving your hands from keyboard to compose a message means losing your mental stack. By the time you're back, you've forgotten what variable you were tracing. That 30-second reply just cost you 10 minutes of regained context.
Documentation that everyone skips writing
You know you should write better code comments. You know the README needs updating. But after writing code all day, the thought of more typing makes you close the file and move on. The docs never get written. Six months later, you're the one trying to figure out what that function does.
Explaining your code in Linear or Jira tickets
The ticket says 'add caching' but now you need to document your implementation choices. You know exactly what to say — you could explain it in 30 seconds out loud — but typing it out takes 5 minutes you don't have before standup. So you write 'done' and move on. The context is lost forever.
Your wrists hurt by Thursday afternoon
Eight hours of typing code, plus Slack, plus documentation, plus commit messages. By mid-week, your wrists are aching and you're reaching for the ibuprofen again. The ergonomic keyboard helped, but you're still typing thousands of words daily. You're 28 and already worried about your hands lasting another 30 years in this career.
How It Works
Blurt works in every app developers use — VS Code, GitHub, Slack, Linear, Notion, your terminal. Anywhere you can put a cursor.
Hold your hotkey
Press your chosen shortcut. A small indicator shows Blurt is listening.
Talk naturally
Say your commit message, code comment, or Slack reply. Blurt handles punctuation.
Release and done
Text appears at your cursor. No copying, no pasting, no extra steps.
Real Scenarios
Writing commit messages without breaking flow
You've staged your changes and need a commit message. Instead of switching mental gears to writing mode, hold your hotkey and say 'Fix race condition in user authentication by adding mutex lock to session handler.' Done in 4 seconds, not 40. Your hands never left the keyboard position. No mental context lost.
Explaining code in PR descriptions
The PR is ready but needs context for reviewers. Hold the button and talk through your changes naturally: 'This refactors the payment module to use the strategy pattern. Each payment provider is now a separate class, making it simpler to add new providers without touching existing code.' Three paragraphs spoken in 20 seconds instead of 3 minutes of typing.
Quick Slack replies during debugging
A teammate asks 'Is the API down?' while you're deep in server logs. Hold, say 'Investigating now, looks like a database connection timeout, will update in 10 minutes', release. Back to debugging in 3 seconds flat. Your mental context survives. No typing, no flow destruction.
Adding code comments without stopping
You just wrote a clever workaround that future-you will definitely forget. Cursor above the function, hold button, say 'This handles the edge case where users have multiple active sessions. We invalidate the oldest session to prevent token conflicts.' Comment done in 5 seconds. Future-you will thank present-you. Keep coding.
Updating Linear tickets with implementation notes
The ticket needs your technical notes before you forget the implementation details. Hold and speak: 'Implemented using Redis sorted sets for O log N lookups. Added TTL of 24 hours to prevent stale data. See PR 847 for the full implementation.' Ticket updated while the context is still fresh in your mind. Your team actually knows what you built.
Writing docs while the code is fresh
You just finished a feature and the API needs documenting before you forget the edge cases. Instead of typing, talk through how it works: 'The get user endpoint accepts an optional include parameter. Pass include equals posts to get the user with their recent posts. Rate limited to 100 requests per minute.' README updated in real-time. Documentation actually gets written for once.
Responding in GitHub code review
Someone left a comment on your PR asking why you chose this approach. Hold button, explain your reasoning out loud: 'Good question. I considered using a factory here but the additional abstraction adds complexity without clear benefit. The switch statement is more readable for our three current cases.' Reply posted without typing a single word. Code review stays conversational, not tedious.
Why developers choose Blurt over built-in dictation
| Blurt | macOS Dictation | |
|---|---|---|
| Activation | Single hotkey, instant start | Click microphone icon or 'Hey Siri' |
| Speed | Text appears in under 500ms | 2-3 second delay before transcription |
| Reliability | Consistent accuracy across sessions | Often fails silently or mishears |
| Code context | Handles technical terms well | Struggles with function names and jargon |
Frequently Asked Questions
Start Typing Faster Today
Free to try — no credit card required
Download Blurt