The paste can fail. The sentence already didn't need it to succeed

You held the hotkey, said the sentence, let go — and nothing appeared where you expected it. Before assuming the words are gone, know this: Coii VoiceInput writes what you said to its history the moment you release the key, before it asks anything to clean it up or paste it anywhere. A failed paste is a delivery problem, not a loss. This is how to get the sentence back.

Step 1 — open history before you try dictating again

Open Coii VoiceInput and go to its history. Every dictation you have made is there as a row: the time, the app it was aimed at, and the text. Find the most recent one — it will be at or near the top — and that is your missing sentence, whether or not it ever reached the field you were looking at.

Do not re-dictate the sentence yet if you can avoid it — confirm it is in history first, so you are not duplicating something that was captured correctly the whole time.

Step 2 — copy the version you actually want

Each row holds two things: the raw transcript, exactly as you said it, and the processed version, after whatever filters you have on — your dictionary, repeat collapsing, filler removal if you turned it on, punctuation and spacing. Nothing about a failed paste changes which of these was written; both are there regardless. Pick the one you meant to use and copy it from the row.

If you are not sure why the two might differ, or which one you would normally have gotten, what comes out of a dictation and why covers the chain that produces the processed version, and why the raw one is kept alongside it rather than discarded.

Step 3 — paste it manually into the field you meant

With the text copied from history, click into the field you were originally dictating into and paste it (Cmd+V) the ordinary way. This works regardless of why the automatic paste failed, because you are now doing the one part of the process — getting text from the clipboard into a field — that the field controls, not Coii VoiceInput.

If the field genuinely does not accept pasted text at all, which is the case for some password fields and a small number of apps, you will need to type the recovered text manually, reading it off the history row. That is a limitation of the field, not of the recovery — the words are legible on your screen; the only thing that changed is how they get from there into the box.

Step 4 — work out why it did not paste, if it is likely to recur

A one-off failure is usually not worth investigating. If it keeps happening with the same app, it is worth finding out which of two causes you have, because they call for different responses.

The field does not accept pasted text. This is a property of the application, not something dictation can work around. Whether dictation works in password fields covers the most common version of this, and for other apps the tell is that pasting with Cmd+V manually — with no dictation involved at all — also fails.

Focus moved before you released the key. If you switched windows, clicked elsewhere, or a notification grabbed focus while you were still speaking, the text is delivered to wherever focus landed at release, which might be nowhere useful, or might be an app where recovering it looks like a paste that "did not happen" because it happened somewhere you were not looking. Why dictation lands in the wrong app is the fuller version of this, including how to keep it from recurring.

The app uses the clipboard fallback and something interfered with it. A smaller number of apps — Terminal among the most common — receive dictation through a clipboard round trip rather than directly, and in rare cases that round trip can be disrupted. History is unaffected either way, which is the point of writing to it first.

Step 5 — check accessibility permission if this is new

If dictation has generally worked and suddenly stopped landing anywhere, the first thing worth checking is whether Coii VoiceInput still has accessibility permission in System Settings — macOS occasionally revokes it after an update, and without it the app has no way to deliver text into most fields at all, which looks exactly like every paste failing at once. The macOS accessibility API is what this permission actually grants, and re-enabling it in Settings after an update is usually the entire fix.

If you already re-dictated it before checking history

It is a natural reaction: the text does not appear, so you say it again, assuming the first attempt simply vanished. If you did this before reading the steps above, nothing is broken — you will now have two rows in history with very similar or identical text, a few seconds apart. Use whichever one you actually need (usually the second, since it is the one you were paying attention to when you said it) and leave the other. History is a record, not a working document; an extra row from a false start costs you nothing and does not need to be cleaned up.

If the second attempt also failed to paste for the same reason as the first — same app, same field, same cause — that is useful information in itself. It tells you the problem is not a one-off glitch but a property of that particular field, which points you toward Step 4 rather than a third attempt at dictating your way past it.

Building the habit: check history before you assume something is lost

The instinct to re-dictate immediately is the one habit worth changing, because it is slower than the alternative and occasionally produces exactly the duplicate-row situation above. History is sorted by time, so the row you want is almost always the one at the top, and confirming it is there takes less time than re-saying a sentence of any length. Over enough dictations, checking first becomes the default rather than something you have to remember to do.

This is also where the durability guarantee is worth more than it looks like on a single occurrence. A cloud dictation service can genuinely lose a sentence in transit — a dropped connection between your Mac and its servers, a request that times out, a server-side error partway through — because the words have to leave your machine before anything can be done with them at all. Coii VoiceInput's history write happens locally, before the engine is asked anything, so the equivalent failure here is only ever about delivery to a field, never about whether the sentence was captured in the first place. The $19 one-time price does not change that; the architecture does, and it is the same architecture whether you dictated your first sentence today or your ten-thousandth.

What this durability guarantee is actually built on

The reason recovery is this straightforward is the order things happen in. Your transcript is written to history the instant you release the hotkey — before the transcription engine is asked to finalize anything, before any filter runs, before a paste is even attempted. A slow engine, a crashed app, a field that refuses pasted text, or focus landing somewhere unexpected all happen after that write, which means none of them can cost you the sentence itself, only its delivery.

This also means recovery does not depend on being online. History is a local record on your Mac, checked and copied the same way whether or not you have a network connection at all — consistent with the rest of how the app runs: nothing you say is uploaded, the only network traffic at all is fetching the model once, activating your licence, and a clock check at launch, and none of that is needed to open a history row and read what is in it.

Finding the right row in a busy stretch of dictation

The advice above assumes the missing sentence is the most recent row, which is true the great majority of the time — you notice a paste failed within a minute or two of it happening, and the row you want is at or near the top. It gets slightly less obvious on a morning where you have dictated a dozen things into six different apps in quick succession and only later realize one of them never landed.

In that situation the two columns that matter are time and destination app. If you remember roughly when you dictated the missing sentence — "sometime around when I was replying to that Slack thread" — scan for rows around that time first, then narrow by which app each row was aimed at. A row aimed at Slack when you were not using Slack at all that morning is not the one you are looking for, even if the timing is close.

If you remember a distinctive word or phrase from what you said, searching history directly is faster than scanning by eye — you do not need to reconstruct the exact time if you can reconstruct even a fragment of the sentence itself. This matters most for anyone who dictates at high volume through a working day, where "which one of these twenty rows is the one that did not paste" is a more realistic question than "did my one dictation this morning get lost."

The underlying guarantee does not weaken with volume. Every row is written independently, at the moment you released the hotkey for that dictation, so a busy morning with a hundred dictations in it has a hundred independent chances to fail a paste and a hundred independent rows in history regardless of which of them did. Finding the right one among many is a search problem, not a question of whether it was kept at all.

FAQ

How far back does history go?

Every dictation you have made is kept as a row, so you can go back well past the most recent one if you need to find something from earlier in the day or before.

Can I search history instead of scrolling?

Yes — history is searchable by the text in each row, so if you remember a word or two from the missing sentence you can find it directly rather than scanning by time.

Does a failed paste show up differently in history from a successful one?

No. The row records what you dictated and where it was aimed, not whether the paste that followed succeeded. This is deliberate: the record of what you said should not depend on what happened to it afterward.

What if I dictated several things in a row and none of them pasted?

Each is its own row, in order, so recovering all of them is the same process repeated — open history, copy each one, paste it into the field it belongs in.

Making recovery a non-event

None of the steps above are complicated, and that is deliberate — a recovery process only earns its keep if it is faster than giving up and retyping the whole sentence from memory, which is rarely word-for-word what you originally said anyway. Once you have done it once, checking history after an odd paste becomes as automatic as checking a sent folder after an email you were not sure went through, and just as quick.

The short version

A dictation that does not appear where you expected is a paste problem, not a missing sentence — check history first, copy the version you want, and paste it manually. Coii VoiceInput is $19 once, with a 30-day trial, and this is exactly the kind of failure mode its history exists to make recoverable rather than a reason to redictate and hope it lands the second time.