noan@laptop — claude — 120×32
─ Claude Code v2.0.0 ─
Welcome back Noan!
Opus 5 · Max 20x
~/Dev/yappr
listening

For people who build with AI

Talk to your AI
like a teammate.

Yappr turns what you mean into the prompt your agent needs.

Download for MacmacOSSend it to your Mac

You ramble. Your agent gets a brief.

you said

“onboarding is broken for google signups, um, they hit the dashboard before the workspace exists so it 404s, can you fix it and add a test, don’t touch email signup”

noan@laptop — claude — 120×32
─ Claude Code v2.0.0 ─
Welcome back Noan!
Opus 5 · Max 20x
~/Dev/yappr
## Goal
Fix the broken onboarding redirect for Google signups.
## Context
Users reach `/dashboard` before the workspace record exists, so it 404s.
## Tasks
1. Wait for workspace creation before redirect.
2. Add a regression test.
## Constraints
- Leave the email signup path untouched.

14 days of Pro to start, then free with every feature. No card.

Download for MacSend it to your Mac

Others write what you said.
Yappr writes what you meant.

Same 4 seconds of talking
Other dictation tools
noan@laptop — claude — 80×24

>onboarding is broken for google signups um they hit the dashboard before the workspace exists so it 404s can you fix it and add a test dont touch email signup

Which signup flow do you mean — Google OAuth, or the magic link?

>the google one

Should I change the existing tests, or add a new one?

>no just add one

Got it. Which file handles the redirect?

>
? for shortcuts

3 rounds of questions before it starts

noan@laptop — claude — 80×24
>## GoalFix the Google signup redirect.## Context/dashboard 404s before the workspace exists.## Tasks1. Wait for the workspace before redirecting.2. Add a regression test.## Constraints- Don't touch email signup.

Read(src/auth/redirect.ts)

Read 84 lines

Update(src/auth/redirect.ts)

Updated with 6 additions and 1 removal

Write(src/auth/redirect.test.ts)

Wrote 32 lines

>
? for shortcuts

Starts on the first try

Yappr vs Wispr Flow, side by side →

Not just prompts.

YYappr
  • 📋Roadmap
  • 📝Decode notes
  • 🗂Archive
Decode notesShare
📝

Decode notes

StatusIn progress
Tagsaudioperf

Where the audio path stands.

The worker is written in TypeScript and decodes on the main thread, so the interface stalls.

The worker is written in C and decodes off the main thread, so the interface stays responsive.

Next: measure the first-word latency again.

Next steps
Profile the worker
Measure first-word latency again
Write up the numbers
“make that C, and decode off the main thread”

Fix a draft by voice

New message
ToSam Ortiz
Subject

Hi Sam,

Quick heads-up: the beta is slipping by about a week.

Does Thursday work to catch up?

Thanks,

Send
“email sam, the beta slips a week — ask if thursday works”

The whole email from one line

Dana M.
Today 2:12 PMstill on for friday at 12?running a bit late, start without meDelivered
iMessage
# build 4

Dana2:11 PM
Standup in 5 — you joining?

You2:14 PM
Running a few minutes late — start without me.

Message #buildAa
Thursday sync Inbox
Dana Marshto me
Dana Marsh

Hi Dana,

I’m running a few minutes late — please start without me.

Thanks,

Send

The right tone for each app

hearing youyour dictionary
anthropicAnthropic
grokGroq
app dot tsxapp.tsx
sam o'konkwoSam Okonkwo

Your stack. Your people. Spelled right.

Is it free?
Every feature and 50 polished dictations a week, with no card — Pro only lifts that weekly cap, at $15 a month for the first 500 people and $20 after.
What happens after I join?
14 days of Pro, then Free — no card, and dictation never stops. Each friend who joins with your code and dictates 1,000 words adds a month; they get 14 extra days.
Will it run on my machine?
macOS only today; Windows and Linux are not supported yet, and the comparison post covers which tools do.

Go on then.
Start yapping.

14 days of Pro to start, then every feature and 50 polished dictations a week, free — no card. $15/mo for no weekly cap: founding price, first 500.

Download for MacmacOSSend it to your Mac

One key. That is the whole interface.

  • HoldHold to talkLet go, and it pastes where your cursor is.
  • TapHands-freeTap once and just yap. Tap again when you're done.
  • Double-tapPaste it againYour last dictation, wherever you are now.

Hold Control. Say anything.

Try it nowControl
Target

Try saying: “the retry logic is wrong, it retries on 400s too, should only be 429 and 5xx, and cap it at three”

noan@laptop — claude — 120×32
─ Claude Code v2.0.0 ─
Welcome back Noan!
Opus 5 · Max 20x
~/Dev/yappr
  • Taptoggle recording
  • Holdpush to talk
  • Double-tapre-paste the last one

wherever you type

Free is actually useful.

Every feature on both plans. Pro is for when 50 a week isn’t enough — every new account starts with 14 days of it, and each friend who dictates 1,000 words adds a month.

Free

$0forever

not a trial — no clock, no card

  • Unlimited dictation, free forever
  • 50 polished dictations a week
  • Every feature, nothing held back
  • Tap, hold or double-tap — your call
Download for MacSend it to your Mac

Pro

Founding · first 500
Standard price $20$15per month

or $150 a year

  • Everything in Free
  • No weekly cap on polished dictations

The 14-day trial needs no card and ends on Free. A paid Pro plan renews automatically — monthly, or yearly on the annual plan — until you cancel; cancel any time and it runs to the end of the period you paid for. Billing terms

Download for MacSend it to your Mac

Trial

14 days of Pro, no card

Cancel

One click

Billing

Monthly; yearly for the founding 500

Data

See the policy

Worth answering.

The questions we get asked the most.

What is Yappr?

Yappr is a voice dictation app for macOS, built for people who build with AI. You hold a key and say what you want the way you would say it to a colleague; Yappr turns what you meant into the prompt your agent needs — the goal, the context, the tasks and the constraints you spoke, sorted and pasted at your cursor in Claude Code, Cursor or the terminal. The same sentence lands as an ordinary message in Slack, iMessage or email. It can also rewrite selected text from a spoken instruction, write a whole email from one spoken sentence, and spell the names and jargon in your own dictionary right, in every app.

How do I dictate a prompt into Claude Code or Cursor?

Click into the prompt box, hold Control, and say what you want the way you would explain it to a colleague — out of order, with the ums. Let go. Yappr pastes the result at your cursor, sorted into a goal, the context and the tasks, with every file name and "don't touch that" you said still in it. Changed your mind halfway? Press Escape and nothing is pasted. There is nothing to install inside the editor: it works in the terminal, Claude Code, Cursor, VS Code and any other app you can type in.

Does it work in Claude Code, Cursor, and the terminal?

That's what it's built for. Yappr sees which app you're in and whether an AI agent is listening — Claude Code in your terminal, or the agent inside Cursor and VS Code — and a real request arrives as a brief. A quick "please fix this" is left as you said it, and a plain shell with no agent gets your words, not a brief. Spoken file names come out as file names — "app dot tsx" becomes app.tsx. Tell Yappr about your project and it uses that to understand you — which thing "the notch" is, how your names are spelled — without pasting it into the prompt.

My editor already dictates. Why pay for this?

Because writing down what you said is a different job from working out what you meant. Claude Code, VS Code and Cursor all added dictation in 2026, all free, all good — and none of them restructures anything. Each one also stops at the edge of the window it ships in, so the pull request, the Slack reply and the email are back to typing. Yappr decides instead: the same ramble lands as a brief in your agent, a sentence in Slack and a proper email in Gmail — no second hotkey, no wake phrase to remember. If you only ever dictate short prompts into one tool, the built-in one is genuinely enough.

Does it change or cut what I said?

No. It reorganizes, and it never summarizes. Your ramble comes out under Goal, Context, Constraints and Tasks — plus Verify, when you said how you'd check the work — with every file name, error code, condition and "don't touch X" you spoke still in there. If you said eight things, eight things land. Rather keep your own words in paragraphs, without the headings? That is one setting. We call this prompt shaping.

Can it write the whole thing, not just tidy it up?

Yes, and it's the one place Yappr writes rather than edits. Say "email Sam that the beta slips a week and ask if Thursday works" and you get the email, not your sentence with the ums taken out. Same for a prompt: describe what you want built and it comes back as the brief. It won't invent facts you didn't give it — a one-line brief makes a short email, which is correct rather than unfinished.

What happens to what I say?

The audio is turned into text on your own Mac. That text is then sent to a third-party service to be cleaned up and shaped, because that part does not run well locally yet. We do not keep it — unless you choose to send us a bug report, which you read in full first and which is deleted after 90 days — and we are not going to make promises about a company we do not control — what we send, and what we know about how it is handled, is set out in the privacy policy.

Can it see my screen?

No, and it never takes screenshots. It reads a few labels instead: which app is in front and the title of its window — in a browser, the tab's address too — what kind of box your cursor is in, and anything you have highlighted. That is how the same sentence comes out differently in iMessage and in a pull request. The title and the address stay on your Mac; what goes out with your words is the app's name, like "Slack" or "Cursor", and the privacy policy lists the rest.

How is this different from Wispr Flow?

Wispr cleans up your speech, and so do we — and both will rewrite a selection when you say the change. The difference is what happens to the shape of what you said. Talking to a coding agent, your ramble arrives as a brief: the goal, the context, the constraints and the tasks, with every detail you spoke still in it. And say what an email should do and Yappr writes the email, rather than handing back your sentence with the ums taken out.

What do I actually get for free?

Every feature, and fifty polished dictations a week. Your rambles turned into clear briefs for your coding agent, whole emails from one spoken sentence, any selected text rewritten by saying what's wrong with it, the right tone for each app, the dictionary that keeps your names and jargon right, and all three hotkey behaviors — none of it is held back for Pro. Polished means fillers, stutters and false starts removed; past fifty, dictation keeps working, it just stops going out for the polish. No card. Pro lifts the weekly cap, and that is the only difference.

How long is the trial, and what do invites add?

Every new account starts with 14 days of Pro — no card, nothing to cancel. When they run out you are on Free: every feature, 50 polished dictations a week, and dictation never stops. Every account also has an invite code. A friend who enters yours within 7 days of signing up gets 14 extra days of Pro at once, and when they have dictated 1,000 words, a month is added to yours — for up to 12 friends. Words are counted on the dictations that get polished, so very short ones do not count.

Is Pro actually unlimited?

For anything you can say out loud, yes. There are limits, and these are all of them: 120 polished dictations an hour and 600 in a day, and 30 minutes of polished speech in any hour. One recording runs for up to 10 minutes; then it stops, types what you said as usual, and you press again to carry on. They exist so that one runaway script, or a key left recording through a lecture, cannot run up the bill for everybody else. The heaviest real user we have measured does about 44 dictations a day — a few minutes of talking — so you are unlikely to meet any of them. If you did, nothing breaks: dictation keeps working and cleanup falls back to what runs on your Mac until the window clears, exactly like Free past fifty. We would rather print the numbers than say “fair use” and leave you guessing.

Windows or Linux?

macOS only, today. Windows and Linux are not supported yet, and we would rather say that than point you at a beta you cannot join. If you need them now, the comparison post covers which tools do. On a Mac, Yappr needs Apple silicon; it does not run on Intel Macs.

Go build
something great.

Download for MacmacOSSend it to your Mac