Voice to Text for Fork

Fork makes Git visual, but you still have to type everything. Commit messages, branch names, stash descriptions, tag annotations. All that context you need to capture about your code changes. Blurt lets you speak it instead of typing it. Hold a button, describe your changes naturally, release. Text appears in Fork wherever your cursor is. Your commits get meaningful messages. Your branches have descriptive names. Your stashes become findable months later.

First 1,000 words free Works in all Fork text fields No configuration needed
Download Blurt Free

The Typing Problem

Commit messages become 'fix' or 'update' because typing is tedious

You just spent an hour fixing a subtle race condition. You know exactly what you changed and why. But typing out a proper commit message? That takes another minute. So you write 'fix bug' and move on. Six months later, you're reading git blame and have no idea what that commit was about. The context is lost forever.

Branch names are cryptic abbreviations

You need a branch name for a new feature. Something descriptive like 'feature/user-authentication-with-oauth-provider-selection' is ideal. But typing that out? You settle for 'feat/auth-oauth' and hope you'll remember what it means. Your team can't tell what anyone's working on from the branch list.

Stash descriptions are empty or useless

You need to switch branches urgently. You stash your work with no message because typing one takes too long. A week later, you have twelve stashes and no idea what's in any of them. You end up applying each one just to see what it contains. Half your stashes are probably duplicates of work you already finished.

Tag annotations get skipped entirely

You're releasing a new version. An annotated tag with release notes would be helpful for future reference. But typing out what changed in this release? You create a lightweight tag instead. Your release history is a list of version numbers with no context about what each one contained.

Interactive rebase messages become copy-paste jobs

You're cleaning up your commit history before merging. Each commit needs a better message. But rewriting five commit messages by hand? You copy the old message and add a word or two. The history stays messy because proper messages take too long to type.

How It Works

Blurt works everywhere in Fork. Commit message fields, branch name dialogs, stash descriptions, tag annotations. If you can type it, you can speak it.

1

Hold your hotkey

Press your chosen shortcut while your cursor is in any Fork text field. A small indicator shows Blurt is listening.

2

Describe your changes

Explain what you did and why. Talk like you're telling a colleague about your work. Blurt handles punctuation automatically.

3

Release and done

Text appears in Fork. Edit if needed, or commit directly. Your thoughts become documentation in seconds, not minutes.

Real Scenarios

Creating descriptive branch names quickly

You're starting work on a new feature. Hold and speak: 'feature slash add user profile image upload with crop and resize.' Blurt transcribes it, you adjust the format slightly. Branch created with a name that tells everyone exactly what you're building. No more guessing what 'feat/img-up' means.

Stash descriptions that make sense later

You need to switch contexts urgently. Hold and describe: 'Work in progress on the checkout flow refactor. Payment validation is done but shipping calculation still needs the tax integration.' Stash created with context. When you come back in a week, you know exactly where you left off and what still needs doing.

Annotated tags with release notes

Version 2.1.0 is ready. Hold and speak: 'Release 2.1.0 adds OAuth integration, fixes the cart persistence bug, and improves checkout performance by 40 percent. Breaking change: the auth endpoint now requires the client ID header.' Your release history becomes useful documentation instead of just version numbers.

Better messages during interactive rebase

You're squashing three commits into one. Hold and describe the combined changes: 'Implement user authentication with email verification. Includes the signup flow, email sending service, and verification token handling. Adds tests for all happy paths and common error cases.' One descriptive commit replaces three cryptic ones.

Quick notes in commit body for complex changes

Your commit touches fifteen files. The summary line isn't enough. Hold and add context: 'This refactors the entire caching layer. The old implementation had race conditions under high load. The new version uses read-write locks and includes automatic cache invalidation. See the README updates for migration steps.' Context preserved for code reviewers and future maintainers.

Documenting why you reverted a commit

Something broke in production and you're reverting. Hold and explain: 'Revert the payment gateway update. The new API version has a bug that causes duplicate charges on retry. Rolling back until the vendor fixes their timeout handling. Original commit was abc123.' Your git history tells the story of what went wrong.

Why Fork 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 Git terminology (commit, rebase, stash, merge) Often mishears technical vocabulary
Reliability Consistent accuracy in native app text fields Sometimes fails in third-party apps
Price $10/month or $99/year, free tier included Free but limited

Frequently Asked Questions

Does Blurt work in Fork's commit message dialog?
Yes. Blurt works anywhere you can type on macOS, including all Fork text fields. Commit messages, branch names, stash descriptions, tag annotations, search boxes. If you can put a cursor there, Blurt can insert text there.
Can Blurt handle Git terminology correctly?
Blurt handles Git terms well. Words like commit, push, pull, merge, rebase, stash, and branch transcribe accurately. Technical terms from your codebase like API, database, authentication, and common programming concepts also work reliably. For highly specialized terms unique to your project, you might need occasional edits.
Does Blurt work with other Git clients too?
Yes. Blurt works system-wide on macOS. Any Git GUI that runs on Mac works with Blurt, including Fork, Tower, Sourcetree, GitKraken, and GitHub Desktop. Even the Terminal works if you prefer command-line Git.
Can I dictate branch names with slashes?
You can say 'slash' and Blurt will transcribe it. So 'feature slash user authentication' becomes 'feature/user-authentication' with minor editing. Most users speak naturally and then quickly adjust formatting for branch naming conventions.
How much does Blurt cost?
Blurt offers a free tier with first 1,000 words free. For unlimited transcription, you can subscribe at $10 per month or $99 per year.
Does Blurt work on Windows or Linux?
Blurt is macOS only. We focused on creating the best possible Mac experience with native menu bar integration and system-level keyboard shortcuts. Windows and Linux versions are not currently available.

Start Typing Faster Today

Free to try — no credit card required

Download Blurt