Use cases / Developers

Write the prose around your code by talking

Code is typed. Everything around it — commit messages, PR descriptions, review comments, issue updates, prompts — is just writing, and talking is faster.

Workflows

Examples of what you'd say and what ends up in the text field.

Commit messages

Hold the key in your terminal or Git client and describe what changed.

Said

“Fix the race condition in the upload queue by locking before we read the retry count”

Typed

Fix the race condition in the upload queue by locking before we read the retry count

Pull request descriptions

Explain the why while it's still in your head, then edit.

Said

“This replaces the polling loop with a webhook. Polling was costing us about two hundred requests a minute and still missed updates.”

Typed

This replaces the polling loop with a webhook. Polling was costing us about 200 requests a minute and still missed updates.

Prompts for coding assistants

Long, specific prompts get better results and are tedious to type.

Said

“Refactor the settings module so each section is its own file, keep the public API the same, and add tests for the migration code”

Typed

Refactor the settings module so each section is its own file, keep the public API the same, and add tests for the migration code.

Review comments

Leave the thoughtful comment instead of the short one.

Said

“um I think this works but we should probably handle the empty list case, uh, otherwise the reduce throws”

Typed with AI cleanup

I think this works, but we should probably handle the empty list case. Otherwise the reduce throws.

Useful features

Custom vocabulary

Add library names, service names and acronyms so they come out right.

Works in any app

Terminal, IDE, browser, chat. If there's a cursor, it types there.

Local by default

Your audio stays on your machine, which matters when you're talking about unreleased code.

Try it on your own computer

Free to start. macOS, Windows and Linux.