guides

How to Dictate Into a Remote Desktop Session

Step-by-step guide to dictating into RDP, Chrome Remote Desktop, and Parsec sessions with Tap2Talk. Voice typing that works across machines.

Remote desktop dictation is broken by default. You hold a key, speak, and the text lands on the wrong machine. Every dictation app does this because they all paste locally, and “locally” is your Mac or PC — not the remote session you are looking at.

Tap2Talk handles this differently. It detects when a remote desktop app is in the foreground and sends the transcribed text directly to the remote machine. No clipboard tricks, no mic forwarding, no workarounds.

This guide walks through the setup for Microsoft RDP, Chrome Remote Desktop, and Parsec. The whole process takes about five minutes.

What You Need

  • A Mac or Windows PC with Tap2Talk installed (the local machine where you speak)
  • A remote machine you access via RDP, Chrome Remote Desktop, or Parsec
  • A Groq API key configured in Tap2Talk (for Whisper transcription)

How It Works

When you hold the hotkey and speak, Tap2Talk records audio from your local microphone and sends it to Groq’s Whisper API for transcription. Then the Groq LLM cleans up grammar and punctuation. So far, standard Tap2Talk behavior.

The difference is what happens next. Tap2Talk checks which application is in the foreground. If it detects a remote desktop client, it routes the finished text to the remote machine instead of pasting locally. The text appears in whatever field is focused inside the remote session.

You do not need to toggle a switch or change modes. The detection is automatic.

Supported Remote Desktop Apps

Tap2Talk automatically detects these remote desktop clients:

  • Microsoft Remote Desktop (RDP) — the standard for connecting to Windows machines and Azure Virtual Desktop
  • Chrome Remote Desktop — Google’s free remote access tool that runs inside Chrome
  • Parsec — low-latency remote desktop popular with creative professionals and gamers

It also detects Citrix Workspace, AnyDesk, TeamViewer, VMware Horizon, Amazon WorkSpaces, Jump Desktop, Screens, Royal TSX, NoMachine, Splashtop, RustDesk, and ConnectWise ScreenConnect.

Step 1: Install and Configure Tap2Talk

If you have not already set up Tap2Talk, install it and configure your Groq API key. Test a quick local dictation first: open any text field, hold Right Alt (or Right Ctrl), speak a sentence, and release. You should see text appear. This confirms your mic and transcription are working before adding the remote layer.

Step 2: Connect to Your Remote Desktop

Open your remote desktop client and connect to the remote machine as you normally would.

Microsoft RDP

Open Microsoft Remote Desktop on your Mac, or use the built-in Remote Desktop Connection on Windows. Connect to your remote machine. Tap2Talk detects the RDP client automatically.

Chrome Remote Desktop

Open Chrome and go to remotedesktop.google.com. Connect to your remote machine. Tap2Talk detects when Chrome Remote Desktop is active — unlike most dictation apps, which cannot distinguish a Chrome Remote Desktop tab from a regular browser tab.

Parsec

Launch the Parsec app and connect to your remote machine. Tap2Talk detects Parsec automatically.

Step 3: Dictate

With the remote desktop session open and focused:

  1. Click into a text field inside the remote session — Word, Outlook, a browser field, your EMR, anything
  2. Hold the Tap2Talk hotkey (Right Alt or Right Ctrl)
  3. Speak naturally
  4. Release the hotkey

The text appears in the remote session within a couple of seconds. Same as local dictation, but the text arrives on the other machine.

For longer dictation, double-tap the hotkey to engage lock mode. Tap2Talk stays recording until you tap again or the 10-minute timeout kicks in.

Step 4: Troubleshooting

If text does not appear in the remote session, work through these checks.

Text appears locally instead of in the remote session

Tap2Talk only routes to the remote machine when it detects a remote desktop app in the foreground. If you have tabbed away from the remote desktop window — to check email or open Finder — Tap2Talk reverts to local paste. Switch back to the remote desktop app before dictating.

Nothing happens at all

Verify Tap2Talk is running. Check the menu bar (macOS) or system tray (Windows) for the Tap2Talk icon. Try a local dictation in a text editor to confirm transcription is working. If local dictation works but remote does not, the issue is with remote detection.

Text appears but in the wrong window on the remote machine

Tap2Talk pastes into whatever window is focused on the remote machine. Before dictating, click into the specific text field you want. If the remote machine has multiple monitors, make sure the correct window is in focus.

Chrome Remote Desktop is not detected

Make sure you are using Chrome Remote Desktop in a Chrome browser tab, not a different browser. Tap2Talk specifically monitors for the Chrome Remote Desktop session. If you are using Chrome but detection still fails, try closing other Chrome windows so the CRD tab is the primary window.

Tips for Daily Use

Use lock mode for long passages. Double-tap the hotkey to lock on. Dictate for as long as you need. Tap once to stop. This is particularly useful for writing long emails or reports in a remote session.

Custom words help with jargon. If you regularly dictate industry-specific terms in your remote session, add them to Tap2Talk’s custom words list. The LLM cleanup will handle them correctly.

Custom prompts for context. Set a custom prompt like “This is a clinical note” or “This is a legal memo” to improve cleanup accuracy for your specific use case.

What Happens Under the Hood

When you hold the hotkey and speak:

  1. Tap2Talk records audio from your local microphone
  2. Audio is sent to Groq’s Whisper API for transcription (typically 1-2 seconds)
  3. The Groq LLM cleans up grammar, punctuation, and filler words
  4. Tap2Talk checks which app is in the foreground
  5. It detects a remote desktop app (e.g., Microsoft Remote Desktop, Chrome Remote Desktop, Parsec)
  6. Instead of pasting locally, it sends the text to the remote machine
  7. Text appears in the focused window on the remote machine

Audio goes to Groq for transcription. Only finished, cleaned-up text reaches the remote machine. No raw audio crosses your local network.

For the technical explanation of why other dictation apps fail at this, read Why Remote Desktop Breaks Every Other Dictation App. For the cross-machine architecture deep dive, see Cross-Machine Dictation: One Voice, Two Computers.

FAQ

Which remote desktop apps does Tap2Talk detect?

Tap2Talk detects Microsoft Remote Desktop, Chrome Remote Desktop, Parsec, Citrix Workspace, AnyDesk, TeamViewer, VMware Horizon, Amazon WorkSpaces, Jump Desktop, Screens, Royal TSX, NoMachine, Splashtop, RustDesk, and ConnectWise ScreenConnect. Detection is automatic — you do not need to configure anything.

Does remote dictation add noticeable delay?

The transcription itself takes 1-2 seconds via Groq Whisper, same as local dictation. Routing text to the remote machine adds negligible overhead. In practice, you will not feel a difference between local and remote dictation.

Can I use this with Chrome Remote Desktop specifically?

Yes. Tap2Talk is one of the few dictation apps that actually detects Chrome Remote Desktop sessions. Most apps cannot distinguish a CRD tab from a regular Chrome tab. Tap2Talk can. See How to Use Voice Dictation with Chrome Remote Desktop for a dedicated guide.

Try Tap2Talk — one-time purchase, no subscription. Or get it free by referring 10 friends.

Ready to ditch typing?

Tap2Talk is $69 once — no subscription, no limits. Or get it free by referring 10 friends.

Buy Lifetime — $69 Get It Free