Parsec lets a friend join your couch co-op game without being anywhere near your couch. You host, they connect, and someone miles away gets to play on your computer. An OSRS service can use the same basic arrangement, except the guest is a trainer you may only know through an order chat.
Before considering that arrangement, understand the account risk: Jagex’s rules explicitly prohibit paying someone to play your account under the real-world trading rule. Using Parsec instead of sharing your password does not avoid that restriction. Your account could be banned.
The appeal is straightforward: you log into RuneScape yourself, so you don’t need to send over your game password. The trainer watches a stream from your PC and sends mouse and keyboard inputs back to it.
That still gives someone control of your computer. Before the first click, you should know what they can see, what they can interact with and how to end the session.
Agree on What the Trainer Will Do
Confirm the equipment, supplies and bank access the job needs before connecting. A prepared cape attempt is a different arrangement from a quest bundle with repeated equipment changes.
Put account restrictions in writing. If you’re preserving a pure’s Defence level, spell that out in the order conversation. Ask what happens if supplies run short or the work needs another session, and agree when you can take a break to play yourself.
TonsOfXP says it offers Parsec on almost all of its OSRS boosting services, with the trainer playing on the customer’s own PC. An extra charge may apply, so confirm the remote option and full price for your order before paying.
Prepare Your Computer
Install Parsec from its official website, use your own account and enable two-factor authentication. The trainer should join through their own account. They don’t need your Parsec password.
This guide uses Windows, where Parsec’s Approved Apps feature is available. Parsec also supports hosting on macOS, but Approved Apps is not available there.
Close email, private documents, password managers and unrelated browser windows. Pause desktop notifications too. A notification can reveal private information while RuneLite remains active. If an unapproved application takes focus, Approved Apps will freeze the guest’s stream and block their input until an approved application is active again.
Log into the game and handle authentication yourself before the trainer connects. If you need to sign in again later, disconnect the guest first. Keep email access and recovery codes private throughout.
Finally, check that your PC won’t go to sleep halfway through the order. It needs to stay on and connected while the trainer plays. Plan for a stretch when you won’t need the same desktop for work.
Accept the Right Guest
In Parsec’s Host settings, enable hosting. You can add the trainer as a friend or send them a share link. Verify their Parsec identity through your existing order chat before accepting the connection request.
Guests have controller access by default. For OSRS, you’ll need to grant mouse and keyboard access through the connected guest’s profile. Those controls manage the active connection; the Friends menu separately manages the saved permissions a friend receives when joining.
Leave “Can connect without your approval” switched off. If the order spans several days, arrange times to accept the next connection. A trainer being on your friends list shouldn’t mean they can arrive on your desktop whenever they choose.
Set Approved Apps and Check the Display
Open Settings → Approved Apps, enable it and select the running RuneLite client. Keep unrelated applications off the list.
As Parsec’s documentation explains, switching to an unapproved application freezes the guest’s stream and blocks their input. Test this before any work begins.
The catch is what happens while RuneLite has focus: the entire captured screen remains visible. Approved Apps does not crop the stream around the game window. Other windows beside it, notifications and overlays can still be seen.
Under Host → Display, select the monitor containing RuneLite. Keep that display clear and confirm which screen the guest actually sees. Parsec also supports switching remote displays, so moving private windows to a second monitor is not a reliable privacy measure. Close private applications before connecting.
On one monitor, give RuneLite the screen and keep everything else closed. Whatever your layout, ask the trainer to confirm what is visible before starting.
Watch Without Interrupting the Run
You can watch directly on your own monitor, but your mouse and keyboard still work. One stray click during an Inferno wave can end the attempt. If you want to watch, leave the controls alone.
Use the agreed chat channel to request a pause. Trying to answer emails on the same desktop during combat can interrupt the session; use your phone if you need to message the trainer mid-attempt.
For an immediate stop, the default host shortcut Ctrl+F3 disconnects all guests. You can also kick a guest through their connected profile. Check your configured hotkeys if you’ve changed them.
Test disconnecting and reconnecting while the character is somewhere suitable for a pause. Learn the controls before the attempt, not while you’re trying to stop it.
Requests Worth Questioning
Some requests don’t fit the remote arrangement you’ve agreed to:
- Your game password “as a backup.” If the connection drops, arrange to reconnect. Sharing credentials introduces additional account-security risks.
- Email access or recovery codes. Handle authentication yourself with the guest disconnected.
- Connecting without approval. Keep ongoing access disabled.
- Disabling Approved Apps or installing unexplained software. Ask what problem needs fixing. Verify any proposed download independently before changing the setup.
- Bank access without a reason. A prepared inventory may be enough for the job. If banking is required, the provider should explain why.
Approved Apps can’t prevent mistakes or unwanted actions inside RuneScape itself. You’re still choosing someone to control your character, so the agreed scope and the person carrying it out matter. These precautions also do not remove the risk of penalties under Jagex’s rules.
Close the Session Properly
Disconnect the guest, check the completed work and log out of the game yourself. Then review their saved entry in Friends: remove mouse and keyboard permissions and confirm connection without approval is disabled, or unfriend them if no further session is planned. Disable hosting if you don’t otherwise use it.
Disconnecting ends the current session. Reviewing the saved settings deals with future access. Don’t assume one has done the other.
If you kept your credentials private, you haven’t deliberately handed the trainer a password. That alone doesn’t establish that the account or computer remained secure. Close the access you granted, and address any suspected exposure or unexpected changes. When the order is over, the remote session should be over too.
Heather Neves is working as a freelance content writer. She likes blogging on topics related to parenting, golf, and fitness, gaming . She graduated with honors from Columbia University with a dual degree in Accountancy and Creative Writing.
