How to pair program remotely on a Mac.

Published · Updated

Pairing with someone who isn't in the room works when you can both read the code, hear each other without lag and hand over the keyboard safely. Here's how to do that when the code is on a Mac, using Doubles, a pair programming app for Mac, where an app comes into it.

Ways to pair

Most pairs use one of three styles, and many move between them in a session.

  • Driver and navigator. One person types; the other reads along, thinks a step ahead and says where to go next. Swap every so often, so that both of you stay fresh and both know the code.
  • Ping-pong. One person writes a failing test, the other makes it pass and writes the next failing test, and so on. The tests set the rhythm, and the keyboard changes hands with each one.
  • Mob, or ensemble, programming. A whole group works on one thing, on one screen. One person drives while the others navigate, and the driver changes every few minutes.

Remotely, the swap is what has to be quick. In Doubles the code stays on the Mac that shares its screen, and the other person takes over by clicking in the shared screen: with the settings Doubles starts with, it asks the person sharing the first time, and a yes lasts for the call. Until they click, the other person only points; a browser guest you've allowed drives as soon as their pointer is over your screen. To take it back, the person sharing moves their mouse or types, and the other's input pauses.

A call can have up to 6 people, each with a pointer that has their name on it.

Screen sharing or co-editing

There are two ways to work on the same code from two places, and they suit different sessions.

Co-editing shares the project. Each person edits in their own editor, with their own cursor, and can move around the code on their own, so two people can work in two files at once. Everyone needs an editor the tool works with, and you see what the tool shares.

Screen sharing shares a screen, with everything on it. Everyone sees the same thing, so it's easy to follow, and whoever drives can use the editor, a terminal, a browser or a simulator: whatever the person sharing has open. There's one cursor, so one person types at a time, and nobody else needs a copy of the code.

Doubles shares screens: the whole display you share, minus the apps you hide. Some pairs use both at once, editing together in a co-editing tool while a call carries their voices, their pointers and everything outside the editor.

Which tools do which, and what each costs: remote pair programming tools, compared. For a particular setup, see Live Share alternatives for VS Code and Cursor, Code With Me alternatives for JetBrains IDEs, Doubles vs Tuple, and remote control in Zoom, Teams, Meet and Slack huddles.

Set up the Mac you share

The Mac with the code is the one that shares its screen. Get it ready before the call rather than during it.

  • Allow what a call needs. A call needs three macOS permissions: Screen & System Audio Recording (Screen Recording on macOS 14), to share your screen; Accessibility, so that people you allow can control your Mac; and Microphone, to talk. Allow them from Doubles' welcome window, or Settings › General, before your first call: after you allow screen recording, macOS may ask to quit and reopen Doubles, which is better now than in a call. macOS asks about the camera the first time you turn it on.
  • Hide what's private. Apps you hide in Settings › Sharing are left out of your share, and nobody can click or type into them. Messages, Keychain Access, Passwords, 1Password, Telegram and Signal start out hidden, if you have them, and so do notification banners, unless you turn that off. On your screen, an outline marks each window the others can't see.
  • Choose the display. With more than one, choose which to share in Settings › Sharing, or as you share. If the call panel is on the display you share, it tucks itself away at the side as a small tab, and comes back when you stop.
  • Let it stay awake. While you share, your Mac doesn't dim, sleep or lock on its own, unless you turn off Keep my Mac awake while I share. Closing the lid still puts it to sleep.

Then make room: close what you won't need, and make the editor's text bigger than you'd have it on your own. What's comfortable on your screen can be small in someone else's window.

Sound: wear headphones

Wear headphones, both of you. On speakers, your microphone hears the others as well as you: your typing can get through while they talk, and if you transcribe or record the call, their words can land in your transcript and recording as yours. Doubles warns you when you're on speakers while you transcribe or record.

On System Default, in Settings › Calls, a call uses the microphone and speaker in System Settings › Sound and follows them: connect headphones in the middle of a call, and the call moves to them.

Reduce background noise, in Settings › Calls, takes typing and other noise out of your microphone before anyone hears it. It's on unless you turn it off, and it holds your voice back about 56 ms: why remote pairing lags has more on that.

During a call, Control-Command-M mutes and unmutes you from any app.

Make the code readable

The code has to be sharp enough to read at a glance, at a size nobody has to lean in for.

Doubles shares your screen at up to 2560 pixels along its long side, and 60 frames a second, unless you change that in Settings › Sharing: a bigger display is scaled down to fit, never up. You can choose 1920, 2560 or 3456 px, or Native, up to 4096 px, and 60 or 30 fps. As the pane says, scaling down blurs thin text on displays that aren't Retina, and native keeps it sharp, at a little more latency; 60 fps has the lowest latency, and 30 fps is light on bandwidth.

When the network gets busy, Doubles keeps the resolution and drops frames instead, so text stays sharp and moves less smoothly. On a slow connection, text can still look soft for a moment after a big change, such as a window switch. If it's slow for you, choose a smaller picture under View › Picture Size while you watch: a smaller picture arrives sooner, and nobody else's picture changes.

Where a screen is shown bigger than it was sent, the Mac watching it sharpens it with MetalFX, if it can, unless you turn that off in Settings › Sharing.

The rest is up to the person sharing: a bigger font in the editor, a theme with strong contrast and the window you're working in made big.

Keep it quick

Lag shows first in the pointer and the keyboard: when what you type shows up a beat late, you start typing ahead of it, or talking over each other. Most of it is the network: how far apart you are, a busy or patchy Wi-Fi network, and whether the call goes straight between you or through a server.

Doubles itself takes about 14 ms from capturing a frame of a 2560-pixel screen to decoding it, measured on 19 Nov 2026 in one process on an M2 Pro, in an optimized build, with no network: the network's time comes on top. Why remote pairing lags, and how to fix it has that measurement and its conditions, and what you can change about the rest: the network, Wi-Fi, the size of your share and your sound.

Hand over control safely

Letting someone drive your Mac should be your choice, and one you can take back at once. In Doubles:

  • Nobody controls your Mac unless you allow them. When someone clicks in your shared screen to drive, Doubles asks you, “Let Grace control your Mac?”, unless your settings already say, and a yes lasts for that call. Return doesn't answer it, and Allow stays off for a moment after it appears, so a key or a click meant for something else can't hand over your Mac.
  • You choose who's asked about. Settings › Control › Who can drive starts at Ask each time. People on my team lets teammates the Doubles server vouches for drive without asking, and Nobody turns everyone down without asking you. While you share, the call panel's ⋯ menu allows or stops each person, and turning off Let Others Control My Screen stops everyone.
  • You can take it back at once. Your own mouse and keyboard always win: when you move or type, their input pauses. Control-Option-Command-period takes control back from everyone, and they drive again only once you allow them again.
  • Some things stay yours. Clicks and keys from someone controlling your Mac never reach the apps you hide or the windows Doubles draws, and their shortcuts for locking your screen, logging you out and Force Quit are never replayed. Locking your Mac, or putting it to sleep, pauses your share and stops remote control until you unlock it.
  • It needs Accessibility. Until macOS gives Doubles Accessibility access, nobody can control your Mac, and anyone you allow is told so.

Who can see and control your screen, on the security page, has the details.

Guests in a browser

Not everyone you pair with has a Mac. Anyone can join a Doubles call from a browser on Windows, Linux, ChromeOS or a Mac, with nothing to install and no account: they open your invite link, choose Join in this browser, and someone in the call lets them in.

In the browser they can talk, turn on a camera, share their screen for the others to watch, point and draw, and control your Mac once you allow it, with their Ctrl key working as ⌘ (the default, except on a Mac). A browser itself can't be controlled, and only the Mac app transcribes and records.

The steps, and the keys that work in a browser, are in the docs: browser guests.

Transcripts, notes and consent

A transcript turns a session into something you can search later. Ask first, though: it holds the others' voices and words too.

In Doubles, each person who wants their words in the transcript turns on Transcribe My Speech, in the call panel's ⋯ menu, and their own Mac transcribes what its microphone hears, on the Mac. Everyone in the call on a Mac gets the lines, labelled by speaker, and Doubles saves them as Markdown, in ~/Movies/Doubles unless you choose another folder in Settings › Transcripts. Nothing said while muted is transcribed, and the Doubles server never receives a transcript.

After a transcribed call, Apple Intelligence writes notes beside the transcript, on the Mac: a summary, decisions, to-dos and what was discussed. That needs macOS 26 with Apple Intelligence turned on. Recording saves a QuickTime movie on the Mac of whoever records.

Whenever someone records or transcribes, everyone in the call sees it, on a Mac and in a browser. That tells people; it doesn't ask them. Doubles can't stop someone from recording their screen with another app, so pair with people you trust.

Pairing with a coding agent

A coding agent can join the pair. In Doubles, whoever starts one runs it on their own Mac, in a folder they trust, and everyone in the call on a Mac sees the conversation: each prompt, the agent's replies and what it asks to do. The person running it answers what it asks, and chooses whether the others may prompt it too.

Driver and navigator works with an agent too: one person prompts it and decides what it may do, while the other follows the conversation and the shared screen, and says what to try next. How to set one up, what Doubles asks before the agent acts and when the agent gets the call's transcript are in the docs: coding agents.

Onboarding, code review and interviews

Onboarding

Pairing is a quick way into a codebase. Let the new person drive while you navigate: they learn where things are by going there. Send them your team's invite link (Invite to Team…, in the menu bar, copies it): once they're in the team, they see when you're around and can call you with a click; People on my team, under Settings › Control › Who can drive, lets them drive without you being asked each time. If you transcribe the session, they keep the transcript on their Mac too.

Code review

Review together instead of in comments: the author shares, and the reviewer points. Everyone has a pointer with their name, and Control-Command-D draws on the screen you're watching or sharing; the ink fades after a few seconds, unless you turn that off in Settings › Sharing. Several people can share their screens at once, each in a window of its own, to look at two branches or two builds side by side.

Interviews

A candidate doesn't need a Mac or an account: send them an invite link, and they join from a browser and knock, and you let them in. Share a Mac with the exercise on it and let them drive when they're ready, or have them share their own screen from the browser. Apps you hide stay out of view, Control-Option-Command-period takes control back at once, and you can remove anyone who joined the call after you. Tell them before you record or transcribe: they'll see it in their browser either way.

Start pairing in one click.

Sharp screen sharing, remote control only when you allow it, drawing and voice. Guests join from a browser.