OpenFrame

Clipboard & Input Sharing During Remote Sessions

OPENFRAMEREMOTE ACCESSTUTORIAL

Phase 7 — Remote Access · Step 4

Section

June 23, 2026

Published

Vladislav Marchenko

Vladislav Marchenko

Head Of Marketing

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.

Vladislav Marchenko

Vladislav Marchenko

Head Of Marketing

Hi all! My name is Vlad and I’ve been brought on to head the marketing team at Flamingo. Thankfully, this isn’t the first time I will be building a marketing department from scratch, so the experience should come in handy. Now it’s time to dive into the world of MSPs and find myself in this new world.

More in Phase 7 — Remote Access

Related Content

Product Releases

Webinars

Case Studies

Blog Posts

Frequently Asked Questions

MSP AI Agents

Yes. In production MSP shops today, 10% to 25% of tickets close before a human opens them. Thread alone has processed 173 million tickets across 750-plus MSP partners at 96% triage accuracy, handing back 490,000-plus technician hours. Agents own the low-risk, high-volume work (password resets, MFA enrollment, known installs, onboarding and offboarding) and flag anything that touches production data or needs judgment for a human to take.
On a five-person desk, reported deployments show $78,000 to $130,000 in annual direct labor savings, roughly 30% fewer escalations, and 15% to 20% better SLA compliance. Broader MSP adoption data adds ticket handling time cut by 45% and five to 12 points of margin, all from reclaimed capacity rather than headcount cuts.

About OpenFrame

OpenFrame isn't built to plug into your stack. It replaces it. Instead of duct-taping a dozen tools together (RMM, MDM, SIEM, patching, remote access, each its own login and bill), we bundle it into one unified platform: RMM, MDM, monitoring, automation, remote access, patch management, security monitoring, and ticketing, plus built-in AI copilots. So "does it integrate with X?" usually means: you won't need X anymore.
Most platforms give you one piece and expect you to bolt the rest on. OpenFrame unifies the whole stack in one place, with AI copilots built in. Fewer logins, fewer bills, less duct tape.
Both. It's built for MSPs and MSSPs alike.

Community & Support

OpenMSP includes integrated community discussions, an embedded Slack community for real-time conversations, peer knowledge exchange, and forums where MSPs can share experiences and solutions. Our community is one of our biggest values - MSPs helping each other with questions, setup guidance, troubleshooting, and sharing real-world implementation experiences.

AI MSP

MSPs use AI to triage and route tickets, cut alert noise, schedule patches, assist L1 security work, and draft client reports. Kaseya's 2025 benchmark found 30% already use it to eliminate tedious tasks, with ticket triage the most common starting point.
Most MSPs start with AI features inside their existing PSA, RMM, and ticketing systems rather than standalone products. Common categories include AI ticket triage, alert correlation, scripting assistants, and AI-native all-in-one platforms like OpenFrame that run intelligence across the whole stack.
Start with a readiness assessment, not a tool purchase. Confirm your ticket history is clean and your RMM, PSA, and monitoring systems connect. Then pick one high-volume, low-risk workflow, usually ticket triage, and pilot it on internal tickets before any client sees it.
Automate high-volume, low-risk tasks first. Ticket triage and alert noise reduction top the list because they run constantly and a human still resolves the underlying issue. Save security approvals, billing changes, and client-facing actions for later, always with a human in the loop.