RustDesk on macOS has two keyboard input modes: Input Source 1 and Input Source 2. If one does not work, try the other.
This matters most when you use shortcuts like Command+Tab inside a remote Mac session. On macOS, Command+Tab is a system shortcut. It switches apps on the Mac that receives it. When you are inside a RustDesk remote window, you may want Command+Tab to switch apps on the remote Mac, not on your local Mac.
Sometimes RustDesk sends the shortcut to the remote Mac. Sometimes macOS keeps it on the local Mac. This depends on the RustDesk input mode, macOS permissions, fullscreen state, and the macOS version.
What Input Source 1 and 2 Mean
Input Source 1 and Input Source 2 are two ways RustDesk captures keyboard input on macOS.
Input Source 1 is the older method. It may work better on some Macs.
Input Source 2 is the newer method. RustDesk added it for newer macOS input rules. It may help when keys, modifier keys, or shortcuts do not pass through.
There is no fixed rule that says one source is always better. If Input Source 1 works for you, use it. If it fails, switch to Input Source 2. If Input Source 2 fails, switch back to Input Source 1.
How to Switch Input Source
- Open your RustDesk remote session.
- Click inside the remote desktop window.
- Move your mouse to the RustDesk toolbar.
- Click the keyboard icon.
- Choose Input Source 1 or Input Source 2.
- Test Command+Tab again.
If Command+Tab still switches apps on your local Mac, try fullscreen mode. macOS may keep some system shortcuts local when RustDesk runs in a normal window.
Check macOS Permissions
RustDesk needs the right macOS permissions to capture and send keyboard input.
Open:
System Settings → Privacy & Security
Then check these sections:
- Accessibility
- Input Monitoring
- Screen Recording
Make sure RustDesk is allowed in each one. If the setting looks correct but input still fails, remove RustDesk from the list, add /Applications/RustDesk.app again, then restart the Mac.
Do this on both Macs if both the local and remote machines run macOS.
Which Input Source Should You Use?
Use the one that works.
For example, if Input Source 1 sends Command+Tab to the remote Mac and Input Source 2 does not, keep using Input Source 1. That is a valid setup.
Input Source 2 is not always better. It is just another input path. It can help on some macOS versions and fail on others.
RustDesk 1.2.4, released as a pre-release on May 11, 2024, included this newer input option. But the best choice still depends on your Mac and your permissions.
Simple Rule
If Command+Tab does not work in RustDesk, do this:
Try Input Source 1.
If it fails, try Input Source 2.
If that fails, check Input Monitoring and Accessibility.
Then restart RustDesk and test again.
For many users, that solves the problem.