Voice Typing in Terminal

Why Voice Type in the Terminal?

The terminal is a developer's most powerful tool, but it's also where some of the most tedious typing happens. Git commit messages, long file paths, SSH connection strings, and interactive prompts all demand precise text input. While you wouldn't want to voice-type a complex piped command, there are dozens of terminal workflows where speaking is faster and more natural than typing.

Git commit messages are the most common example. A well-written commit message describes what changed and why, but the friction of typing often leads developers to write cryptic one-word messages like "fix" or "update." With Steno, you can hold your hotkey and say, "Refactor the authentication module to use JWT tokens instead of session cookies for better scalability" — and that entire descriptive message appears at your cursor in a second. Better commit messages lead to better code reviews, better debugging, and a more useful git history.

Beyond commit messages, voice typing in the terminal helps with any natural language task: writing README content in editors like nano or vim (insert mode), composing documentation, or even dictating search queries for tools like grep. This is part of how developers use voice-to-text daily to stay productive while reducing physical strain.

How to Set Up Steno for Terminal

Terminal Workflows You Can Voice Type

Dictate Git Commit Messages

This is the killer use case for voice typing in the terminal. Instead of git commit -m "fix", you can type git commit -m ", then hold your hotkey and say "Fix the off-by-one error in the pagination logic that caused the last page to show duplicate results." Release, type the closing quote, and hit Enter. Your commit history becomes infinitely more useful when commit messages are easy to write.

Compose Interactive Git Rebase Messages

When git opens an editor for rebase messages, merge commits, or tag annotations, you can switch to insert mode (if using vim) and voice type the message content. This works in any terminal-based text editor — nano, vim, emacs — as long as you're in a text-input mode where keystrokes produce characters.

Write Code Comments in Terminal Editors

If you edit files in nano or vim directly in the terminal, you can voice type comments, docstrings, and documentation inline. In VS Code, this works in the integrated terminal panel too. Enter insert mode, position your cursor after a comment prefix, hold the hotkey, and speak your explanation.

SSH Session Text Input

When connected to a remote server via SSH, Steno still works because it types at the local macOS level. Your spoken text is sent as keystrokes to the terminal, which forwards them through the SSH connection. This means you can voice type into remote editors, compose messages on remote systems, or enter responses to interactive prompts — all by voice.

Dictate Search Queries and File Paths

Long file paths, complex grep patterns, and search queries are tedious to type character by character. While you'll still need to type special characters like slashes and pipes, you can voice type the natural language parts of commands. For example, type grep -r ", hold your hotkey and say the search phrase, release, then type the rest of the command.

Pro Tips for Voice Typing in Terminal

Frequently Asked Questions