Speak the messy version first
Dictate the context you would normally underwrite: constraints, failing behavior, expected output, edge cases, and the reason behind the change.
Developers
Ship clearer context without typing every word.
Peanut is useful when the work is not code syntax itself: prompts, issue notes, PR summaries, QA findings, test plans, refactor explanations, and long technical docs you would rather listen through.
Where it fits
Cursor, Linear, GitHub, Slack, docs, browser fields, and internal tools.
Best shortcut
Use Peanut when you need to explain intent, tradeoffs, and reproduction steps quickly.
Why it beats plain dictation
Read-aloud, history, snippets, translation, and BYOK keep the workflow going after text appears.
Turn debugging into notes
Capture reproduction steps, suspected causes, test results, and follow-up tasks while the details are still in your head.
Listen through dense text
Use read-aloud for specs, incident writeups, generated code explanations, and long PR descriptions when your eyes need a break.
Developer workflows
Moment
Typing-only workflow
With Peanut
Cursor prompt
Short prompt, missing constraints
Full spoken context, then cleaned into a usable prompt
Linear ticket
Sparse notes after the debugging session
Repro steps, expected behavior, and next actions dictated immediately
PR summary
Typed after the change, often too brief
Speak the risk, testing, and product impact while context is fresh
Repeated comments
Rewrite the same review language
Use snippets for standard test notes, setup commands, and caveats
For builders who think in paragraphs.
Peanut is not trying to replace your editor. It helps you get the surrounding technical context into the tools where your team already works.