Test Presspeech with one app

Separate insertion from recognition

Presspeech binds each recording to the window where it began. It should paste only when it can still verify that destination. A focus change normally leaves the transcript available for manual paste. On macOS, if Presspeech detects another copy replacing the clipboard during delivery, it stops and preserves that newer copy; it shows a Couldn't paste notice instead of overwriting it with the transcript.

This is a delivery check, not a transcription-quality test. The recognized wording can differ from what was spoken and still pass: the question is whether the same finished transcript reaches the intended field once, or is recovered safely without reaching another field.

Choose a useful target

If you already depend on one app, test that app. Otherwise, choose a safe disposable field in a target class that does not yet have a comparable report. The live searches below make missing coverage visible without collecting anything on this site.

Before testing

1. Finish Presspeech setup

   Use the current official build. On macOS, this baseline requires 0.3.8 or later; update before testing if the About window shows 0.3.7. Confirm the model is ready, the microphone and hotkey checks pass, and Try Dictation works first.

2. Open two disposable fields

   Use one blank field in the target app and one blank field in a local scratch app. Never use a production message, document, account, command shell, or field where pasted text can submit, send, or execute. Test a remote/virtual environment or terminal-based editor only when it is isolated, disposable, and non-executing; otherwise skip that target.

3. Use harmless, distinct phrases

   Create a different phrase for every attempt so stale or duplicate delivery is visible. Do not use names, credentials, commands, customer data, or text from real work.

   Optional eight-phrase prompt

   If English suits the selected language hint, use these in order: amber rabbit one; blue otter two; copper robin three; green badger four; ivory falcon five; purple fox six; silver heron seven; yellow turtle eight. Otherwise use the same colour-animal-number pattern in the test language. Recognition accuracy is not scored; compare the finished target text with the scratch paste. Never add either version to the public report.

4. Make clipboard behavior comparable

   On macOS 0.3.8 and later, leave Keep Previous Clipboard for Manual Restore off for this baseline. Published Windows 0.1.12 leaves the finished transcript on the current clipboard. Upcoming Windows 0.1.13 marks that item for exclusion from Windows Clipboard History and Cloud Clipboard; published 0.1.12 does not. macOS 0.3.8 can expose transcript entries to macOS Universal Clipboard; disable Handoff if the harmless test text must stay on the Mac. Builds containing local-only transcript clipboard writes prevent Universal Clipboard transfer while preserving local Command-V. If macOS Clipboard History in Spotlight is enabled on macOS 26 or later, clear it after the check if you do not want the text retained there. Also disable third-party clipboard managers if you do not want the test text retained elsewhere.

5. Record versions, not private context

   Note the Presspeech, operating-system, and target-app versions. Classify the target as native, browser/web editor, Electron/Chromium, terminal, remote desktop/virtual machine, or elevated Windows app, and record the generic field type (for example, plain text, rich text, or browser content editor). Omit account, server, document, tab, form, and window names.

Keep the target focused

Run five completed attempts with a different harmless phrase each time.

1. Start in the blank target field

   Keep its window focused from the start of recording until Presspeech finishes. Do not copy anything or allow a clipboard tool to replace its contents during delivery.

2. Dictate once, then inspect the target

   Note whether one copy appeared and whether Presspeech showed a copied/manual-paste recovery notice.

3. Inspect the clipboard before copying anything else

   If delivery succeeded or Presspeech showed its copied/manual-paste notice, paste into the separate local scratch field before copying anything else. With restoration off and no intervening clipboard change, this should be the finished transcript. After a Couldn't paste notice on macOS, do not assume the clipboard contains it: use Copy Last Transcript if offered, or dictate again if Recent Transcripts is off. Record the failed delivery; deliberate recovery afterward does not turn it into a successful attempt.

4. Classify one outcome

   Use the definitions below, then clear both disposable fields before the next attempt.

If you know another copy changed the clipboard during delivery, record that attempt as an interruption under Relevant conditions and repeat with a fresh harmless phrase. Exclude known interruptions from the five completed-attempt counts. Do not use this exclusion for unexplained failures; report those as Incorrect or unsafe above.

Move focus before dictation finishes

Use blank disposable fields in two separate windows. Start dictation in the first window, move focus to the second, then finish. In hold mode, move before releasing the hotkey; in toggle mode, move before the stop press.

Classify each attempt as copied for manual paste without inserting anywhere, inserted into a field, or other/not completed. The three counts should total three.

Record categories, not words

Use this optional worksheet as you complete the checks above. It records only the outcome category selected for each attempt, calculates the two sets of aggregate counts, and prepares the exact count and overall-result block used by the compatibility report. There is nowhere to enter a phrase or transcript.

Keep platform boundaries separate

Share counts, not content

1. Find the same platform, app, version, and field type

   Browse existing compatibility reports. When the platform, app version, and generic field type match, add a comment there instead of opening a duplicate—even if your outcome differs. Paste the worksheet block, then add the Presspeech and operating-system versions, generic hardware if useful, and relevant conditions, because variation under comparable conditions is important evidence. Open a separate report for a different platform or field type.

   Comment shape for another observation

   Presspeech version: [x.y.z]
   Operating-system version: [version]
   Hardware (optional, no serial or device names): [generic model/chip]
   
   [paste the worksheet's six counts and Overall result]
   
   Relevant conditions: [trigger mode, suffix, clipboard manager/history,
   assistive technology, or a minimal reproduction; omit private context]

2. Submit one target-app report

   If no matching report exists, open the compatibility report form. Paste the worksheet's report-ready block into Eight-check outcome counts and select the same overall result in the form, or enter the same values manually. For a new report, put the platform, public app name/version, and generic field type after the fixed [Compatibility]: title prefix. Passing results are useful because they provide the denominator that failure-only reports cannot.

   For Overall result, a complete automatic-paste pass means all five steady-focus attempts pasted once and all three focus-change attempts recovered safely. Focus-change recovery is expected; choose the manual-recovery option only when it occurred while the original target stayed focused. Any incorrect or unsafe result takes precedence.

3. Review diagnostics before pasting

   Copy Diagnostics produces a privacy-safe summary if you choose to include it; exact microphone names, raw error details, and raw local log lines are not copied into that report. Never add dictated or recognized text, clipboard contents, audio, dictionary or shortcut contents, screenshots with user data, credentials, titles, names, or private paths.

Community reports are exploratory evidence for the exact versions and conditions recorded. They do not replace native release qualification or promise universal support.