Spoken snippets

Create a snippet#

1. Open Settings → Vocabulary → Snippets.
2. Write the trigger, then =>, then the text to insert.
3. Click Save.
4. Start a dictation and say “insert” followed by your trigger.
5. Release the shortcut and review the inserted result.

project link => https://example.com/project
support reply => Thanks for the report. We will take a look.

For the first example, say “insert project link.” Store project link as the trigger—not insert project link. The word “insert” is added by the matching convention.

Use line breaks#

Each snippet occupies one line in the Settings box. Write a literal backslash followed by n where you want a line break in the inserted text:

my signature => Alex Morgan\nCustomer Support\nhttps://example.com
bug template => Summary:\nSteps to reproduce:\nExpected result:\nActual result:

Saying “insert bug template” inserts the saved layout with actual line breaks. Multiline results use paste delivery even if TypeUnicode is selected. The receiving app decides how a pasted multiline block is interpreted.

The snippet editor also supports an escaped backslash. When editing Windows paths by hand, check the saved text carefully so a backslash followed by n is not mistaken for a line-break instruction.

Make triggers distinctive#

Choose a short phrase you can say clearly and that is unlikely to occur after “insert” in ordinary speech. Longer matching triggers are processed before shorter ones. Keep similarly named snippets easy to distinguish.

A trigger only works when the recognized text contains the expected phrase. If it does not expand, inspect Heard in History. A misspelling of the trigger can explain the failure; adding an unrelated replacement later in the pipeline is not the same as fixing what the snippet matcher sees.

Snippets and cleanup#

Expansion uses the saved text rather than asking a model to invent the passage. If a dictation expands a snippet, that entire dictation bypasses the Claude rewrite step. This protects prepared text such as a link or signature from stylistic rewriting.

Local replacements and spellings still run after expansion. Avoid rules that would also match and alter words inside your saved snippet. Caret fitting and the destination’s paste behavior can also affect the surrounding insertion.

What snippets do not do#

Snippets are static saved text. They do not evaluate variables, fetch a live date, call an API, fill interactive form fields or run a script. Saying a trigger inserts its stored text into the current destination.

Do not store passwords or API keys as convenient spoken snippets. Vocabulary files are ordinary local data and exports are readable JSON. Use a password manager for secrets.

Snippets travel with the main vocabulary’s import and export. Export before replacing your collection with another file.