Control Where TypingVoi Inserts or Copies Text

This guide is for people who want TypingVoi to send finished text to the right place every time. It explains the output modes, when to use each one, and how Original Field and Current Field change insertion behavior.

1. Open the profile output settings

Output delivery is controlled per profile, so start with the workflow you actually want to change.

1. Open TypingVoi from the menu bar.
2. Open Settings.
3. Select the profile you want to edit.
4. Open the Profile & Output section.

Screenshot placeholder: Profile & Output settings card showing Profile name, Profile quick-start shortcut, Where final text goes, and Where inserted text goes

If you use multiple profiles, remember that each one can send text somewhere different. That is often the right way to separate writing, support, meetings, or review-first workflows.

2. Choose where final text goes

The Where final text goes picker controls what TypingVoi does after transcription finishes.

Screenshot placeholder: Output mode picker open with Insert at Cursor, Clipboard Only, and Do Nothing visible

You have three modes:

• Insert at Cursor: TypingVoi tries to place the final text into a text field for you.
• Clipboard Only: TypingVoi copies the final text to the clipboard and does not try to type it.
• Do Nothing: TypingVoi finishes the transcription but skips delivery.

Choose the mode based on the job, not just on preference. Direct insertion is fastest when it works well. Clipboard mode is safer when the target app is unpredictable. Do Nothing is best when you want to review first instead of sending text immediately.

3. Understand how Insert at Cursor works

Insert at Cursor is the most automated option. TypingVoi starts by trying accessibility-based insertion, which is why Accessibility Typing permission matters for this mode.

In practice, the flow is:

1. You start recording from a profile set to Insert at Cursor.
2. TypingVoi remembers the text field or app context it may need.
3. When the final transcript is ready, TypingVoi tries to insert it through macOS accessibility tools first.
4. If insertion succeeds, the text is sent to the chosen field.
5. If insertion cannot complete, TypingVoi falls back to the clipboard so you can paste manually.

That fallback is intentional. If direct typing fails, TypingVoi does not silently lose the result.

4. Pick the insert target: Original Field or Current Field

When Insert at Cursor is selected, TypingVoi also shows Where inserted text goes.

The menu labels are:

• Original Field (at Starting)
• Current Field (at Ending)

Use them like this:

• Original Field: TypingVoi tries to return to the field that was active when recording started. This is best when you trigger recording, speak, and want the text to go back to the same draft, note, or reply box.
• Current Field: TypingVoi uses whatever field is active when recording ends. This is best when you intentionally move to another field before delivery, or when your workflow changes focus during the capture.

For most people, Original Field is the safer default because it protects the field you started from.

5. Know what happens when insertion fails

Direct insertion can fail for practical reasons:

• Accessibility Typing permission is not enabled
• The target app does not expose a normal editable field
• Focus changed in a way macOS accessibility cannot resolve cleanly
• The app accepts paste better than direct value updates

When that happens, TypingVoi falls back to the clipboard instead of discarding the transcript. You can then paste the result yourself.

This is the behavior to expect:

• If accessibility access is missing, Insert at Cursor falls back to the clipboard.
• If the original field cannot be reached, TypingVoi may still insert into the current field if possible.
• If direct insertion still does not succeed, TypingVoi copies the prepared final text to the clipboard.

If you want a fully predictable manual workflow, switch that profile to Clipboard Only instead of relying on fallback behavior.

6. Decide which mode fits each workflow

Use Insert at Cursor when:

• You dictate directly into normal text fields
• You want the fewest manual steps
• You have already granted Accessibility Typing
• The target app usually behaves well with direct insertion

Use Clipboard Only when:

• You work in apps where direct typing is inconsistent
• You want to review before pasting
• You often move between fields while speaking
• You want a stable fallback workflow across many apps

Use Do Nothing when:

• You are capturing for review rather than immediate delivery
• You plan to copy from the transcript card yourself
• You are testing transcription quality before deciding where text should go

7. Set up a practical default

If you are not sure what to choose, start with one of these patterns:

• Writing or General: Insert at Cursor with Original Field
• Support or app-specific workflows: Clipboard Only if the target app is unreliable
• Meetings or review-first capture: Do Nothing or Clipboard Only

The right choice depends less on the model and more on how stable the target app is and whether you want automatic delivery or a review step.

8. Test the profile once before relying on it

After changing output settings, run one short real test.

1. Open the app and profile you want to use.
2. Place the cursor in the target field.
3. Start a short recording.
4. Speak one sentence.
5. Stop recording and watch where the final text goes.
6. If it lands in the wrong place or only copies to the clipboard, change the output mode or insert target and test again.

If your main problem is missing permission, fix that first. If your main problem is app behavior, Clipboard Only is usually the cleanest answer.

Related guides

• Create Profiles for Different Apps and Workflows
• Fix Permissions and Choose Shortcuts
• Record From the Menu Bar and Use Push-to-Talk
• Complete the Onboarding and First Test

Best next step: apply one output mode to your most-used profile, then test it in the exact app where you dictate most often.