Voice to Text for Terminal
The terminal is where you do your real work. But typing long commands, SSH configs, and Git commit messages slows you down. Blurt lets you speak directly into your terminal. Hold a button, say your command or message, release. Text appears at the cursor. Works in iTerm2, Terminal.app, Hyper, Warp, or any terminal emulator on macOS. Your hands stay on the keyboard for navigation. Your voice handles the text.
The Typing Problem
Long commands with multiple flags
You know exactly what you need: a find command with path, name pattern, exec, and xargs piped to grep. Typing it out takes 30 seconds of careful keystroke-by-keystroke accuracy. One typo and you're hitting the up arrow, navigating with Ctrl+A and Ctrl+E, fixing it character by character. You could say it in 5 seconds.
Git commit messages worth reading
You know you should write meaningful commit messages. 'Fix bug' is useless six months later. But typing out 'Refactor authentication middleware to handle expired tokens gracefully and add retry logic for transient failures' takes forever when you're mid-flow. So you write 'fix auth' and move on. Your git log becomes unreadable history.
SSH config files and scripts with comments
You're setting up a new server or writing a deploy script. Comments matter for future you and your teammates. But explaining what each block does means switching from code brain to prose brain, and typing paragraphs of documentation is tedious. The comments never get written. Six months later, nobody remembers why that flag is there.
Complex file operations you need to get right
Moving, copying, or deleting files with specific patterns across directories. The command needs to be precise. You're thinking through the logic out loud anyway: 'find all the log files older than 30 days and compress them.' Why not just say that and have it appear as your starting point?
Documentation in READMEs while you work
You're in the terminal, testing commands, and you should be documenting them. But opening another app breaks your flow. If you could just speak 'Run this command to initialize the database with the seed data' directly into your terminal-based editor, the docs would actually get written.
How It Works
Blurt works anywhere you can type on macOS, including every terminal app. iTerm2, Terminal.app, Warp, Hyper, Alacritty, Kitty. If you can put a cursor there, Blurt can insert text.
Hold your hotkey
Press your chosen shortcut. A small indicator shows Blurt is listening. Your terminal stays focused.
Speak your command or message
Say your Git commit message, script comment, or command description. Speak naturally.
Release and execute
Text appears at your cursor. Hit enter to run the command or keep editing. No extra steps.
Real Scenarios
Git commit messages that actually explain things
You've staged your changes and your cursor is waiting at the commit message prompt. Hold your hotkey and speak: 'Add rate limiting to API endpoints with configurable thresholds per user tier and automatic backoff on 429 responses.' Done in 4 seconds. Your commit history becomes readable. Future you will understand what past you was thinking.
Long commands with complex arguments
You need a find command with multiple conditions. Instead of typing each flag carefully, speak the structure: 'find dot slash src dash name asterisk dot ts dash type f dash mtime plus 30 pipe xargs grep dash l TODO.' Fix up the syntax, hit enter. Starting point created in seconds, not minutes.
Script comments while you build
You're writing a bash script and should explain what the next block does. Cursor in place, hold and speak: 'This section handles cleanup of temporary files created during the build process, preserving only the final artifacts.' Comment written before you forget why it matters.
SSH config documentation
You're setting up SSH configs for multiple servers. Each host entry needs context. Speak: 'Production database server, read replica, use for analytics queries only.' Comments appear inline. When you come back in three months, you'll know which server is which.
Quick notes in terminal-based editors
You're in vim or nano editing a config file. You need to add a comment explaining a setting. Speak directly: 'Increase max connections to handle peak traffic during product launches.' The comment appears. No mode switching or special commands.
Command history documentation
You just ran a complex sequence of commands to fix an issue. Before you forget, open a notes file and dictate: 'To resolve the port conflict, first stop the running process, update the config, then restart with the new port binding.' Future troubleshooting documented in real-time.
README updates from the terminal
You're testing a new feature and need to update the README with instructions. Pop open the file and speak: 'Run npm run migrate to apply database changes. This requires the DATABASE URL environment variable to be set.' Documentation written while the context is fresh.
Why developers choose Blurt for terminal work
| Blurt | macOS Dictation | |
|---|---|---|
| Terminal compatibility | Works in all terminal apps | Often fails in terminal contexts |
| Activation | Single hotkey, instant start | Double-tap Fn or click microphone |
| Technical vocabulary | Handles git, ssh, grep, and commands | Struggles with technical terms |
| Speed | Text appears in under 500ms | 2-3 second delay typical |
Frequently Asked Questions
Start Typing Faster Today
Free to try — no credit card required
Download Blurt