Voice to Text for GitHub
GitHub is where your code lives, but writing about that code takes forever. PR descriptions, issue responses, code review comments, README updates, discussion replies. All that prose you need to write around your code. Blurt lets you speak it instead of typing it. Hold a button, explain your changes naturally, release. Text appears in GitHub wherever your cursor is. Your PRs get the context they deserve. Your code reviews become actually helpful. Your issues get triaged in seconds, not minutes.
The Typing Problem
PR descriptions that are actually useful take forever to write
You just spent three hours building a feature. Now you need to explain what you did, why you did it, what to test, and what reviewers should pay attention to. You could explain it verbally in 30 seconds, but typing it takes 10 minutes. So you write 'Fixed bug' and move on. Your reviewers have no context. The review takes twice as long.
Code review comments feel like a chore
You spotted an issue in someone's PR. You know exactly what the problem is and how to fix it. But explaining it clearly in writing takes time. You're tempted to just write 'refactor this' but you know that's not helpful. So either you spend 5 minutes crafting a thoughtful comment, or you leave something cryptic. Neither feels right.
Issue triage becomes a backlog nightmare
Bug reports are piling up. Each one needs a response: acknowledgment, questions for clarification, status updates. Writing 'Thanks for reporting, can you provide reproduction steps?' fifty times a day is mind-numbing. You fall behind. Users feel ignored. The issue backlog becomes a source of guilt.
Documentation never gets written
The README is outdated. The wiki is a graveyard. You know you should document that API, explain those setup steps, update those contribution guidelines. But after a day of coding, more typing is the last thing you want. So the docs stay stale. New contributors struggle. Questions get repeated. Technical debt compounds.
GitHub Discussions feel like running a forum
Your open source project has active discussions. Users ask questions, propose features, report issues. Each thread deserves a thoughtful response. But you have code to write and a day job. Responding to discussions becomes a second job. Community engagement suffers because typing is slow and your time is limited.
How It Works
Blurt works everywhere in GitHub. PR descriptions, code review comments, issue responses, wiki edits, README updates, discussion replies. If you can type it, you can speak it.
Hold your hotkey
Press your chosen shortcut while your cursor is in any GitHub text field. A small indicator shows Blurt is listening.
Explain naturally
Describe your changes, explain your reasoning, ask clarifying questions. Talk like you're explaining to a colleague. Blurt handles punctuation automatically.
Release and done
Text appears in GitHub. Edit if needed, or submit directly. Your thoughts become documentation in seconds, not minutes.
Real Scenarios
Writing detailed PR descriptions that reviewers actually read
Your PR is ready but needs context. Hold the button and talk through it: 'This refactors the authentication module to use JWT tokens instead of session cookies. The main changes are in the auth middleware and the user controller. I added a new token refresh endpoint. Testing notes: you will need to clear your browser cookies before testing. The migration runs automatically.' A description that would take 5 minutes to type takes 30 seconds to speak. Your reviewers know exactly what they're looking at.
Thoughtful code review comments without the time sink
You spotted a potential memory leak in a PR. Hold and explain: 'This looks like it might leak memory because the event listener is never removed when the component unmounts. Consider adding a cleanup function in the useEffect return, or use the AbortController pattern we have in the utils folder.' Helpful, constructive feedback in 10 seconds. You gave context, explained the problem, and suggested a solution. That's a useful code review comment.
Triaging issues at speed
A user reported a bug. Hold and respond: 'Thanks for reporting this. I can reproduce the issue on my end. This looks related to the caching changes we made in version 2.3. I am adding it to our sprint backlog. As a workaround, you can clear your local cache by running npm run clear-cache. We will have a fix in the next patch release.' Issue triaged, user informed, workaround provided. What would take 3 minutes of typing takes 15 seconds.
Updating README documentation while you still remember how it works
You just finished implementing a new feature and the README needs updating. Instead of putting it off, hold the button and speak: 'To use the new caching feature, add the cache option to your config object. Supported values are memory, redis, or none. Memory is the default. For Redis, you will also need to set the REDIS_URL environment variable.' Documentation written while the implementation is fresh. No more outdated READMEs.
Responding to GitHub Discussions
Someone asked about your project's architecture in Discussions. Hold and explain: 'Great question. We use a modular architecture where each feature is a self-contained module with its own routes, controllers, and services. This makes it easier to add new features without touching existing code. Check out the modules folder structure in the repo for examples. Happy to answer follow-up questions.' Community engagement without the typing fatigue.
Wiki pages that actually get written
The wiki needs a setup guide. Nobody wants to write it. But speaking it? That's easy. Hold and talk through the process: 'First, clone the repository. Then copy the example environment file to dot env. You will need to set your database URL and API keys. Run npm install to install dependencies, then npm run migrate to set up the database. Finally, npm run dev starts the development server on port 3000.' Wiki page done. No more 'TODO: write setup guide' sitting in your backlog for months.
Explaining complex code changes in commit descriptions
Your commit touches fifteen files and GitHub wants a description. Hold and summarize: 'This commit introduces the new rate limiting system. Each endpoint can now specify its own rate limit configuration. The default is 100 requests per minute. Rate limit headers are included in all responses. Redis is used for distributed counting across server instances.' Context preserved for future debugging sessions.
Why GitHub users choose Blurt over built-in dictation
| Blurt | macOS Dictation | |
|---|---|---|
| Activation | Single hotkey, instant start | Click microphone or double-tap function key |
| Speed | Text appears in under 500ms | 2-3 second delay before transcription |
| Technical terms | Handles GitHub jargon well (PR, merge, rebase) | Often mishears technical vocabulary |
| Reliability | Consistent accuracy in browser text fields | Sometimes fails in web apps |
| Price | $10/month or $99/year, free tier included | Free but limited |
Frequently Asked Questions
Start Typing Faster Today
Free to try — no credit card required
Download Blurt