Talon is not a dictation app, and that is the point

If you need to operate a computer without a keyboard, install Talon and stop reading. It is free to download, it runs on three operating systems, and it does a job this app does not attempt in any form. Its own site leads with four capabilities — "Voice Control · talk to your computer", "Noise Control · click with a back-beat", "Eye Tracking · mouse where you look" and "Python Scripts · customize everything" — and there is no row in any table below where Coii VoiceInput competes with those.

What follows is for the reader who arrived at this search for a narrower reason: they want to stop typing text, and Talon turned out to be a much larger commitment than they were expecting. That is a real and common situation, and it has a different answer.

What Talon actually is

A control layer. You speak, and the machine does things — moves the cursor, clicks, switches window, selects a word, deletes a line, runs a command you defined. Dictating prose is one of the things it can do, and it is not the headline. The headline is that the keyboard and the mouse both become optional.

The Python scripting is not a bonus feature either; it is how the system is meant to be used. Commands are defined, shared, and tuned to the applications you personally live in, and there is a large community doing exactly that. The noise control — clicking with a sound rather than a word — and the eye tracking integration are the parts that have no analogue anywhere else in this category.

On availability: their download page offers macOS, Linux (X11) and Windows, with a standard installer and a portable zip for the last. Their public changelog lists 0.4.0 with the date "Jul 24, 2023", and beta builds are published separately — the most recent beta page on their own site is headed "Beta (Dec 16, 2025)". Their site publishes no price; it promotes a Patreon offering "early feature access" and "high priority support", and it points at documentation and a Slack for anything else. Check it yourself before you plan around any of that.

Who should be using Talon rather than this

Stated properly, because this is the section that decides whether the rest of the page is relevant to you at all.

Anyone who needs to use a computer without their hands. Not "types less" — needs not to type. A dictation key covers the text and leaves the navigation, the selection, the clicking and the shortcuts exactly where they were, which is most of what a keyboard is used for. Talon covers all of it.

Anyone whose work is mostly editing rather than composing. "Select that line", "delete the last three words", "go to the top of the function" — a dictation key cannot express any of those. It writes new text and has no vocabulary for changing existing text.

Anyone on Windows or Linux. This app is macOS only. There is no argument to make here.

Anyone who wants to build their own system. If the idea of writing scripts that shape how your computer responds to your voice sounds like a good weekend rather than a chore, you will get more out of Talon in a month than out of any fixed-behaviour tool in a year.

None of that is faint praise. Talon is the more ambitious and more capable piece of software, it costs nothing to download, and the honest recommendation for a large share of the people reading this is to go and try it first.

What this app is instead

One key, one behaviour. Hold ⌥ Space, say the sentence, let go, and about half a second later the words are in the field you were already typing in. There is no window to open, no mode to enter, no command language, and nothing to configure beyond the hotkey.

That narrowness is deliberate and it is what you are choosing. There is no learning curve to speak of: the whole of the manual is "hold the key while you talk". There is nothing to maintain, no script to update when an application changes, and no configuration that can drift. Somebody installs it on a Tuesday and by Thursday has stopped thinking about it.

The trade is obvious. It will never do a thing you did not already know it does, and there is no path from "I wish it also…" to actually having that.

The table, such as it is

Seven clear rows to Talon. This is the least competitive table in the library and it should be, because the two products are answering different questions. The only rows on the left that matter are the last three and the price, and they only matter if the question you are answering is the narrow one.

The one place they overlap

Prose. Long, ordinary, unstructured text — the email, the paragraph, the message, the comment. Both tools will put it on the screen, and this is where a reader genuinely has to choose.

Two things push a heavy prose writer towards a dedicated dictation key.

The first is that a control system is optimised for commands, and commands and prose want opposite things from a recogniser. A command vocabulary is small, fixed and needs to be recognised with near-certainty; free prose is open-ended and needs to be recognised loosely and punctuated sensibly. Systems that do both carry a mode boundary somewhere, and mode boundaries are a thing you have to remember while composing a sentence — which is exactly when you have no attention to spare.

The second is friction per press. When most of your dictations are under five seconds — a reply, a commit message, a line in a chat — the cost of entering and leaving a mode is comparable to the cost of typing the thing. A key you hold has no mode at all, and that is why the press count ends up so much higher.

What a dictation key can promise that a control system cannot

Two behaviours, and they are both about failure rather than capability.

The words are written down first. Release the key and the row is in your local history before the rest of the sequence runs. Everything that could go wrong afterwards — a slow engine, an application that quit, a paste that lands oddly — happens after the sentence is already saved.

The destination is fixed at key-down. Start speaking into a text field, and that field is where the text goes, even if focus moves while you are still talking. Anything that watches the front window at the moment of insertion has to get this right some other way, and most tools do not describe how.

Neither is a claim about accuracy, speed or intelligence. They are claims about what happens on the bad day, which is the only kind of claim worth making about a tool you use sixty times a day.

The commitment, described fairly

The reason a lot of people search for a Talon alternative is not that Talon disappointed them. It is that they installed it, read the documentation, saw how much of it there was, and realised they had picked up a system rather than an app. That reaction deserves to be described accurately rather than used.

Talon is configured in Python, and the community maintains large sets of commands that people adopt and then modify. That is a strength — it is how a tool becomes genuinely yours, and it is why people who use it seriously get results no fixed product can match. It also means the first useful week involves reading, choosing a starting configuration, learning a command vocabulary and adjusting it to the applications you actually use. Anybody who has set up a tiling window manager or a serious editor configuration knows the shape of this exactly: enormous payoff, real up-front cost, and an ongoing relationship rather than a purchase.

Whether that cost is worth paying depends on one question, and it is not a question about software. If you cannot type, it is worth paying, easily, and this page is not going to pretend a $19 dictation key is a substitute. If you can type perfectly well and simply write a lot, the calculation is different, because what you want back is the two hours a week you spend converting thoughts into keystrokes — and spending a weekend to get it is a poor trade you will abandon in February.

The narrow tool is not better. It is cheaper to adopt, and for the narrow problem that is the whole of the argument.

Two weeks, one each

If you are genuinely undecided, the test is not a feature comparison. It is two weeks, and it has a specific shape.

Spend the first week with Talon and its default or community configuration. Do not try to become fluent — that is not what you are measuring. Count two things: how often you reached for a command and could not remember it, and how often you used it for prose rather than control. If the second number is high and the first is annoying you, your problem is dictation and you have been using a control system to solve it.

Spend the second week with a held key and nothing else. Count the presses. If you end that week above about forty a day, mostly on short things, then a dictation key is the tool that matches your actual behaviour, and the interesting question is only which dictation app to buy. If you end it frustrated because what you wanted was to move the cursor, select the paragraph and jump to the next file without touching anything, then the answer was Talon all along and the setup cost is worth paying.

One rule for the test: change one of the hotkeys before you run both. Two tools listening for the same key produces intermittent, confusing behaviour, and an intermittent fault will bias a two-week evaluation more than any real difference between the products.

Why the narrow one stays narrow

It is fair to ask why a dictation app would not simply add commands. "Delete that sentence" is not an unreasonable feature request, and plenty of products in this category have said yes to it.

The answer is that the moment an app interprets what you said instead of writing it down, you have to know which mode you were in when you spoke — and that knowledge has to be present in the half second when you are also composing a sentence. Say "new paragraph" into a product that takes commands and you may get a line break; say it into this one and you get the words "new paragraph", because that is what you said. The second behaviour is duller and it is completely predictable, and predictability is the property that lets a tool disappear.

There is a version of this product with commands in it. It would be more capable, more impressive in a demo, and worse at the one job, and it would be competing with a mature system that does the same thing better and for free. Not building it is the decision that makes the rest of the page true.

Cost, honestly, on both sides

Talon's site publishes no price. It offers direct downloads and a Patreon with "early feature access" and "high priority support". What that means for you on the day you read this is a question for their site rather than for ours, and guessing at it here would be exactly the kind of stale number that makes comparison pages worthless.

Coii VoiceInput is $19 once. Three devices on the licence. Updates included, nothing renews, and the trial is thirty days of the entire app with no card and no account. That is the whole commercial story and there is no tier above it.

Against a subscription that arithmetic is the headline — see Wispr Flow or Willow, both priced monthly. Against a free download it is not an argument at all, and the reason to pay is the behaviour above rather than the money.

Running both

This is a supported and sensible configuration, and it is what a lot of the people reading this page will end up doing: Talon for moving around, selecting, clicking and editing, and a held key for the moments when what you need is a paragraph rather than a command.

One rule makes it work. Do not let both listen for the same keypress. Two tools bound to one key is the single configuration that reliably breaks, and the symptom — sometimes it works, sometimes it does not, sometimes both fire — will look like a bug in whichever of the two you happen to distrust. Change one of them first, before you have any opinions to be misled by.

Beyond that, they do not collide. One is a control layer and the other is a text insertion; they are not competing for the same job even when they are running at the same time.

What neither of them does

Neither records or summarises a meeting. Neither transcribes an audio file you already have. Neither is a substitute for a decent microphone — a laptop mic in a shared room will cost you more accuracy than any difference between any two products in this category, and fixing that is cheaper than either purchase.

And neither of them is a medical device or a treatment for anything. They are input tools. Whether a given one helps with a given situation is a question for you and, if it is that kind of question, for someone qualified to answer it.

Which to install

Talon if you need the machine operated by voice, you are on Windows or Linux, you want to script your own environment, or the reason you are reading this is that typing is not merely tedious but not an option. It is free to download and it is the more serious tool.

This one if what you want is to stop typing text specifically, on a Mac, with no system to learn and nothing to maintain — and you would like the words written to disk before anything can lose them. Thirty days of the whole app, no card, no account.

If neither fits: Apple Dictation is already on your Mac and costs nothing, Murmur is free and open source, VoiceInk is a larger paid Mac app, and if you came here from the Windows world, what happened to Dragon on the Mac is the page that explains why your search went nowhere.