Why does dictation break in remote sessions?
Dictation tools listen to a microphone on the machine where they run. In an RDP, Citrix, or VDI session, the apps you're typing into run on a remote machine — and that machine has no microphone. Unless your IT department configures audio-input redirection (most don't, and many security policies forbid it), Win+H and other in-session dictation tools open, wait, and hear silence.
This isn't a niche complaint. Microsoft's own Q&A forums carry long-running threads about the microphone not being recognized in Remote Desktop sessions and Speech Recognition failing to start on Remote Desktop servers ("Speech Recognition could not start because the language configuration is not supported"). The pattern is always the same: the dictation feature lives on the remote machine, and the remote machine can't reliably reach your microphone.
How Pithflow gets around it
Pithflow never needs the remote machine to hear anything. It captures your voice on your local Windows machine, runs AI cleanup on the transcript, and injects the finished text as simulated keystrokes. Remote desktop clients forward keystrokes to the remote session — so the text lands in whatever field has focus, exactly as if you had typed it.
Verify it yourself in five minutes
You don't have to take a vendor's word for it. Install Pithflow on your local machine (the free tier is 2,000 words a week, no card), open your usual RDP or Citrix session, click into any text field in the remote window, hold your hotkey, and speak. If you can type into the remote window, the dictated text lands there — because as far as the remote session can tell, you did type it. That's the whole trick, and it's why no IT ticket is involved.
What works in a remote session — compared
| In an RDP/Citrix session | Pithflow (local) | Win+H (in-session) | Cloud app installed in-session |
|---|---|---|---|
| Hears your microphone | ✓ (local capture) | Only with audio redirection | Only with audio redirection |
| Needs install on remote machine | No | Built in | Yes — often blocked by IT |
| Works on locked-down corporate VDI | ✓ | Rarely | Rarely |
| AI cleanup of the transcript | ✓ | — | Depends on app |
Who needs this?
- Clinicians charting in hosted EMRs through Citrix
- Finance, legal, and support teams working in locked-down VDI environments
- Developers and admins who live inside RDP sessions on remote servers
- Anyone whose IT department won't approve software installs on the remote image
Frequently asked questions
Why doesn't Windows voice typing (Win+H) work over RDP?
Win+H runs inside the session where you invoke it. In a remote session, the remote machine can't use your local microphone as a dictation source unless audio redirection is configured — and on locked-down corporate VDI images it usually isn't. The dictation panel opens but hears nothing.
How does Pithflow work inside a remote desktop session?
Pithflow runs on your local machine, not the remote one. It captures your microphone locally, cleans up the transcript, and types the result as keyboard input — and remote desktop clients forward keyboard input to the remote window. To the remote session, Pithflow looks like very fast typing.
Do I need to install anything on the remote machine or ask IT?
No. Pithflow installs only on your local Windows machine. Nothing runs inside the remote session, which is exactly why it works on locked-down corporate environments where you can't install software.
Does this work with Citrix and other VDI, or only Microsoft RDP?
Any remote-desktop technology that forwards your local keyboard input — RDP, Citrix, and common VDI clients — receives Pithflow's typed output the same way. If you can type into the remote window, Pithflow can type into it too.
Try it in your next remote session
Free tier: 2,000 words a week, no credit card. Installs only on your local machine.
