Voice to Text for Linear
Linear is where your team builds software. But writing issues, cycle planning notes, and project updates takes time you don't have. Every detailed issue description means less time coding. Blurt lets you hold a button, speak naturally, and release. Your text appears instantly in any Linear text field. Issue descriptions, comments, project documents, initiative briefs. No copying, no pasting, no switching apps. Just talk and ship.
The Typing Problem
Writing good issue descriptions feels like a tax on shipping
You know exactly what needs to be built. You could explain it to a teammate in thirty seconds. But typing out the context, acceptance criteria, and technical considerations takes ten minutes. So you write 'Fix the thing' and hope the assignee can figure it out. They can't. They ping you on Slack. You explain it verbally anyway. Double the time.
Cycle planning notes become a bottleneck
Your cycle planning meeting just ended. Priorities are clear in everyone's head. But someone needs to document them. Update the project descriptions. Write summaries for each initiative. That someone is you. By the time you finish typing, the next meeting has started. Planning documentation is always behind.
Project updates that nobody writes
Leadership wants weekly project updates. Stakeholders want visibility. Your team knows where things stand, but nobody has time to write status reports. So updates slip. A week becomes two. Suddenly you're fielding questions that a simple project update would have answered. The cost of not writing is higher than writing, but typing still takes too long.
Issue comments that should be paragraphs become sentences
You're triaging an issue. There's important context about why this bug exists, what you've already tried, and what the right fix probably looks like. Typing all that takes five minutes. So you write 'looked into this, probably needs a refactor' and move on. The next person to pick up this issue has to rediscover everything you already know.
Initiative briefs never get the detail they deserve
You're kicking off a new initiative. It needs background, goals, success metrics, risks, and a rough plan. You have all of this in your head from the last three strategy discussions. But typing a proper brief means blocking off an hour. You write the minimum viable version. The team starts building without full context. Rework follows.
How It Works
Blurt works everywhere in Linear: issues, projects, cycles, initiatives, comments, and documents. Anywhere you can type, you can talk.
Click into any Linear text field
Put your cursor in an issue description, comment, project brief, or any text area in Linear.
Hold your hotkey and speak
Press your chosen shortcut and talk naturally. Describe the issue, explain the context, list the requirements. Blurt adds punctuation automatically.
Release and keep building
Your text appears at the cursor. Move to the next issue, the next project, the next cycle. Documentation done, back to shipping.
Real Scenarios
Writing issue descriptions with full context
You just discovered a bug in the checkout flow. Hold the button and describe it: 'When a user adds more than five items to their cart and applies a percentage discount code, the total displays incorrectly. The discount is applied to each item individually instead of the cart total. This affects approximately ten percent of our checkout sessions based on analytics from the last week. Acceptance criteria: discount codes should apply to cart subtotal after all items are added. Need to check if this also affects the mobile app.' Issue created with full context in forty-five seconds. The engineer who picks it up knows exactly what to fix.
Rapid issue triage during bug review
You're going through the bug backlog with your team. Issues are flying by. Instead of typing status updates, hold the button: 'Confirmed on staging, this is P1, assigning to platform team. Likely related to the caching changes in version 2.4. Workaround is to clear local storage.' Next issue. 'Cannot reproduce, need more info from reporter. Adding needs-info label.' Triage a dozen issues in the time typing would handle three.
Cycle planning documentation
Your team just planned the next two-week cycle. Before you forget, hold the button and dictate the summary: 'This cycle focuses on payment reliability. Top priority is the Stripe webhook retry logic, followed by the invoice reconciliation bug. We are deprioritizing the new payment methods work until next cycle. Carry-over from last cycle includes the subscription pause feature which needs design review before engineering.' Cycle documented while the conversation is fresh.
Project status updates for stakeholders
Friday afternoon. Time for project updates. Hold and speak: 'Week three update. Core API refactor is seventy percent complete. Blocked on database migration which is waiting for DevOps capacity. Risk: if migration slips past next Tuesday, we miss the integration deadline with Partner X. Mitigation: discussing priority escalation with DevOps lead Monday.' Stakeholders informed. You're done before the meeting started.
Detailed comments during code review
You're reviewing a PR linked to a Linear issue. You want to add context to the issue itself. Hold and explain: 'Reviewed the implementation. The approach is solid but I have concerns about the database query in the user lookup. It is doing a full table scan which will be fine now but could cause issues at scale. Suggesting we add an index before merging. See my comment on line 145 of the PR.' Feedback documented in Linear, connected to the code review.
Initiative briefs during strategy sessions
Your team just finished discussing a new initiative. You need to capture the brief while the ideas are fresh. Hold and dictate: 'Initiative goal: reduce checkout abandonment by fifteen percent over Q3. Background: analytics show users are dropping off at the payment step, primarily on mobile. Hypothesis: streamlining the payment form and adding Apple Pay will address the main friction points. Success metrics: checkout completion rate, time to complete purchase, mobile versus desktop conversion parity.' Initiative documented in two minutes, not an hour.
Quick comments and questions on issues
You're scanning through your assigned issues. Each one needs a response. Hold: 'Clarifying question: does this need to work for guest users or only logged-in accounts?' Next issue: 'Started looking at this. Initial investigation suggests the problem is in the event handler, not the API. Will update when I have more info.' Next: 'This is actually a duplicate of issue 1247. Marking as duplicate.' Responsive issue management without the typing overhead.
Why Linear power users choose Blurt over built-in dictation
| Blurt | macOS Dictation | |
|---|---|---|
| Activation | Single hotkey, instant start | Double-tap function key or click microphone |
| Speed | Text appears in under 500ms | 2-3 second delay before transcription |
| Technical terms | Handles dev jargon well (API, webhook, PR) | Often mishears technical vocabulary |
| Consistency | Reliable in Linear's web and desktop apps | Sometimes fails in web-based text fields |
| Pricing | $10/month or $99/year, free tier included | Free but limited accuracy |
Frequently Asked Questions
Start Typing Faster Today
Free to try — no credit card required
Download Blurt