The Talon community command set is a git clone into your user directory

help active is the way into everything else

The most useful thing in this repository is not a command but a discovery mechanism. Running help active displays the commands available in the active, frontmost application, and the set of commands changes depending on the application or even the window title. From there you can move through the help by voice, using the displayed numbers, so help one one opens the item numbered 11 and help eleven does the same thing. Button titles that do not start with a number work too, which is why help next shows the next page of contexts.

The help machinery lives in two files, core/help/help.talon and core/help/help_open.talon, and the search side is just as direct. Saying help search tab displays every tab-related command, and help search help does the same for help itself. To jump straight to a context, you use the name displayed in the help window, which is derived from the .talon file name, so help context symbols and help context visual studio both work.

There is also a running log. The command history toggles a display of recent voice commands, which is the fastest way to find out whether the machine misheard you or whether a command simply does not exist in the current context.

The alphabet and the key map live in two readable files

The core of the command set is plain text you can inspect before you start speaking. The alphabet is defined in a Talon list file, core/keys/letter.talon-list, and the key commands are defined in core/keys/keys.talon. Say help alphabet to open a window displaying the alphabet, and the example given is to say air bat cap to insert abc. help close closes that window.

Modifiers are spoken as separate words. help modifiers lists them, and shift air presses Shift plus A to type a capital A. On Windows the documented examples are control air to select all, and super-shift-sun to trigger the screenshot application on Windows 10 and 11, with escape to leave it. On Mac, command air selects all and control shift command 4 copies a screenshot of the selected area to the clipboard. The documentation notes that the order of the modifiers does not matter, which matters when you are trying to remember a shortcut under pressure.

Symbols are split in two places. Single symbols are defined in core/keys/symbols.py, so control colon presses that key, while multi-character punctuation such as ellipses live in plugin/symbols/symbols.talon. Any modifier, symbol, alphabet letter, number or function key can be combined into a shortcut, and press control taps the Control key on its own.

Formatters decide whether your punctuation survives

Formatters are the part of this command set that most directly changes how your output reads. They insert words with a consistent capitalisation and punctuation style, and help format displays the available formatters with the example output each one produces when followed by one two three.

The difference between the two families is the part worth remembering. Prose formatters, marked with an asterisk in the help window, preserve hyphens and apostrophes. Non-prose, or code, formatters strip punctuation instead, which is how a variable name ends up valid. Saying snake hello world inserts hello_world, and chaining formatters works too: dubstring snake hello world also produces hello_world, since the later formatter wins on the shape of the string.

Basic editing commands live in core/edit/edit.talon, where undo that and redo that are the defaults and paste that, copy that and cut that cover the clipboard. The suggested path is to learn the alphabet first, then the keys, symbols, formatters, mouse and edit commands, and only after that to try moving text between two windows.

Installing means cloning into the Talon user directory

On Linux and Mac the documented install is a clone into the user directory Talon reads.

cd ~/.talon/user
git clone https://github.com/talonhub/community community

On Windows the same two steps run in a command prompt, with a different base path.

cd %AppData%\Talon\user
git clone https://github.com/talonhub/community community

Using git is recommended rather than downloading a zip and extracting it, because the documentation says the zip route makes it harder to keep track of changes you make to your own copy of the files. That is the real argument for the clone: the directory is a working copy you can modify, diff and update, and a change you make to a .talon file is a change you keep.

Before any of that, the prerequisites are Talon itself, a machine running Mac, Windows or Linux, and a speech recognition engine. The project recommends Talon's built-in Conformer, described as a wav2letter engine, and also allows Dragon NaturallySpeaking on Windows or Dragon for Mac, with the warning that Dragon for Mac is discontinued and its use deprecated.

Eye tracker commands ship even when you have no eye tracker

The command set includes commands for working with an eye tracker, and the documentation makes a point of saying that an eye tracker is not required to use the repository. That distinction matters for anyone reading the file list and wondering whether they need extra hardware: they do not, and the eye-tracking commands simply sit unused until the hardware appears.

The repository is more useful alongside other Talon projects than on its own, and the documentation names them. Cursorless is listed for programming and text editing, Rango for browser navigation, and gaze-ocr for cursor control that combines eye tracking with text recognition. AXKit is listed for native OS accessibility integration and is marked macOS only. There is also a pointer to a collection of other user file sets.

The layout supports that composition. The top level holds core, plugin, apps, lang, tags and test directories, along with a settings.talon file, a migration_helpers directory, and text documents named BREAKING_CHANGES.txt, CONTRIBUTING.md and PRACTICES.md. The project configuration targets Python 3.11 for linting and points pytest at a stub directory, so the Python in the repository is treated as a real test surface rather than a set of loose scripts.

A rename with a migration path, and no release history

The repository was originally called knausj_talon, named after its original creator, and the documentation keeps that history in the open. A renamed project with a changed command vocabulary is exactly the situation where users lose their muscle memory, so the presence of a BREAKING_CHANGES.txt file at the top level, alongside a migration_helpers directory, is a meaningful signal about how the transition was handled. The documentation itself does not walk through those migrations, so a user upgrading from an older copy has to read those two places directly.

The other fact worth stating plainly is that the project publishes no GitHub releases. There is no version to pin, no changelog on the release page and no upgrade path spelled out in the documentation. The last push was on 2026-10-20, so the main branch moves, and a user who clones and later pulls gets whatever changed, including command renames. The licence is MIT, which is permissive, and the documentation asks that community-generated documentation for Talon itself lives at talon.wiki.

Editorial conclusion

talonhub/community is the right starting point for a Talon user who wants the community command vocabulary instead of writing their own, and the git install path is simple enough to reverse by deleting one directory. It is the wrong choice if your machine can only run Dragon for Mac, since that path is marked discontinued and deprecated, or if you need an internationalised interface, which the Talon web client provides and this command set does not. Before you commit, open help active on a fresh install to see which commands the community set registers in your applications, and check that your speech engine is one the project still supports.

Frequently asked questions

Official sources

1. Issues
2. License: MIT
3. README
4. talonhub/community on GitHub