Reviewed 02/10/2026
Clipboard & Input Sharing During Remote Sessions
Phase 7 — Remote Access · OpenFrame Onboarding
Remote desktop sessions run inside your browser, and the browser sits between your keyboard and the remote machine. That's great for convenience, but it means a few things behave differently than a local session — copy-paste, certain shortcuts, keyboard layout. Here's what to expect and how to work around the quirks.
Clipboard sharing
In the remote desktop "…" menu there's a Clipboard Sharing toggle (on by default). With it on, text you copy locally can be pasted into the remote machine and vice versa — the usual workflow for moving a command, a path, or a password manager value across.
If copy-paste suddenly stops working mid-session, check that Clipboard Sharing is still enabled — toggling it off and back on clears most hiccups. Note that browser clipboard access can be finicky by design (browsers guard the clipboard for security), so very large or non-text content may not cross cleanly.
Input control
The Enable Input toggle (also in the "…" menu) controls whether your keyboard and mouse actually drive the remote machine. It's normally on. Turn it off when you want to watch without risk of fat-fingering something — useful when you're showing a user their own screen, or observing a process you don't want to disturb. If your clicks and typing aren't registering on the remote, Enable Input being off is the first thing to check.
Shortcuts your browser steals
This is the big one. Some key combinations never reach the remote machine because your local OS or browser grabs them first — press Win+L and your computer locks; press Alt+Ctrl+Del and your machine intercepts it. You can't fix that by typing harder.
The answer is Apply Shortcut in the "…" menu. It sends the combo to the remote machine directly, bypassing your local capture. The list includes the ones that matter most:
- Alt + Ctrl + Del
- Win + L (lock), Win + R (Run), Win + M (minimize all), Shift + Win + M (restore)
- Win + Up / Win + Down (snap/restore window)
- Ctrl + W
So when a shortcut "doesn't work" in the session, don't assume it's broken — send it through Apply Shortcut instead.
Keyboard layout mismatches
If the characters you type come out wrong on the remote (symbols in the wrong place, etc.), it's usually a keyboard layout difference between your machine and the remote one. Open the session Settings (gear) and toggle Use Remote Keyboard Map to have OpenFrame use the remote device's layout instead of yours. Flip it back if your own layout is the right one.
Quick checklist
- Clipboard Sharing is on when you need copy-paste across
- Enable Input is on when you need to control (off when you only want to watch)
- Used Apply Shortcut for combos the browser intercepts (Win+L, Alt+Ctrl+Del, etc.)
- Toggled Use Remote Keyboard Map if typed characters came out wrong
- Re-toggled clipboard/input if something stopped responding mid-session
What's next
That completes Phase 7 — Remote Access. You can now get onto any online machine — full desktop, a shell, or just the file system — and handle the browser-in-the-middle quirks. Next is Phase 8 — Integrations, wiring OpenFrame into the rest of your stack.
Based on OpenFrame v0.9.19. Clipboard and input behavior depend partly on your browser's own security rules, and this area is actively evolving — re-check the console if something behaves differently than described.
