DEV Community: Al Amin

TextExpander Pricing vs Cheap Alternatives: A Developer's Cost Breakdown (Free, Open Source and Paid)

Al Amin — Fri, 30 Oct 2026 03:44:44 +0000

If you have ever looked at TextExpander pricing and wondered whether a cheap alternative would do the same job, you are not alone. Developers retype a lot: PR descriptions, review comments, bug report templates, standup notes, the same curl flags. A text expander removes most of that. The question is how much you need to pay for it.

This post breaks down TextExpander's current plans, then compares them with free and low-cost options from a developer's point of view: price, platforms (including Linux), how snippets are stored, and team sharing.

What is a text expander?

A text expander is a background app that watches what you type and replaces a short trigger with longer saved text. You type something like /pr and it expands into a full pull request template. Most tools also support placeholders such as today's date or a fill-in form, so one snippet can produce slightly different text each time.

Unlike editor snippets (VS Code user snippets, JetBrains live templates), a system-wide text expander works across apps: your browser, Slack, email, the terminal, and your IDE.

TextExpander pricing in 2026

According to TextExpander's own pricing page (checked on 30 October 2026):

Free: $0, with unlimited total snippets but only 5 active snippets, and you can swap one active snippet every 2 weeks.
Pro: $5 per user per month, billed annually ($60 per year), up to 5 users, unlimited active snippets, plus dynamic content like date math and JavaScript snippets.
Business: $10 per user per month, billed annually ($120 per year), no 5-user cap, plus snippet requests, guest sharing and Google SSO.
Enterprise: custom pricing.

Monthly billing is also offered; annual billing gives two months free. Prices are in USD and exclude tax, so VAT or GST can be added at checkout depending on your country.

On platforms, TextExpander's FAQ lists Mac, Windows, iPhone and iPad, and a Chrome extension. Linux is not on that list.

What the free plan means for developers

Five active snippets runs out fast. A PR template, a "needs repro" reply, a review nit, a signature, a standup template, and you are already over. After that, you either swap snippets every two weeks or pay for Pro.

Pro is fair value if you need JavaScript snippets or shell scripts on macOS. If your needs are simpler, or you work on Linux, cheaper routes exist.

Cheap and free TextExpander alternatives

espanso (free, open source)

espanso is an open-source text expander for Windows, macOS and Linux. Snippets ("matches") live in YAML files under a config folder, and changes reload automatically after you save. It has a package hub, a search bar (Alt+Space by default) and app-specific configs.

The big plus for developers: snippets are plain files you can keep in your dotfiles repo and review in git. The trade-off is that you edit YAML by hand and need to get indentation right.

matches:
  - trigger: ":pr"
    replace: "## What\n\n## Why\n\n## How to test\n"

AutoHotkey hotstrings (free, Windows only)

AutoHotkey is a free scripting tool for Windows, and its hotstrings expand abbreviations as you type. If you already write AHK scripts, adding hotstrings costs nothing, but it does not help on macOS or Linux.

Editor snippets (free, editor only)

VS Code user snippets and JetBrains live templates are already installed and great for code. They do not follow you into Slack, a GitHub comment box or an email, which is where a lot of repeated text happens.

Text Blaze (freemium)

Text Blaze started as a Chrome extension and now also has Windows and macOS desktop apps. Per its plans page, Pro is $2.99 per month billed yearly (or $3.49 billed monthly) and adds full access to forms, images and tables, and if/then rules. Business is $6.99 per user per month billed yearly. The free plan has limited snippets. Text Blaze's FAQ says native apps for other platforms are on its roadmap with no ETA, so on Linux you are limited to the Chrome extension today.

InsertKit (free tier plus a low-cost plan)

InsertKit is a text expander combined with voice typing and clipboard history. It runs on Windows, macOS and Linux (AppImage, .deb and .rpm), plus Android and a Chrome extension, and snippets sync through your account. There is a free tier, and the paid plan is $2.99 per month at international pricing.

A few details that matter to developers:

Triggers and prefixes. Triggers look like /pr or /repro. The / and ; prefixes are on by default, and a trigger saved as /pr also works as ;pr, which helps in apps like Slack or Discord that use / for their own commands.
F4 to pause. On desktop, F4 turns typed snippet triggers off and on, which is handy before a long coding session so nothing expands inside an identifier.
Dynamic snippets. Add fields such as text, dropdown or date, and typing the trigger opens a small fill-in form (desktop and Chrome extension). Built-in variables like {{date}} are available too.
Linux notes. The app has a Linux dependencies check (xdotool, wtype, maim), and on Wayland its tips point to wtype or ydotool.
Voice, if you want it. Voice typing works in 100+ languages, and saying "insert" plus a snippet name pastes that snippet by voice. A dynamic snippet inserted by voice still opens its fill-in form. A Code formatting profile turns spoken identifiers into camelCase or snake_case.
Bring your own model. You can add your own API keys, including a custom OpenAI-compatible provider such as Ollama or LM Studio, so the AI formatting and voice assistant can run against a local model. There is also an offline Whisper option for speech on desktop.

The trade-off compared with espanso: snippets are edited in a GUI and synced through an account rather than kept as YAML files in your repo.

Side-by-side comparison

Tool	Entry price for one person	Free option	Linux	How snippets are stored	Team sharing
TextExpander	$5/user/mo billed annually (Pro)	Yes, 5 active snippets	Not listed	Cloud account, app UI	Pro up to 5 users; Business unlimited
espanso	$0	Fully free, open source	Yes	YAML files on disk	Share files or packages yourself
AutoHotkey	$0	Fully free	No (Windows only)	Script files	Share scripts yourself
VS Code / JetBrains snippets	$0	Built in	Yes (inside the editor)	Editor config	Via settings sync or repo
Text Blaze	$2.99/mo billed yearly (Pro)	Yes, limited snippets	Chrome extension only	Cloud account, app UI	Business plan
InsertKit	$2.99/mo	Yes, free tier	Yes	Cloud account, app UI	Private or Teams snippets

Prices are as published by each vendor at the time of writing and can change, so check before you buy.

How to choose without overpaying

Start from where you type, not from feature lists:

Only inside your editor? Use your editor's built-in snippets. They are free and already there.
Across apps, and you like config-as-code? espanso gives you text expansion on every desktop OS for free, with snippets in git.
Windows only, and you already script? AutoHotkey hotstrings cost nothing.
Need fill-in forms and team sharing on Mac or Windows? TextExpander Pro or Text Blaze are worth comparing. Count your active snippets first, because the TextExpander free plan caps them at 5.
Want snippets, voice typing and clipboard history in one app, including on Linux and Android? A combined tool can replace two or three separate subscriptions.

Also budget for migration time: rebuild your top ten snippets in the new tool and use it for a week before deleting anything.

Trying a cheaper option

If you want text expansion across apps with a GUI instead of YAML, test a low-cost tool against your current setup for a week. Current plans are on the InsertKit pricing page, and the free tier is enough to rebuild a few of your most-used snippets and compare.

FAQ

How much does TextExpander cost?

Per TextExpander's pricing page, Pro is $5 per user per month and Business is $10 per user per month, both billed annually. Monthly billing is available at a higher rate, and Enterprise is custom. Taxes may be added depending on your country.

Is there a free version of TextExpander?

Yes. The Free plan keeps unlimited snippets in your account but only 5 can be active at a time, and you can swap one active snippet every 2 weeks.

What is the cheapest TextExpander alternative?

espanso and AutoHotkey are free. espanso works on Windows, macOS and Linux with YAML config; AutoHotkey is Windows only. Among paid GUI tools, Text Blaze Pro and InsertKit both list $2.99 per month (Text Blaze's price is billed yearly).

Is there a TextExpander alternative for Linux?

Yes. espanso supports Linux, and InsertKit has a Linux desktop app (AppImage, .deb and .rpm). TextExpander's FAQ does not list Linux.

Can a text expander work in the terminal and IDE?

System-wide expanders such as espanso and InsertKit type into most apps where you can enter text, including terminals and editors. If expansions get in the way while coding, use a toggle key; in InsertKit, F4 pauses typed triggers on desktop.

Do I need a text expander if my editor has snippets?

Not for code inside the editor. A system-wide expander covers everything else: PR descriptions, issue replies, chat messages and emails.

Text Expander With Voice Typing: Why I Keep Snippets and Dictation in One App

Al Amin — Fri, 23 Oct 2026 03:38:43 +0000

For a long time I ran two separate apps: a text expander for the replies I send over and over, and a dictation tool for everything new. They worked, but they never talked to each other. Then I tried a text expander with voice typing built in, and my day got simpler. This post explains what that kind of tool is, the three ways to set one up, and how to pick.

I compare TextExpander, Wispr Flow and InsertKit using only what each company publishes on its own site (I checked the pages on October 23, 2026). Prices and plans change, so check the pages again before you buy.

What is a text expander with voice typing?

A text expander saves text you use often, such as a sign-off, an address or a support reply, and inserts it when you type a short trigger like /reply. Voice typing (dictation) turns what you say into text at your cursor.

A text expander with voice typing does both from one app. You type a trigger for fixed text, you speak for new text, and ideally you can also call up a saved snippet by voice.

Why snippets and dictation belong together

Most of what I write falls into two buckets:

Fixed text. The same refund policy, the same booking link, the same "thanks, I'll get back to you" line. Snippets handle this well because the wording never changes.
New text. The part of an email that answers this specific person, a quick Slack reply, notes after a call. Speaking is faster here because there is nothing to reuse.

A real email is usually both: a few sentences I need to say fresh, plus a block I have written a hundred times. With two separate apps I kept switching modes. With one app I dictate the personal part and drop in the fixed part without leaving the text field.

Three ways to get a text expander with voice typing

Option 1: A text expander plus separate dictation

This is the classic setup. TextExpander is a well-known example. According to its pricing page:

The Free plan includes 5 active snippets, with 1 snippet swap every 2 weeks, and new accounts get a 30-day preview of paid features.
Pro is listed at $5 per user per month and Business at $10 per user per month, both billed annually.
One account works across Mac, Windows, iPhone and iPad, and the Chrome extension.
Paid plans add dynamic content such as date math, conditional sections in fill-ins and JavaScript snippets.

I did not see voice dictation listed on TextExpander's pricing page, so in this setup you pair it with the dictation built into your system or another app.

Option 2: A dictation app that has snippets

Wispr Flow comes at it from the voice side. Its features page describes snippets as voice shortcuts: you speak a cue, and Flow pastes the full text where you are typing. Its pricing page says:

Flow is free on Mac, Windows, iPhone and Android, with weekly usage limits on the free plan.
The free plan includes speech-to-text in any app, 100+ languages, and a dictionary and snippets.
Pro is listed at $15 per user per month on monthly billing and removes the limits.

If you mostly speak and only need a handful of saved phrases, this is a strong option.

Option 3: One app built for both

InsertKit, the app I use, treats snippets, voice typing and clipboard history as three equal parts of one app. You can type a trigger, speak, or say "insert" plus a snippet name, and it all works from the same snippet library.

Text expander with voice typing: a quick comparison

Feature	TextExpander	Wispr Flow	InsertKit
Typed snippet triggers	Yes	Not listed on its features page	Yes, with `/` or `;` prefixes
Voice dictation	Not listed on its pricing page	Yes, 100+ languages	Yes, 100+ languages
Insert a snippet by voice	Not listed	Yes, speak the cue	Yes, say "insert" plus the snippet name
Clipboard history	Not listed	Not listed	Yes, synced to your account
Platforms	Mac, Windows, iPhone and iPad, Chrome	Mac, Windows, iPhone, Android	Windows, macOS, Linux, Android, Chrome
Free plan	5 active snippets	Weekly usage limits	Daily voice limit on InsertKit Free

"Not listed" means I could not find it on the pages I checked, not that it can never exist.

How my combined workflow looks in practice

Here is a normal client email, start to finish, in InsertKit on my desktop:

I click into the email body and press the voice shortcut (Right Alt by default). A small pill near the cursor shows it is listening.
I speak the personal part: "Hi Dana, thanks for sending the draft, I've gone through it and I have two small changes."
Smart Formatting cleans up punctuation and filler words like "um", and it adapts the style to the app. In an email app it keeps a professional, warm tone. In a chat app like Slack it stays short and casual.
For the fixed part I type /reply and my saved paragraph about turnaround times appears. If I'd rather not touch the keyboard, I say "insert reply" instead, and InsertKit matches the snippet by its trigger or title.
If I need something I copied an hour ago, I press Ctrl+Shift+Z (Cmd+Shift+Z on Mac). The popup has Clipboard, Snippets and Favorites tabs, so it doubles as a snippet picker.

A few details made the combination work better than two apps:

Dynamic snippets (desktop). A snippet like /meet can open a small form with fields for a client name and a date, then insert the finished message.
Variations. One trigger can hold several versions, like a short and a long reply, and a picker lets you choose.
Custom vocabulary. I added client and product names, plus corrections like "insert kit" to "InsertKit". These sync to my account.
Voice Assistant. Saying "hey ik" followed by a request, like "hey ik write a polite reminder about the invoice", makes the AI write the answer straight into the text field.

When this setup is not the right fit

To be fair, one app for everything is not always the answer:

You only need snippets with heavy logic. If your team relies on JavaScript snippets or conditional fill-ins, TextExpander lists those on its paid plans.
You need meeting notes. Wispr's pricing page includes a Notetaker for meetings on Mac and Windows. That is a different job from dictation and snippets.
You work mainly on iPhone. InsertKit's site lists Windows, Mac, Linux, Chrome and Android. Wispr Flow and TextExpander both list iPhone.

How to set up a text expander with voice typing in InsertKit

Install the app for your platform and sign in. The same account syncs your snippets, clipboard history and vocabulary across desktop, Android and the Chrome extension.
On macOS, grant Accessibility (for pasting) and Input Monitoring (for detecting triggers as you type). The app shows a banner with buttons that open the right System Settings page.
Create three or four snippets for the text you type most. Use a slash style like /reply, /addr or /thanks. The Templates library has ready-made ones if you'd rather not start from zero.
Turn on Voice Typing and test your microphone on the Voice Typing page.
Add the names and terms you say often to Custom Vocabulary.
Try saying "insert" plus one of your snippet names, so you get used to both paths.

You can start on the free plan. The pricing page lists a free plan covering snippets, voice and clipboard with no credit card, a daily voice limit on InsertKit Free, and credits for InsertKit Premium. You can compare the details on InsertKit's plans for text expansion and voice typing.

FAQ

Can a text expander do voice typing?

Some can. A classic text expander only expands typed triggers. A text expander with voice typing adds dictation, so you can speak new text and insert saved snippets from the same app. InsertKit does both on Windows, macOS, Linux, Android and in its Chrome extension.

Can I use voice commands to insert text snippets?

Yes, in apps that support it. In InsertKit you say the call name "insert" plus the snippet name, for example "insert greeting", and the snippet is pasted. You can change the call name. Wispr Flow's snippets also work by speaking a cue.

Does voice typing work offline?

On desktop, InsertKit has a Local Offline (Whisper) option that runs on your computer, so your audio stays on the device in that mode. It is not available on Android. Cloud providers process audio online.

How many languages does voice typing support?

InsertKit voice typing supports 100+ languages, plus auto-detect. Wispr Flow also lists 100+ languages.

Is a dictation app with snippets the same thing?

Close, but the starting point differs. A dictation app with snippets is voice-first, with saved phrases you call by voice. A text expander with voice typing also gives you typed triggers, fill-in forms and a snippet library you can use with or without speaking.

If you juggle a text expander and a separate dictation tool, try one week with a single app for both.

How to Set Up Paid Client Calls with TidyCal (One-Time $29 Lifetime Deal)

Al Amin — Thu, 22 Oct 2026 21:02:31 +0000

Freelance developers spend a surprising amount of time on things that are not code. Booking discovery calls, chasing payment for a consulting hour, rescheduling over email. A booking link with payment built in removes most of that.

This guide covers setting up that workflow with TidyCal, a scheduling tool sold on AppSumo as a lifetime deal: a one-time payment instead of a monthly subscription. The current offer is on the TidyCal AppSumo deal page.

Why a booking tool for freelance work

A typical freelance week has a few kinds of calls:

Free 15–30 minute discovery calls with new leads
Paid consulting or code review sessions
Recurring check-ins with retainer clients
The occasional group session or workshop

TidyCal supports one-on-one, group and recurring booking types, so all of these can live behind one link. The product page sums up the flow: "Share one link. Clients pick a time, pay if you charge, and it lands on your calendar."

Step 0: Pick the right tier

Both tiers are lifetime access with a single payment.

	Individual	Agency
Price	$29 once (regular $144)	$79 once
Team members	No	You + 3
Integrated calendars	10	10
Reminders	Email	Email + 10 SMS/mo (US & Canada)
Bookings per month	Unlimited	Unlimited
Platform fee on paid bookings	1%	1%
Team booking page / collective / round-robin	No	Yes
Custom domain & no branding	No	No

A solo freelancer is usually covered by Individual. A small dev shop where leads should go to whoever is free will want Agency for round-robin meetings.

Deal terms to keep in mind: activate within 60 days of purchase, upgrades between the two tiers are allowed while the deal is live, downgrades within 60 days, and the deal is only for users who do not already have a paid TidyCal account. AppSumo's 60-day money-back guarantee applies.

Step 1: Connect your calendars

TidyCal syncs with Google Calendar, Outlook Calendar and iCloud Calendar, with up to 10 integrated calendars on either plan. Connect every calendar that holds real commitments (work, personal, a client's shared calendar) so conflicts get blocked automatically.

Step 2: Set availability, buffers and limits

Under availability, set:

Working hours for when calls can be booked
Buffer time between meetings so a call that runs over does not eat the next one
Booking limits so a single day does not fill with calls when there is code to ship

These three settings matter more than anything else for protecting focus time.

Step 3: Create your booking types

A sensible starting set:

Discovery call — free, 20 minutes, one-on-one, Google Meet or Zoom link attached
Paid consultation — 60 minutes, one-on-one, payment required
Retainer check-in — recurring weekly booking for ongoing clients
Workshop — group booking for a small cohort

TidyCal allows unlimited booking types and can attach Zoom, Google Meet or Teams links.

Step 4: Turn on payments

Connect Stripe or PayPal. Paid booking types then collect payment when the client books, so there is no invoice to chase afterwards.

Beyond single sessions, TidyCal lets you sell packages (for example, a bundle of sessions) and subscriptions, and you can create coupon codes for repeat clients or launches.

Factor in the cost: there is a 1% platform fee on paid bookings, on top of Stripe or PayPal fees. The page notes the separate Pro plan has no platform fee.

Step 5: Make the page and emails yours

Pick a page style, add your logo and colors, and write custom confirmation and reminder emails. Good confirmation emails cut down on no-shows and pre-call questions. Include what the client should prepare, such as a repo link or a short project brief.

One thing that will not change on the lifetime tiers: a "Powered by TidyCal" bar stays at the bottom of the booking page. Custom domain and no-branding are not part of either tier.

Step 6: Collect reviews automatically

TidyCal can request a review after each completed booking and show reviews on the booking page, with a verified review history. For freelancers, social proof on the same page where someone books is useful.

Step 7: Wire it into the rest of your stack

Integrations listed include Zapier, Google Analytics, Stripe, PayPal, Zoom and Google Meet. With Zapier, a new booking can trigger things like adding the client to a CRM or creating a task. Google Analytics shows how many visitors reach the booking page versus how many book.

Other options worth knowing about: CC others on bookings (useful when a client's PM wants to be in the loop), custom reply-to on the Agency plan, translation in 30+ locales, and AI features.

Where to put the link

Your portfolio site's contact page
GitHub profile README
Email signature
The "contact" section of proposals

What reviewers on AppSumo mention

TidyCal holds a 4.3 rating from 936 reviews on AppSumo. Support comes up often. Reviewer asya17 wrote:

"I reached out with an issue, and Luka Belik, Customer Experience Manager, was phenomenal. His instructions were clear, specific, and incredibly easy to follow. I made the exact updates he recommended, tested everything, and it worked perfectly."

There is also a useful warning from reviewer andres099, who upgraded tiers and later posted an update:

"UPDATE: I reached out to support and a couple of hours later received an email stating that issue was resolved. Turns out it was just a bug."

Their advice for anyone upgrading: "Just make sure if all your features are there if you're upgrading for some reason."

Things to double-check

Deal details can change, so verify every detail on the sale page before purchasing, especially the current price, the tier features and the activation window.

Wrap-up

For a freelancer, the workflow is simple: one link, clear availability, payment taken up front, reviews collected automatically. TidyCal handles that for a one-time $29 (Individual) or $79 (Agency), with the trade-offs of a 1% fee on paid bookings and a visible TidyCal bar.

You can check out the TidyCal lifetime deal here.

Disclosure: This post contains an affiliate link. A commission may be earned if you purchase through it, at no extra cost to you.

Text Expander With Multiple Variations: Canned Replies for GitHub Issues That Don't Read Like a Bot

Al Amin — Thu, 22 Oct 2026 06:45:46 +0000

If you maintain a project, work in devrel or sit in a support rotation, you already know the problem a text expander with multiple variations solves. The same five questions arrive every week, and the same canned reply pasted under each of them starts to look like a bot wrote it. People notice. A reporter who gets the identical "please provide a minimal reproduction" block that was posted on the last forty issues feels processed, not helped.

This post is about a small change that made my canned replies feel human again: keeping several versions of a reply under one shortcut, and choosing the right one at the moment I need it.

The problem with one canned reply per situation

Most of us start with a flat list. One snippet for "needs repro", one for "duplicate", one for "thanks for the PR". It works for a while. Then you notice three things:

The tone is wrong half the time. A first-time contributor and a long-time maintainer from another project should not get the same wording.
The length is wrong the other half. Sometimes a one-liner is enough. Sometimes the person needs the full checklist.
You end up with trigger sprawl. You create /repro, /repro-short, /repro-new, /repro-firm, and then forget which ones exist.

What I wanted was one shortcut per situation, with the variants living behind it.

What snippet variations are: multiple replies behind one shortcut

Snippet variations means one trigger holds several items, and each item has a label and its own content. In InsertKit, which is the tool I use for this, the flow looks like this:

I type the trigger, for example /repro.
Instead of inserting text immediately, a Choose variation picker opens. It shows the trigger, the snippet title, and how many options are available, with numbered items that each show a label and a preview.
I move with the arrow keys, press Enter or Tab to insert the one I want, or Esc to cancel. A small counter shows where I am, like "2 / 4".

The important detail for this use case: you choose. It is not a random rotation. That matters because the goal isn't to fool anyone with shuffled wording. The goal is to pick the reply that actually fits the person and the situation, without retyping it.

How I structure variations for issues, reviews and community questions

The trick is to label variations by who or how much, not by a vague number. When the picker opens, the labels are what you scan, so make them obvious.

Issue triage: `/repro`

First-timer, friendly: thanks them for the report, explains what a minimal reproduction is, and points to the issue template.
Regular contributor, short: "Could you add a minimal repro? Happy to dig in once we can reproduce it."
Stale, closing soon: a polite note that the issue will be closed if no repro arrives, with a clear way to reopen it.
Can't reproduce on main: asks for version, OS and the exact steps they ran.

Code review: `/review`

Nit, non-blocking: makes it clear the comment is optional.
Needs tests: asks for a test that covers the change, with a note on where similar tests live.
Scope too large: suggests splitting the PR and offers to review the first part quickly.
Approve with thanks: a short, warm approval for first contributions.

Community questions: `/faq-install`

Short answer: two lines and the docs section name.
Long answer: full install steps for people who are clearly stuck.
Known issue: acknowledges the bug, explains the workaround, and says where progress is tracked.

Three shortcuts, eleven replies. I only remember /repro, /review and /faq-install; the labels do the rest.

Making a picked variation still sound like you

Variations get you most of the way. A few habits close the gap between "template" and "reply":

Leave one sentence open. End the template where a personal line naturally goes, then type one specific sentence about their issue.
Write variations in your real voice. If you'd never say "We appreciate your patience" out loud, don't save it.
Keep them short. Long canned replies are the ones that feel automated. Link to docs by section name instead of pasting the whole page.

Variations vs. dynamic snippets: pick one per snippet

InsertKit also has dynamic snippets on desktop: you add fields like a text input, a dropdown or a date, and typing the trigger opens a small form, then your values replace placeholders such as {{username}} in the content. That's useful when the reply is the same but the details change, like a release note with a version and a date.

A snippet can't be both at once. In the snippet editor, the Snippet variations and Dynamic switches can't be on together, so I decide per snippet:

Different wording or length for the same situation: variations.
Same wording, different values: dynamic.

For triage replies I almost always want variations, because the tone is what changes.

Where the shortcut works

Because it runs system-wide on Windows, macOS and Linux, the same /repro works in the GitHub web UI, a Discord or Slack message, an email to a user, or a text field in my editor. Variations also work in the Android app and the Chrome extension, so I can answer from my phone with the same set.

A few practical notes from using it as a developer:

Slash-command apps. Discord and Slack use / for their own commands. A trigger saved as /repro also works with any other prefix you enable under Settings, Snippets, Trigger Prefixes, so you can switch prefixes for those apps.
Pausing while coding. On desktop, F4 toggles all snippets off and on. I press it before long coding sessions so nothing expands mid-identifier.
Sharing with a team. Snippets can be Private or shared with your team, which helps when several people triage the same repo and you want consistent but not identical wording.

If you also answer by voice, the same app does voice typing in 100+ languages, but that's a separate topic.

How this compares with other ways of keeping canned replies

GitHub has its own saved replies, and I still use them for things that only live on GitHub. According to GitHub's docs they work in issues, pull requests and discussions, are tied to your personal account, and you can create up to 100. The limit for me was that they stay inside GitHub.

If you're looking for an espanso alternative with a GUI, it's worth knowing what espanso does here, since it's a capable open-source tool. Per espanso's docs, if several matches share one trigger it shows a selection dialog (they call it match disambiguation), it has a Choice extension for picking from a list, and a Random extension that picks one replacement at random. All of that is configured in YAML files. If you like editing config, that's a solid setup.

Approach	Where it works	How you pick a version	How you set it up
GitHub saved replies	Issues, PRs and discussions on GitHub	Choose from your saved list	Web settings
espanso	System-wide	Selection dialog for shared triggers, or random	YAML config files
InsertKit variations	System-wide on desktop, plus Android and Chrome	Choose variation picker with labels and previews	GUI snippet editor

I went the GUI route: I wanted to edit replies in a form, see labels and previews when choosing, and have the same snippets on my phone.

Setting up your first variation snippet

Open InsertKit and go to Snippets, then Add Snippet.
Set a trigger such as /repro and a clear title like "Needs reproduction".
Turn on the Snippet variations switch.
Add items, each with a label ("First-timer, friendly", "Regular, short") and the reply text.
Pick a category like "Triage" so it's easy to filter later, and choose Private or Teams.
Save, open any issue, and type /repro. The picker opens; choose and insert.

If you want to try it, you can download InsertKit for desktop and add your first variation snippet in a few minutes.

FAQ

What is a text expander with multiple variations?

It's a text expander where one shortcut holds several versions of a snippet. When you type the shortcut, you choose which version to insert instead of always getting the same text.

Does InsertKit pick a variation at random?

No. When you type the trigger, a Choose variation picker opens with numbered, labeled items and previews. You select one with the arrow keys and Enter or Tab, or cancel with Esc.

Can I use snippet variations for canned replies on GitHub issues?

Yes. The desktop app expands snippets system-wide, so a trigger like /repro works in GitHub's comment box in the browser, as well as in chat apps, email and editors.

Can one snippet have both variations and fill-in fields?

No. In InsertKit a snippet uses either variations or dynamic fields, not both. Use variations when the wording changes and dynamic snippets when only the details change.

Do variations work on Android?

Yes. When you type the full trigger on Android, a picker appears so you can choose which item to insert. Dynamic fill-in forms are a desktop feature.

What if an app already uses the slash key for commands?

You can enable other trigger prefixes in Settings, and a trigger saved with a slash also works with any enabled prefix. On desktop you can also press F4 to turn snippets off temporarily.

Voice Typing on Linux: How to Dictate Into Any App on X11 and Wayland

Al Amin — Wed, 21 Oct 2026 06:43:38 +0000

Voice typing on Linux has always been a bit of a DIY project. On Windows you press Win+H, on macOS you tap the dictation key, and on most Linux desktops you go looking for a Python script, a Whisper model, and a way to get the text into the window you're actually using.

This post explains what a working voice typing setup on Linux needs, why X11 and Wayland behave differently, and how I set it up with a GUI app instead of gluing scripts together. It's written for people who want dictation in a terminal, an editor, a browser, and a chat app, not just inside one program.

What "voice typing on Linux" actually requires

Speech-to-text is only half the job. A usable setup has three parts:

Capture: record from the right microphone, and know when to stop.
Transcribe: turn audio into text, either with a local model (such as Whisper) or a cloud API.
Insert: put the text where your cursor is, in whatever app has focus.

Most homemade setups get the first two working quickly. The third part is where Linux gets tricky, because it depends on your display server.

X11 vs Wayland: why inserting text is the hard part

On X11, any program can send synthetic keystrokes or paste into the focused window. Tools like xdotool do this, which is why older dictation scripts "just work" on X11 sessions.

On Wayland, apps are isolated from each other by design. A random program can't type into another window the way it could on X11. To insert text you need a tool that the compositor allows, such as wtype (on compositors that support the virtual keyboard protocol) or ydotool (which works at the input-device level and usually needs extra permissions).

So if a dictation tool works on your laptop but not on a colleague's, the first thing to check is echo $XDG_SESSION_TYPE. If it says wayland, the insertion method is probably the difference.

Local Whisper vs cloud speech-to-text

	Local (offline) Whisper	Cloud speech API
Internet needed	No	Yes
Where audio goes	Stays on your machine	Sent to the provider
Setup	Download a model once	Sign in or add an API key
Speed	Depends on your CPU/GPU and model size	Depends on your connection and the provider
Good for	Private notes, offline work, sensitive text	Weaker hardware, quick setup

Model size is the main trade-off for local dictation. Small models download fast and run on modest hardware; larger models are heavier and usually more accurate. Try a small one first and move up only if the results aren't good enough for you.

A GUI setup: voice typing on Linux with InsertKit

I use InsertKit, a voice typing and text expander app, which ships Linux builds as .AppImage, .deb and .rpm. It runs in the system tray and inserts text at the cursor in most apps where you can type: terminals, VS Code, browsers, Slack, and so on.

1. Install and check dependencies

After installing, open Settings → General → Linux Dependencies. It checks for xdotool, wtype and maim. On Wayland, the tips point you to wtype or ydotool. On Debian or Ubuntu, for example:

sudo apt install xdotool wtype

2. Pick a speech engine

In the Speech Engine panel you can choose:

InsertKit Free: hosted models with a daily limit. You just sign in; no API key.
InsertKit Premium: premium hosted models that use credits.
Local Offline (Whisper): runs fully on your computer with no internet. Models download inside the app: Tiny (~75 MB), Base (~140 MB), Small (~460 MB), Medium (~1.5 GB) and Large v3 (~3 GB).
Bring your own key: OpenAI, Groq, OpenRouter, Deepgram, AssemblyAI or ElevenLabs.

If privacy is the reason you're on Linux in the first place, Local Offline is the mode to pick: in that mode your audio doesn't leave the machine.

3. Dictate

Click into any text field, press the activation shortcut (default Right Alt / AltGr), and speak. A small pill near the cursor shows LIVE while it listens and THINK while it transcribes. Press the shortcut again to stop, or just stop talking: auto-stop after silence is on by default (5 seconds, adjustable to 2, 3, 8 or 10, or off).

Long dictation is split into chunks at natural pauses and transcribed while you keep talking, so a long paragraph doesn't arrive all at once at the end.

4. Let formatting match the app

With Smart Formatting on, the text is cleaned up (punctuation, filler words like "um") and the style adapts to the app you're in. In VS Code, vim or a terminal it uses a code-comment style, and spoken identifiers become camelCase or snake_case. In a chat app it stays short and casual. If the AI step can't be reached, the raw transcript is still pasted, so you don't lose what you said.

5. Teach it your words

Linux work is full of words speech models get wrong: kubectl, systemd, nginx, your project names. In the Vocabulary tab you can add hint words, and add corrections like "when heard as engine x, write as nginx". Corrections are applied before and after formatting.

Voice typing plus snippets

Because the same app is also a text expander, you can mix the two. Save a snippet with a trigger like /standup, type it in any app, and the full template appears. Or say "insert standup" while dictating and the snippet is pasted by voice. Press F4 to pause all snippets when you don't want / triggers firing, for example in a terminal session.

Pricing is simple: there's a free tier, and paid plans start at $2.99/month. Voice typing supports 100+ languages with auto-detect.

FAQ

Is there voice typing built into Linux?
Most Linux desktops don't ship system-wide dictation the way Windows (Win+H) and macOS do. You usually add it with a separate app or script.

Can I use Whisper for dictation on Linux offline?
Yes. Whisper models can run locally. In InsertKit, choose Local Offline (Whisper), download a model, and dictation works without an internet connection.

Why does my dictation tool work on X11 but not Wayland?
Wayland doesn't let apps type into other windows freely. You need a compositor-supported tool such as wtype, or ydotool.

Does voice typing work in the terminal?
With a system-wide app, yes: text is inserted wherever the cursor is, including terminal emulators.

Do I need an API key?
No. InsertKit Free and Premium need no key. Keys are optional if you want to use your own OpenAI, Groq or other account.

Wrapping up

A good Linux dictation setup comes down to three questions: where transcription happens (local or cloud), how text gets into the focused window (X11 or Wayland tooling), and whether the output fits what you're writing. Sort those out and voice typing on Linux stops being a weekend project and becomes something you reach for daily.

Text Expander for Developers: Reusable PR Descriptions, Bug Reports and Code Review Replies with Slash Triggers

Al Amin — Tue, 20 Oct 2026 06:05:51 +0000

Most developers I know already have a text expander habit, even if they don't call it that: a pinned note with a PR template, a gist of "polite no" review comments, a bug report skeleton buried in a wiki. The problem is the friction. Open the note, find the right block, copy, switch back, paste, fix the placeholders.

A text expander for developers removes that loop. You type a short trigger like /pr, and the full template appears in whatever you're typing in. This post covers the snippets I find worth saving, how to structure them, and how I set them up in InsertKit.

Why slash triggers work well for code-adjacent writing

A trigger is only useful if you never type it by accident. Plain words like reply show up in normal sentences, so I start every trigger with a slash: /pr, /bug, /lgtm. A slash almost never starts a word in prose, and it's easy to remember as "this is a shortcut".

A few habits that help:

Short and consistent. /pr, /bug, /nit, /ty. If you have to think about the trigger, you won't use it.
Group by prefix idea. Use /rev- for review replies, /bug- for issue templates, so autocomplete narrows them down as you type.
One job per snippet. Small snippets compose better than one giant template.

Snippet 1: a pull request description

## What
{{summary}}

## Why
Context, ticket or issue link: 

## How to test
1. 
2. 

## Notes for reviewers
-

Save this under /pr. In InsertKit you can turn a snippet into a dynamic one, so typing /pr opens a small form where you fill in fields like the summary, and the rest of the template is inserted around your answers. Placeholders are written as {{variable}}.

Snippet 2: a bug report that people can actually act on

**Summary**
One sentence describing what's wrong.

**Steps to reproduce**
1. 
2. 
3. 

**Expected behavior**

**Actual behavior**

**Environment**
OS / browser / app version:

**Logs or screenshots**

Trigger: /bug. The value isn't the template itself. It's that you stop skipping the "Environment" section when you're tired and in a hurry.

Snippet 3: code review replies

Review comments are repetitive, and tone matters. Having the wording ready helps you stay kind and clear when you have thirty files to go through.

/nit → Nit (non-blocking):
/lgtm → Looks good to me. Thanks for the clear description and tests.
/q → Could you add a bit of context on why this approach was chosen over the alternatives? Happy to approve once I understand the trade-off.
/split → This PR is doing a few things at once. Could we split it so each part can be reviewed and reverted on its own?

If you like to vary the wording by situation, InsertKit's snippet variations let one trigger hold several versions, each with a label. Type the trigger and a small picker opens so you can choose between, for example, a short and a longer version of the same reply.

Snippet 4: the small stuff you retype constantly

/sig for your email signature
/repo for a repository or docs link
/standup for a daily update skeleton
/today using the built-in {{date}} variable for notes and changelogs

Variables like {{date}}, {{time}} and {{myName}} are built in, so you don't need to type them each time.

Setting it up in InsertKit

I use a text expander for developers that works on desktop and mobile called InsertKit. It runs on Windows, macOS and Linux, with an Android app and a Chrome extension (iOS is planned for later). Here is the workflow:

Install the app and sign in. Snippets sync to your account, so they follow you across devices.
Create a snippet, give it a trigger such as /pr, and paste your template.
Optionally add a category (for example "Code review") so the list stays tidy.
Type the trigger in any text field. The snippet fires as soon as the full trigger is typed, no Space or Enter needed.

A few details that matter for developers:

Autocomplete popup. Type / and a small list of matching snippets appears at your cursor. Arrow keys to move, Tab or Enter to insert, Esc to close.
Prefix settings. Some apps use / for their own commands (Slack, Discord and Notion do). In Settings you can switch which prefixes are active, such as using ; instead.
A global on/off key. The default is F4. Handy when you're about to type something where expansion would get in the way.
Teams. Snippets can be Private or shared with a team, so your PR template can live in one place for everyone.

Because the expansion happens system-wide, the same /pr works in the GitHub web UI, a Slack message, or a text field in your editor.

Bonus: dictate the first draft, expand the rest

InsertKit also has voice typing in 100+ languages, and I sometimes combine the two. I dictate the free-form part of a bug report ("what I saw, what I expected") and let the /bug snippet provide the structure. It's optional, but it's a nice fit when typing long explanations feels tedious.

A starter set to copy this week

If you want to try the idea without overthinking it, start with five snippets:

Trigger	Use
`/pr`	Pull request description
`/bug`	Bug report skeleton
`/nit`	Non-blocking review comment
`/lgtm`	Approval reply
`/standup`	Daily update

Use them for a week, then add one new snippet each time you catch yourself typing the same thing twice.

FAQ

Do I need a text expander if my editor already has snippets?
Editor snippets only work inside the editor. A system-wide expander covers the places where you write the most prose: GitHub, Slack, issue trackers and email.

Which text expander for developers works on Linux?
InsertKit has a Linux desktop app (AppImage, deb and rpm packages), alongside Windows and macOS. Check the download page for the current builds.

Will slash triggers clash with Slack or Notion commands?
They can, since those apps use / themselves. You can turn individual trigger prefixes on or off in settings and use ; in those apps instead.

Can I share snippets with my team?
Yes. Snippets can be set to Teams access, and team management happens on the web dashboard.

Are my private snippets encrypted?
There is an optional end-to-end encryption setting for private snippets, currently marked as beta. Team snippets stay unencrypted so teammates can use them.

Is there an Android version?
Yes. The Android app expands /triggers in other apps, which is useful for quick replies on the go.

Wrapping up

You don't need a clever system. Pick the three or four things you retype every week, give them slash triggers, and let the machine do the typing. Your future self reviewing a PR at 6 pm will thank you.

What's the snippet you'd add first? Share it in the comments.

Local Whisper vs. Cloud Dictation: Privacy, Latency and Accuracy Tradeoffs (Plus a Private Setup)

Al Amin — Sun, 18 Oct 2026 05:01:35 +0000

"Just run Whisper locally" is good advice that skips a lot of detail. Local speech-to-text is genuinely useful, but it is not automatically faster, more accurate, or even fully private, depending on what else sits in your pipeline.

This post breaks the decision into three questions (what leaves the machine, where latency comes from, and how accurate it is for your voice) and ends with a setup where nothing leaves your computer. I use InsertKit as the dictation front end because it supports local Whisper, bring-your-own-key cloud providers, and custom OpenAI-compatible endpoints in one place. The tradeoffs apply to any stack.

1. Privacy: map the data flow first

A modern dictation pipeline usually has two stages:

mic audio -> [speech-to-text] -> raw transcript -> [LLM formatting] -> text at cursor

Each stage can be local or remote, and people often secure one and forget the other.

Speech-to-text. With a cloud engine, your audio is uploaded and processed by that provider. With a local Whisper model, audio stays on your machine.
Formatting. Clean-up (removing filler words, fixing punctuation, adapting tone) is usually done by a chat model. If that model is in the cloud, your transcript leaves the machine even when the audio did not.
Side channels. Sync features count too. In InsertKit, snippets, clipboard history, custom vocabulary, and API keys sync to your account. If your vocabulary list contains an unreleased product codename, that word list is synced, even if every audio clip stays local.

What InsertKit stores is worth knowing precisely: cloud voice history in Settings → Usage covers the last 30 days and is text only, no audio, with a Clear button. Local voice history stays on the device, and setting its maximum to 0 disables it.

So "private" is not a property of a model. It is a property of the whole path.

2. Latency: where the milliseconds actually go

Local is not always faster. Rough breakdown:

Cloud: upload time + queueing + inference on fast hardware + download. On a good connection, short utterances can come back very quickly, because providers run large models on serious GPUs.

Local: zero network, but inference runs on your CPU or GPU. A small model on a modern laptop is responsive. A large model on an older CPU can take noticeably longer than the time you spent talking.

Two details that matter in practice:

Model loading. Expect the first transcription after loading a large model to be slower than the ones that follow.
Long dictation. If the tool waits until you finish a three-minute ramble before transcribing, you wait for all of it at the end. InsertKit splits long speech into chunks at natural pauses and transcribes them while you keep talking, which hides much of that delay locally and in the cloud.

3. Accuracy: benchmark your own voice

Published word error rates come from benchmark datasets, not from your accent, your mic, or your jargon. Ten minutes of testing beats any leaderboard.

Here is a quick, tool-agnostic way to compare Whisper model sizes with whisper.cpp:

git clone https://github.com/ggml-org/whisper.cpp
cd whisper.cpp
cmake -B build
cmake --build build -j --config Release

for m in base small medium; do
  sh ./models/download-ggml-model.sh $m
done

# Convert a 60-second recording of you reading real work text to 16 kHz mono WAV
ffmpeg -i sample.m4a -ar 16000 -ac 1 -c:a pcm_s16le sample.wav

for m in base small medium; do
  /usr/bin/time -p ./build/bin/whisper-cli -m models/ggml-$m.bin -f sample.wav -otxt -of out-$m
done

Then score each output against what you actually said:

# pip install jiwer
from jiwer import wer

ref = open("reference.txt").read()
for m in ["base", "small", "medium"]:
    hyp = open(f"out-{m}.txt").read()
    print(m, "WER:", round(wer(ref, hyp), 3))

Use real material: a commit message, a ticket description, a paragraph full of service names. Generic sentences flatter every model.

A few patterns you will likely see:

Bigger models handle accents and noise better, at the cost of speed and memory.
Jargon fails across all sizes. That is a vocabulary problem, not a model-size problem.
Whisper can hallucinate on silence or noise, producing text nobody said. Trimming silence and using a decent mic reduce it.

For jargon, a correction layer helps more than a bigger model. InsertKit's Custom Vocabulary has word hints plus "heard as → write as" corrections, like post gres → Postgres, and corrections run before and after formatting so the LLM cannot undo them.

The decision, simplified

Audio must never leave the machine: local Whisper.
Speed on modest hardware: cloud, or a small local model.
Accuracy on difficult audio: a large local model with a GPU, or a strong cloud engine.
Zero setup: a hosted engine that needs no key.
Air-gapped or offline work: local Whisper plus a local LLM, or formatting turned off.

Many developers end up hybrid: local for anything touching client code or internal docs, cloud for low-stakes chat.

A fully private dictation setup

Here is the setup where audio and text both stay on your machine. Local Whisper is a desktop feature in InsertKit (Windows, macOS, Linux).

Step 1: Local speech-to-text

In the Speech Engine panel, choose Local Offline (Whisper) and download a model inside the app. Sizes go from Tiny (~75 MB) and Base (~140 MB) through Small (~460 MB) and Medium (~1.5 GB) to Large v3 (~3 GB). Use your benchmark results to pick. Small is a sensible starting point on most laptops.

Step 2: A local LLM for formatting

Run a local OpenAI-compatible server. With Ollama:

ollama pull llama3.2
curl http://localhost:11434/v1/models

LM Studio exposes a similar server, by default at http://localhost:1234/v1.

In InsertKit, open Settings → API Keys and add a Custom OpenAI-compatible provider: a name, the base URL (for example http://localhost:11434/v1), a key if your server needs one, and the models (auto-fetched or entered by hand). Then choose that model for Smart Formatting.

Smaller local models format well enough for clean-up. If output gets too creative, add a short custom instruction under Use my own instructions, such as "Fix punctuation and remove filler words. Do not add or change content."

Step 3: Decide what happens when formatting is unavailable

Enable Keep working offline so the raw transcript is pasted if the formatter cannot be reached. Or skip formatting for sensitive sessions and rely on vocabulary corrections.

Step 4: Verify, do not assume

Turn off Wi-Fi (or run nmcli networking off on Linux) and dictate a paragraph into your editor. If text still appears and is formatted, both stages are local. Turn the network back on afterwards, because account sync needs it.

Linux note

Check Settings → General → Linux Dependencies. Typing and pasting rely on tools such as xdotool and wtype, and on Wayland the tips point to wtype or ydotool.

Where cloud still wins

To be fair to cloud dictation:

No local resources. Large models do not eat your RAM or battery during a long build.
Consistent quality on weak hardware.
Language coverage. InsertKit's voice typing covers 100+ languages with auto-detect. If you dictate in more than one, benchmark each on your local model before committing to it.
Mobile. InsertKit's Android app uses hosted or BYOK engines; there is no on-device Whisper there.

If you use the cloud, at least choose deliberately. InsertKit Free needs no key and has a daily limit, Premium uses credits, and BYOK covers providers such as OpenAI, Groq, Deepgram, AssemblyAI, and ElevenLabs.

Wrapping up

Local Whisper is a strong default for private work, but privacy depends on the full path, latency depends on your hardware, and accuracy depends on your own voice. Benchmark with real text, add vocabulary corrections for your stack, and verify your setup with the network off.

If you want to try this exact setup, the desktop builds are at insertkit.com/download.

Dictating Code Comments and Commit Messages: A Practical Hands-Free Setup

Al Amin — Sat, 17 Oct 2026 05:18:32 +0000

I do not want to dictate code. Brackets, indentation, and symbol-heavy syntax are a bad fit for speech, and autocomplete already does a lot of that work.

The prose around code is a different story. Comments that explain why, commit messages that someone will read during a painful git bisect, PR descriptions, review replies. That text is often the part we rush, because typing a careful paragraph after an hour of debugging feels like a chore. Saying it out loud is easier, and it usually comes out clearer.

Here is how I set that up with InsertKit, a desktop app (Windows, macOS, Linux) that combines voice typing, text snippets, and clipboard history.

The basic loop

Put your cursor where the text should go: a comment line, the commit message buffer, a PR description box.
Press the voice shortcut (Right Alt by default) and talk.
Stop talking. After a short silence (5 seconds by default, configurable), recording stops and the text is inserted at the cursor.

It works system-wide, so the same shortcut works in your editor, a terminal, the browser, or a chat app. Long explanations are fine too: speech is split into chunks at natural pauses and processed while you keep talking.

Let the Code profile handle formatting

Raw transcripts are messy. With Smart Formatting turned on, InsertKit cleans filler words and punctuation and adapts the style to the app in focus. When the active window is VS Code, Cursor, IntelliJ, Sublime, vim, or a terminal, it uses the Code profile.

Two things happen in that profile:

Output reads like a comment or docstring, not a chatty paragraph.
Spoken identifiers become camelCase or snake_case. Say "this wraps fetch user profile and retries on a timeout" and you get a comment that refers to fetchUserProfile instead of four loose words.

It will not always guess the convention you want, so glance at identifiers before you move on. If you want a specific house style, there is a Use my own instructions option for a custom formatting prompt. Keep in mind it changes formatting generally, not only in your editor.

If the formatter is unreachable, the raw transcript is pasted anyway, so nothing you said gets lost.

Snippets for the boilerplate around the prose

Voice handles the thinking. Snippets handle the structure that should look the same every time. A few I use:

/todo for a TODO tag with my name and today's date, using built-in variables:

TODO({{myName}}, {{date}}):

Type /todo, then press the voice shortcut and say what needs doing.

/pr for a PR description skeleton:

## What changed

## Why

## How to test

## Notes for reviewers

Drop it in, then dictate each section. "Why" is where speaking pays off most.

/commit as a dynamic snippet. On desktop, a snippet can have form fields. I use a Dropdown called type (feat, fix, refactor, docs, chore, test) and a Text field called scope:

{{type}}({{scope}}):

Type /commit in the commit buffer, pick the type, enter the scope, press Enter, then dictate the subject and body.

If you forget a trigger, typing / opens a small autocomplete popup at the cursor with matching snippets.

Press F4 before snippets bite you

Here is the gotcha nobody mentions. Snippets fire the moment the end of what you typed matches a trigger, without waiting for Space. That is great in a chat box and dangerous in code. If you have a /pr snippet and you type a path like /proc/... or a URL segment starting with /pr, it will expand.

Two fixes:

Pick triggers that rarely appear in code or paths. /prdesc is safer than /pr.
Press F4 (Fn + F4 on Mac) to turn the whole snippet system off while you are writing code, and press it again when you switch to prose. A small toast confirms "Snippets disabled" or "Snippets enabled". You can change the key in Settings.

Some apps also use / for their own commands. Under Settings → Snippets → Trigger Prefixes, you can enable a different prefix character for those cases.

Teach it your jargon

Speech engines are trained on everyday speech, not on your stack. Custom Vocabulary fixes that in two ways:

Add word: hint terms like Kubernetes, PostgreSQL, gRPC, or your internal service names.
Add correction: "When heard as" → "Write as". For example "post gres" → "Postgres", "next js" → "Next.js", or "k eights" → "k8s".

Corrections run before and after AI formatting, so the formatter cannot "fix" your spelling back. Vocabulary syncs to your account, so it follows you to another machine.

Picking an engine: hosted, BYOK, or fully local

You can start with InsertKit Free, which needs no API key and has a daily limit. For more control there are a few options worth knowing.

Bring your own key. Settings → API Keys accepts keys for providers such as OpenAI, Groq, OpenRouter, Deepgram, AssemblyAI, and ElevenLabs for transcription, plus chat providers for formatting. Adding a key assigns sensible defaults. A Groq key, for example, sets whisper-large-v3 for speech.

Local Offline (Whisper). On desktop you can download a Whisper model inside the app, from Tiny (~75 MB) up to Large v3 (~3 GB). With this engine selected, audio is transcribed on your machine and does not leave it. Start with Small or Base on a laptop and move up if accuracy is not good enough for your accent and vocabulary.

Custom OpenAI-compatible endpoint. Formatting uses a chat model, and by default that may be a cloud model. If you want the text to stay local too, add a custom provider pointing at a local server such as Ollama or LM Studio: set a name, the base URL, a key if needed, and fetch or enter the model list. Pair that with Local Offline Whisper and the whole pipeline runs on your machine.

If your team has rules about what can leave your machine, that is the setup to look at. Or turn Smart Formatting off and rely on vocabulary corrections alone.

Linux notes

On Linux, check Settings → General → Linux Dependencies. InsertKit relies on tools such as xdotool, wtype, and maim to type and paste. On Wayland, the tips point to wtype or ydotool.

A couple of extras

Voice Assistant: say "hey ik draft a short changelog entry for a fix to session expiry handling" and a draft is typed at the cursor. Treat it like a junior's first draft.
Clipboard history: Ctrl + Shift + Z opens a small popup with recent copies, snippets, and favorites. Handy for juggling an error message, a ticket ID, and a stack trace line while writing a commit.

What does not work well

Open-plan offices. Dictation is awkward with people around.
Dictating code itself. Stick to prose.
Skipping review. Read every comment before you commit it.

If you want to try this workflow, the desktop builds are at insertkit.com/download. My suggestion: set up /todo, /commit, and a few vocabulary corrections, then dictate every commit body for a week and see if your history reads better.

DEV Community: Al Amin

TextExpander Pricing vs Cheap Alternatives: A Developer's Cost Breakdown (Free, Open Source and Paid)

What is a text expander?

TextExpander pricing in 2026

What the free plan means for developers

Cheap and free TextExpander alternatives

espanso (free, open source)

AutoHotkey hotstrings (free, Windows only)

Editor snippets (free, editor only)

Text Blaze (freemium)

InsertKit (free tier plus a low-cost plan)

Side-by-side comparison

How to choose without overpaying

Trying a cheaper option

FAQ

How much does TextExpander cost?

Is there a free version of TextExpander?

What is the cheapest TextExpander alternative?

Is there a TextExpander alternative for Linux?

Can a text expander work in the terminal and IDE?

Do I need a text expander if my editor has snippets?

Text Expander With Voice Typing: Why I Keep Snippets and Dictation in One App

What is a text expander with voice typing?

Why snippets and dictation belong together

Three ways to get a text expander with voice typing

Option 1: A text expander plus separate dictation

Option 2: A dictation app that has snippets

Option 3: One app built for both

Text expander with voice typing: a quick comparison

How my combined workflow looks in practice

When this setup is not the right fit

How to set up a text expander with voice typing in InsertKit

FAQ

Can a text expander do voice typing?

Can I use voice commands to insert text snippets?

Does voice typing work offline?

How many languages does voice typing support?

Is a dictation app with snippets the same thing?

How to Set Up Paid Client Calls with TidyCal (One-Time $29 Lifetime Deal)

Why a booking tool for freelance work

Step 0: Pick the right tier

Step 1: Connect your calendars

Step 2: Set availability, buffers and limits

Step 3: Create your booking types

Step 4: Turn on payments

Step 5: Make the page and emails yours

Step 6: Collect reviews automatically

Step 7: Wire it into the rest of your stack

Where to put the link

What reviewers on AppSumo mention

Things to double-check

Wrap-up

Text Expander With Multiple Variations: Canned Replies for GitHub Issues That Don't Read Like a Bot

The problem with one canned reply per situation

What snippet variations are: multiple replies behind one shortcut

How I structure variations for issues, reviews and community questions

Issue triage: /repro

Code review: /review

Community questions: /faq-install

Making a picked variation still sound like you

Variations vs. dynamic snippets: pick one per snippet

Where the shortcut works

How this compares with other ways of keeping canned replies

Setting up your first variation snippet

FAQ

What is a text expander with multiple variations?

Does InsertKit pick a variation at random?

Can I use snippet variations for canned replies on GitHub issues?

Can one snippet have both variations and fill-in fields?

Do variations work on Android?

What if an app already uses the slash key for commands?

Voice Typing on Linux: How to Dictate Into Any App on X11 and Wayland

What "voice typing on Linux" actually requires

X11 vs Wayland: why inserting text is the hard part

Local Whisper vs cloud speech-to-text

A GUI setup: voice typing on Linux with InsertKit

1. Install and check dependencies

2. Pick a speech engine

3. Dictate

4. Let formatting match the app

Issue triage: `/repro`

Code review: `/review`

Community questions: `/faq-install`