Resonant

Resonant + Linear

Speak issue descriptions.
Ship faster context.
5x your typing speed.

Linear rewards thorough issues. Reproduction steps, affected scope, priority reasoning — the context that prevents three rounds of follow-up. Voice lets you include all of it in the time it takes to type the title.

Resonant transcribes your voice locally on your Mac. Press a key, speak the full context, and clean structured text lands in Linear. No cloud. No latency.

Used by engineers at

AnthropicLinearGoogleNvidiaStripe

The gap

Same bug. Same engineer.
Different input method.

Bug report: checkout page crashes on Safari

Typed34 words -- typed in 50 sec

Title

Checkout crash on Safari

Description

Checkout page crashes on Safari when user clicks pay. Works on Chrome. Seems related to the Stripe integration.

Missing: OS version, reproduction steps, frequency, affected users, error logs, what was already investigated.

Dictated with Resonant152 words -- dictated in 30 sec

Title

Checkout crash on Safari 17.2+ when Stripe payment sheet initializes

Description

Checkout page crashes on Safari 17.2 and above when the user clicks the Pay button. The Stripe payment sheet fails to initialize — console shows a SecurityError related to the cross-origin iframe sandbox attribute. **Reproduction steps:** 1. Open checkout with any item in cart 2. Select credit card payment 3. Click "Pay now" 4. Safari freezes for 2-3 seconds, then the page goes white **Expected behavior:** Stripe payment sheet opens normally, as it does on Chrome and Firefox. **Affected users:** Roughly 18% of our checkout sessions are Safari (checked PostHog). This has been happening since the Stripe SDK upgrade last Tuesday. **What I've tried:** Rolling back the SDK version locally fixes it, but that version has the currency formatting bug we patched. I think the fix is to add the allow-popups-to-escape-sandbox attribute to the iframe, but want to confirm that doesn't break our CSP headers. **Priority reasoning:** This is blocking revenue for ~1 in 5 users. Suggesting P1.

Full context. Reproduction steps. Affected scope. Prior investigation. Priority reasoning.

Where it fits

Six moments in Linear
where voice changes the output.

Issue descriptions

Say everything the issue needs: what broke, how to reproduce it, who it affects, what you already tried. The context that turns a vague ticket into an actionable one.

Sprint review notes

Narrate what shipped, what carried over, and why. Dictate the recap in the time it takes to open the document. Your team gets the full picture, not a bullet-point summary.

Project updates

Speak the status — what's on track, what's at risk, what changed since last week. Stakeholders get the nuance that gets lost when you condense to save typing time.

Bug reports with full context

Reproduction steps, environment details, error output, what you already investigated. The kind of thorough report that prevents three rounds of follow-up questions.

Design doc summaries

Talk through the approach, the alternatives you considered, and the tradeoffs. Attach it to the project in Linear. Faster than writing it from scratch, richer than skipping it.

Standup recaps

What you did, what you're doing, what's blocking you — spoken in 15 seconds. Clean text lands in Linear. No more typing the same three bullet points every morning.

Before and after

Raw voice in.
Structured update out.

You speak the way you think — with filler words, tangents, and self-corrections. Resonant cleans it up into structured text that reads like you spent 10 minutes writing it.

What you say (raw)

"Okay so the onboarding flow — we're seeing a big drop-off on the second step, the one where users connect their workspace. I looked at the PostHog funnel and it's like 40% of users abandon there. I think the problem is we're asking for too many permissions upfront, the OAuth scope list looks scary. What if we did a progressive permissions thing where we only ask for read access first and then prompt for write access when they actually try to create something. Also the loading state after they click authorize is like 6 seconds with no feedback, people probably think it's broken."

~90 words, spoken in 18 seconds

What Linear receives
## Onboarding drop-off at workspace connection step We're seeing 40% abandonment on step 2 of onboarding (workspace connection). Based on the PostHog funnel analysis, two issues are driving the drop-off: **1. Permission scope is too broad upfront** The OAuth consent screen requests full read/write access immediately. The scope list looks intimidating to new users who haven't built trust with the product yet. **Proposed fix:** Implement progressive permissions — request read-only access during onboarding, then prompt for write access contextually when the user first attempts to create or modify a resource. **2. Authorization loading state has no feedback** After clicking "Authorize," users wait ~6 seconds with no visual indication that anything is happening. Likely causing users to close the tab or navigate away. **Proposed fix:** Add a loading indicator with status text ("Connecting your workspace...") immediately after the OAuth redirect returns. **Impact:** If we recover even half of the 40% drop-off, that's a meaningful improvement to activation. Suggesting this as a priority for the current cycle.

Structured, formatted, ready to paste into Linear

Architecture

Your voice stays
on your machine.

Issue descriptions contain internal context — architecture decisions, customer names, security details, infrastructure specifics. Cloud dictation routes that audio through external servers before you even decide to submit.

Resonant processes everything on your Mac. Audio never leaves your device. The only thing that reaches Linear is the finished text — exactly as if you'd typed it.

No accounts. No audio uploads. No server logs of your dictated bug reports. Your internal context stays internal.

Free. Local. Works in any Linear field.

Give Linear the context
your issues actually need.

Thorough issues. Structured updates. No subscription, no cloud, no typing bottleneck.

Requires macOS 14+ · Apple Silicon