Cloud providers

Add a key only for the services you use. Your audio is sent to the service you pick.

Sort by

Local models

Speech recognition that runs on this Mac: your audio stays here.

Sort by

Accuracy is the share of words right on the FLEURS English test; speed is measured on a reference laptop (Handy models benchmark). Your own numbers are in Performance.

Performance

Usage

of audio transcribed
What that adds up to
versus typing it at 40 words a minute
Words per weeklast 8 weeks
After transcription

Dictionary

How the dictionary works

A short guide to fixing the words your speech model gets wrong.

What it's for

Every speech model has words it keeps getting wrong: names, products, technical terms. Your dictionary remembers those mistakes and fixes them in each new dictation, before the text reaches you.

How an entry works

An entry pairs what the speech model writes with the words you might have meant. Say it often writes “cloud” when you said “Claude”. But sometimes you really mean a cloud. So the entry keeps both words:

cloud → Claude, an AI assistant you ask to write or code
cloud → cloud, internet storage and servers

In “Ask cloud to draft the reply”, Entune writes Claude. In “The backups are in the cloud”, it leaves cloud alone. It chooses from the surrounding words, which is why each word has a short description: write what the thing is and what it goes with.

Each word is defined once and shared by every entry and every speech model that uses it: “clawed” → Claude and “cloud” → Claude name the same Claude. An entry lists only the words its heard text was actually used for, and the heard text itself when that is a real word.

Getting suggestions

Entune can build the dictionary for you. A suggestion model, the language model you choose with its key in Settings, reads what your speech model wrote and suggests entries for the words it gets wrong. For the entries those transcripts show, it also suggests more words a heard text was used for, clearer meanings, and removals. It reuses the words already in your dictionary instead of defining them again.

Get suggestions is the simple path: it reads up to 300 of your speech model's newest transcripts not yet used by suggestions you applied; a run you discard or stop uses none.

Reusing earlier transcripts

Each transcript is read once: after you apply a run's suggestions, the next Get suggestions reads only what you dictated since, so you don't pay twice for the same text. Under Advanced, Choose a span reads them again. The timeline shows every transcript of this speech model, oldest on the left, with the ones used before marked under the line; drag the handles to choose how much to read.

Reuse them when the earlier suggestions no longer stand for what those transcripts can teach: you cleared or rebuilt your dictionary, you chose a stronger suggestion model or a higher reasoning effort, an update improved how Entune suggests, or an earlier run's suggestions were poor. Reading again costs tokens again. Entries already in your dictionary are shown to the suggestion model beside the transcripts they occur in, so it improves them instead of adding them twice.

Learning from audio

The ⋯ menu learns from audio instead of transcripts, from one of three sources:

Your other models' recordings are recordings already in Entune that this speech model hasn't transcribed. Another dictation app: Import copies the audio that app keeps on this Mac into Entune's data folder; its transcripts are never copied and its files stay as they are. Importing again adds only what is new. An audio folder: choose a folder of recordings of you talking, such as meetings or voice notes, in WAV, MP3, M4A, FLAC, OGG or WebM; each file is copied once.

The hours and minutes are recorded audio: the length of the recordings you choose, not how long the run takes. Entune first transcribes that audio with your speech model, which a cloud provider charges for, then the suggestion model reads the new transcripts. What happens, under the timeline, shows both steps and their estimates. The timeline runs oldest on the left; drag the handles to choose how much to use, and each edge snaps to whole recordings. An hour or two of recent audio gives quick results.

Time and settings

Text goes to the suggestion model in parts, one after another, because each part builds on the entries found so far. With audio, parts start as soon as enough is transcribed, while the rest is still transcribing. Cloud speech models transcribe several recordings at a time; a local model takes one at a time.

Reasoning effort is the level the suggestion model's provider names, from minimal to xhigh. Higher effort reasons longer and usually finds more; high is the default. A provider without a level maps it to one it has.

The estimate uses what Entune has measured: your speech model's transcription times, and the time per part of earlier runs with the same suggestion model and effort. A combination not used before says so.

Sometimes a reply starts and then sends only blank space. Entune stops it within a minute or two and tries that part again, three attempts in all. A ChatGPT plan also ends any single reply at about 15 minutes. If a part fails all its attempts, or runs past a time or length limit, Entune stops and keeps the finished parts. Choose a lower reasoning effort, or less audio, and press Continue: it picks up where it stopped. Transcripts made so far are kept for Continue while Entune stays open.

Reviewing suggestions

Suggestions open in a panel beside your dictionary, grouped into new entries, changes, removals and clearer meanings. Edit any of them, leave out the ones you don't want with ×, and apply the rest in one step. Nothing is saved until you apply. Dictation keeps working the whole time; only editing the dictionary waits until you apply or discard.

Each speech model makes its own mistakes, so suggestions are kept for the speech model chosen when the run starts.

Pinned and learned entries

Learned entries are used only with the speech model they were learned for. Pin an entry to use it with every speech model; pinned entries are yours and suggestions leave them as they are. A pinned entry is used instead of a learned one with the same heard text. Words aren't pinned: each is shared by every entry that uses it. Pinning doesn't make an entry win: Entune still reads the sentence.

Adding an entry yourself

Choose Add word and fill in one line: how it's written, what the speech model hears (several, separated by commas) and what it is. Each heard text becomes its own entry. For several words, a spelling kept as written, or always replacing, open the full editor from the link under that line. Edit on an entry opens the same editor; Delete word removes a word from every entry that uses it.

Your coding agent can do this for you: connect it under Settings › Integrations and ask it to set up your dictionary.

Edit entry

One heard text and the words it can stand for. A word is shared by every entry that uses it.

Get suggestions

What it learns is kept for this speech model.

General

Appearance

Theme
Follow the system, or fix one.
Text size
Scales the whole window. ⌘+ ⌘− step it, ⌘0 resets.

Shortcuts

Hold-to-talk
One key. Records while held, release to stop.
Hands-free
A combination. Press to start, again to stop.
Cancel dictation
Discard the active shortcut recording.

Speech recognition

Corrections & formatting

After speech recognition, Entune can fix known mistakes and tidy the text. A decision model makes each choice: it answers questions about the text and never writes any.

Decision model
Needed for the steps below. Choose where the decisions are made.
The original transcript is always kept in History.
Advanced: waiting and retries
All three steps share the maximum wait, including retries.

Dictionary setup

Suggestion model
Writes dictionary suggestions when you choose Get suggestions on the Dictionary page. It reads the transcripts it learns from. Dictation and editing work without it.
No model

Integrations

Your agent

Connect a coding agent over MCP and it runs Entune for you: it sets up the models, builds your dictionary from the recordings on this Mac, keeps it accurate, and tells you when it's ready. What it reads goes to your agent's model provider.
MCP endpoint
On this machine only, while Entune runs.
Claude Code
Run once in a terminal. Other agents that speak MCP over HTTP take the endpoint above.

Local API

Apps and agents you dictate to can send corrections you have confirmed. Each one is added to your dictionary as a pinned entry.
Endpoint
HTTP on this machine only. Nothing else is exposed.
Example request
Send only what the person confirmed, whole words or phrases, never guesses.

Received corrections

Newest first. Each one is already in Pinned; remove it there if it's wrong.

Tracing

See exactly what the suggestion model received and answered: each dictionary-suggestion request and reply goes to Langfuse, transcript text included. Off until both keys are saved. Get keys

Data & privacy

What Entune keeps on this Mac, and what it sends elsewhere.

What leaves this Mac

Speech recognition
Audio goes to the cloud service you pick. Models on this Mac keep it here.
Corrections & formatting
When on, transcript text, the words in question and relevant dictionary meanings go to TypeSafe if Jev is your decision model, and to OpenAI or Perplexity if you chose theirs. With Laya they stay on this Mac.
Dictionary suggestions
When you ask, transcripts and your dictionary go to your suggestion model. Transcripts made only for a suggestion run are not saved by Entune.
Tracing
Off unless you save Langfuse keys under Integrations. Then each suggestion request and reply, transcript text included, also goes to the Langfuse host you set.
Each service's own retention rules apply.

Your data stays yours

No expiry
Entune never automatically expires or deletes your saved audio or transcripts. This includes audio imported to build dictionaries. Saved files are kept locally.
Original audio
A ZIP of all recordings and imported dictionary audio. Large exports can take a while to prepare.
Export audio
Transcripts
JSON with saved text, raw transcripts, models, dates and every attempt. Transcripts used only to build a dictionary from imported audio are not saved.
Export transcripts
Exports are created on this Mac. Saved API keys and settings are excluded.

Start over

Delete all Entune data
Recordings, transcripts, the dictionary, settings, API keys and downloaded models on this Mac. You can export first.

How corrections and formatting work

What happens to a transcript after speech recognition.

The steps

The steps you turned on all run at once on the transcript from the speech model: your dictionary, fillers, and paragraphs and bullets. Their changes are applied together. The original transcript is always kept in History, and you can copy it from there.

Your dictionary

For each word your speech model often gets wrong, the decision model reads the sentence around it and picks the meaning that fits: “Ask cloud to draft it” becomes “Ask Claude to draft it”, while “the backups are in the cloud” stays. Entries set to always apply skip that choice. When no meaning can be chosen, the words stay as they were.

Fillers and formatting

Sounds such as “um” and “uh” are removed, and repeats such as “like like” become one, where the decision model hears hesitation; a sound that carries meaning, quoted text and code are left alone. Paragraph breaks and bullets are added only where the dictation clearly has them, and every word is kept.

Waiting and failures

The steps share one time limit, including retries; you can change it under Advanced. If a step fails, the others are still applied, and History says which one failed.

The decision model

A decision model answers questions about the text and never writes any. For fillers and formatting it receives the whole transcript; for your dictionary, the passage around each word in question with the meanings that could apply, including your personal usage notes. It never receives audio.

Four are available. Jev, from TypeSafe, runs in the cloud on your own TypeSafe key, so the text goes to TypeSafe even when speech recognition runs on this Mac. OpenAI's and Perplexity's run in the cloud on your own API key with them, so the text goes to them in the same way. Laya, an open-weight model from Convai Innovations, runs on this Mac for English, so the text stays here. Its engine is installed once in Terminal, and Entune runs it only while Laya is chosen and a step is on. Laya reads a limited amount of text per question, so in a long dictation its filler and paragraph decisions see only part of it.

How your data works

What stays on this Mac, and what goes where.

On this Mac

Entune keeps its data in one folder on this Mac: your recordings, every transcript (the speech model's original and each processed version), your dictionary, settings, and the API keys you enter. Keys are stored in Entune's database, not in the macOS keychain. Entune has no accounts and sends no usage data.

Audio you import from another dictation app or a folder is copied into that folder; your original files are not changed or moved.

Speech recognition

With a cloud speech model, such as AssemblyAI, Groq or Soniox, each recording's audio is sent to that service to be transcribed. With fast mode, parts of it go to that service while you are still speaking. Transcribing again with another model sends the audio to that model's service.

With a model on this Mac, such as Whisper or Parakeet, audio stays here. Downloading one fetches the model from Hugging Face.

Corrections and formatting

When Apply your dictionary, Remove fillers, or Paragraphs and bullets is on, transcript text goes to your decision model: the whole transcript for fillers and formatting, and for your dictionary the passage around each word in question with the meanings that could apply. Audio is never sent.

With Jev, the text goes to TypeSafe, and with OpenAI or Perplexity to them, even when speech recognition runs on this Mac. With Laya, it stays on this Mac; its first start fetches the model from Hugging Face.

Dictionary suggestions

Only when you choose Get suggestions, the transcripts it reads and your dictionary are sent to your suggestion model (Anthropic, OpenAI through an API key or a ChatGPT subscription, Google Gemini, Groq or Mistral). With Learn from audio, the chosen audio is first transcribed by your speech model as above. Transcripts made only for a suggestion run are not saved.

Tracing

Off unless you save Langfuse keys under Settings › Integrations. When on, each dictionary-suggestion request and reply, with the transcript text and dictionary it carries, is also sent to the Langfuse host you set, so you can see exactly what the suggestion model received and answered. Turn off removes the keys and stops sending.

Keeping and deleting

Entune never deletes recordings or transcripts on its own. Exports are created on this Mac and leave out your keys and settings.

What a cloud service keeps, and for how long, is up to that service and your account with it. Deleting data in Entune can't remove copies a service kept, exports you saved, or copies in Time Machine or other backups of this Mac.

Delete all Entune data

This can't be undone.

Everything Entune keeps in its data folder is deleted:

  • Recordings and their audio
  • Transcripts: originals, processed versions and every attempt
  • Audio copied in from other dictation apps or folders
  • Your dictionary, its automatic copies and suggestion progress
  • Corrections received from other apps
  • Settings, shortcuts and saved API keys
  • Downloaded models, for speech and for Laya
  • The backups folder, and the log (emptied)

Not affected: your original audio files, exports you saved, anything a cloud service kept, Time Machine or other backups, and the Entune app itself. Files are deleted the normal way; this is not a secure erase.

Want a copy first? Export audio Export transcripts