Install, pair, and use Pairling.
Set up the Mac and iPhone. Then control, extend, and review your coding sessions.
Install and pair
Install one Mac runtime and pair one iPhone.
Install Pairling on the Mac
- Open Terminal on the Mac that runs your coding CLIs.
- Install Pairling with .
- Start setup with .
- Review each proposed change before setup applies it.
Install Pairling on the iPhone
- Install Pairling from TestFlight.
- Open Pairling and start setup.
- Scan the QR code on the Mac.
- Confirm the Mac name and route.
The iPhone stores pairing credentials in Keychain. The Mac stores a hash of the bearer token and the device scope.
Inspect the npm package
Use to list the package files.
Use to check registry signatures.
Connect to a Mac
Use a private route on the same network or away from the Mac.
Use Pairling Connect
Pairling Connect embeds Tailscale technology in the app. It does not require a separate VPN app or system VPN profile.
The iPhone and Mac join the selected tailnet. Pairling sends control traffic through the encrypted tailnet data path.
PairDrop requires Pairling Connect. Regular session control can also use a local network route or a configured SSH route.
Use a custom control server
- Open Pairling Connect settings.
- Select the custom control server option.
- Enter a compatible control server address.
- Complete the server approval flow.
The default control server is Tailscale. The custom server controls its own metadata and retention.
Use an SSH route
- Run on an already paired Mac.
- Add the SSH route in Pairling.
- Check the Mac host key before you approve it.
The SSH route forwards only the Pairling gateway port. It does not give the iPhone a shell.
Understand Mac sleep
Pairling can prevent idle sleep while a live session needs the Mac. A closed laptop lid can still put the Mac to sleep.
Control a coding session
Open a live session and act on the Mac from the iPhone.
Open the session
- Open the Pairling dashboard.
- Select the active Mac.
- Select a live or recent coding session.
- Choose Transcript or Terminal.
Transcript shows structured provider output. Terminal shows the live terminal surface when that session has a supported terminal.
For provider-specific setup and boundaries, read how to control Claude Code from your iPhone.
Send input
Enter text in the compose field and select Send. Pairling sends the text to the exact session on the Mac.
Use the pending input card when the coding CLI asks a question. Use the approval card when the coding CLI requests approval.
Interrupt work
Use Interrupt for a normal stop request. Use the terminal controls when the session needs direct terminal input.
Pairling waits for Mac state before it clears pending cards. The iPhone does not claim success from a local tap alone.
Start or resume work
Choose a coding CLI, a project, and the correct session.
Start a session
- Open the new session sheet.
- Select a coding CLI that is available on the Mac.
- Select the project directory.
- Enter the first prompt.
- Review the launch settings and start the session.
Resume a session
- Open a past session.
- Check the provider, project, and last activity.
- Select Continue.
- Confirm the resumed session before you send new input.
The coding CLI controls its native resume behavior. Pairling shows the session state that the Mac reports.
Search and export
Find work across sessions and move a reviewed result to another app.
Run an exact search
Enter a search term and select exact search. The Mac searches the provider transcript files that Pairling can read.
Run a semantic search
- Build the local semantic index on the iPhone.
- Enter a question or idea.
- Open a result and check its source session.
The iPhone creates and stores the embedding index. The index contains short snippets and numeric vectors.
Export a session
Open the session export control. Select the format, review the output, and use the iOS share sheet.
Clear iPhone history
Clear history removes the saved iPhone snapshot and hides selected rows. It does not delete provider transcripts on the Mac.
Send text and files
Add source material to the session that needs it.
Attach a photo or video
- Open the compose attachment menu.
- Select Photos.
- Select the photo or video.
- Wait for the Mac path to appear in the draft.
- Send the draft to the session.
Attach a file
- Open the compose attachment menu.
- Select Files.
- Select one file of 100 MB or less.
- Review the inserted Mac path.
- Send the draft.
The Mac stores regular attachments under ~/Pairling/uploads. Pairling does not remove these uploads automatically.
Open a OneStream handoff
Open the handoff JSON with Pairling. Pairling loads its prompt and transcript text into the compose draft.
Pairling includes an iOS Share Extension for text, links, images, videos, and files. Shared items queue in a protected local inbox. Pairling transfers them to PairDrop when it can connect. You then choose whether to attach an item to an existing session.
Dictate and improve prompts
Turn speech or rough text into a reviewed compose draft.
Use short dictation
- Select the microphone in the compose field.
- Speak one short request.
- Stop dictation and review the text.
- Edit the text before you send it.
Short dictation prefers on-device recognition. Apple can process the audio when the selected locale has no on-device recognition.
Record or import audio in Compose
- Open Compose.
- Select Record, or select Import Audio and choose an audio file.
- For a recording, speak while the transcript appears, then select Stop Recording.
- Open the saved item to play the audio, edit the transcript, or regenerate word timings.
- Extract key points or turn the transcript into an improved prompt.
- Sync the item to your Mac through PairDrop, attach its audio, or send its prompt to a selected session.
Compose keeps the audio, transcript, word timings, key points, and prompt together on the iPhone. Deleting the item removes that local copy. A copy already synced to PairDrop remains on the Mac.
Use Prompt Helper
- Enter or dictate a draft.
- Select Prompt Helper.
- Select a Prompt Preset.
- Review the changed draft.
- Undo the change when it does not match your intent.
Prompt Helper uses Apple Foundation Models on the iPhone. It does not send drafts or preset instructions to a network fallback.
User Prompt Presets are Markdown files under ~/.pairling/prompt-presets on the Mac.
Use PairDrop
Move files between the iPhone and the Mac through Pairling Connect.
Send a file to the Mac
- Confirm that Pairling Connect is active.
- Open PairDrop.
- Select a file.
- Wait for the upload to finish.
A small upload can be 10 MB. A resumable foreground upload can be 100 MB.
Use a PairDrop file in a session
- Open the file in PairDrop.
- Select Attach to session.
- Select the session.
- Review the exact Mac path in the draft.
The reviewed Mac source stores PairDrop under ~/PairDrop. Files use your Mac storage.
Download a file to the iPhone
Open the PairDrop item and download its content. Pairling verifies the byte count and SHA-256 value before it uses the preview.
Delete a PairDrop item
Delete hides the item and sets its deletion time. It does not erase the object bytes from the Mac.
Run an orchestration
Give one objective to a planner and a bounded set of workers.
Create the run
- Open the orchestration sheet.
- Select the project and coding providers.
- Enter one objective.
- Select a mode and autonomy level.
- Select one to four workers.
- Set the time limit and stop condition.
- Review the run and start it.
Each run has one planner. The run can use one to four workers and can last from five to 180 minutes.
Choose the mode
| Mode | Use |
|---|---|
| Research | Collect and compare findings. |
| Debug | Find the cause of a fault. |
| Scaffold | Create the first project structure. |
| Decide | Compare options and recommend one. |
| Draft | Create a first written result. |
| Remember | Prepare durable project memory. |
| Extend | Continue an existing result. |
Understand permissions
Pairling records the selected permission profile and gives it to each role. The coding CLI process still controls actual file and command access.
The reviewed launch code can use provider bypass flags. Do not treat the selected profile as an operating-system sandbox.
Stop the run
Select Stop to send a termination signal to active run processes. The run files and provider transcripts stay on the Mac.
Use alerts and Live Activities
Follow work without keeping Pairling open.
Enable notifications
- Open Pairling notification settings.
- Allow alerts, sounds, and badges in iOS.
- Select the Pairling events that you need.
Pairling can notify you about required input, results, failures, route risk, worker pressure, and deployment results.
Use a Live Activity
A Live Activity can show the session, provider, project, current step, latest event, result, risk, and required action.
Pairling excludes raw prompts, transcripts, command output, credentials, and full paths from push event payloads.
Disable alerts
Disable notifications to stop future delivery. This action does not erase all stored registration and delivery records.
Configure coding CLI tools
Use native iPhone controls for common coding CLI configuration.
Use the slash command library
Type a slash in the compose field. Pairling lists commands, skills, and plugins that the selected provider reports.
The Mac reads command metadata from provider, user, plugin, and project files. Pairling inserts the selected command into the draft.
Change Claude permissions
Open the Permissions picker. Review the allow, deny, ask, directory, default mode, and effort values before you save.
Saving changes the matching values in ~/.claude/settings.json.
Manage Claude hooks
Open the Hooks picker. Add or remove a supported event, matcher, command, and timeout.
Saving replaces the hooks block in ~/.claude/settings.json.
Manage project memory
Open Memory to list, read, create, edit, or delete project memory files. Pairling also updates the project MEMORY.md index.
Check MCP servers
Open MCP to read the server list and status from the Claude CLI. Select one server when you need a restart attempt.
Set provider visibility
Hide a provider to remove it from Pairling selection controls. This setting does not uninstall the coding CLI.
Use Phone Tools, Shortcuts, and Watch
Extend a coding session through other Apple system surfaces.
Use Phone Tools
- Enable Phone Tools in Pairling settings.
- Keep Pairling open in the foreground.
- Call a Pairling phone tool from the Mac session.
- Review the result in that session.
Phone Tools can provide a second opinion, a vibe check, a preference check, or local corpus recall.
The Mac holds requests in memory. A model fallback can send a request to the selected coding provider.
Use Siri and Shortcuts
Shortcuts can summarize attention, open an active session, stop stale workers, open a draft, or send confirmed text.
Direct send requires its Pairling setting and a confirmation. Siri and Shortcuts can process input through Apple system services.
Use Apple Watch
The Watch can show bounded Mac and session state. It can refresh, open the exact iPhone route, or snooze a Sentinel alert.
Manage stored data
Know which action erases data and which action only hides or revokes it.
| Action | Result |
|---|---|
| Forget Mac | Removes the iPhone profile and Keychain secrets. The Mac keeps a revoked device row. |
| Clear history | Clears the iPhone snapshot and hides rows. Mac provider transcripts remain. |
| Clear semantic index | Removes the iPhone embedding file. Original Mac transcripts remain. |
| Clear synthesis | Removes generated synthesis files from the iPhone. |
| Delete Prompt Preset | Removes that user Prompt Preset file from the Mac. |
| Delete memory | Removes the selected memory file and its index entry from the Mac. |
| Delete PairDrop item | Hides the item. Object bytes remain on the Mac. |
| Stop orchestration | Stops active processes. Run files and provider transcripts remain. |
| Disable notifications | Stops future delivery work. Stored registration records can remain. |
Uploaded attachments, handoffs, and orchestration runs have no automatic cleanup in the reviewed source. Remove these files on the Mac.
Read the Privacy Policy for the complete feature data map.
Pairling protocol
Review the enforced connection boundary between the iPhone and a paired Mac.
The Pairling Connect bridge permits a defined path list. The Mac then checks the paired device, its scope, and request proof.
Open the Pairling Protocol Reference for the complete path list.
FAQ
Read the boundaries that affect normal use.
Does Pairling store my coding sessions?
Your coding CLI stores its session files on the Mac. Pairling stores a recent iPhone snapshot and reads those Mac files.
Does Pairling require Pairling Connect?
PairDrop requires Pairling Connect. Session control can use Pairling Connect, a local network route, or a configured SSH route.
Can Pairling work when the Mac sleeps?
No. The Mac runtime must be reachable. Pairling can prevent idle sleep, but a closed laptop lid can still stop access.
Does Prompt Helper send my draft to a server?
No. Prompt Helper uses Apple Foundation Models on the iPhone and has no network fallback.
Does PairDrop delete file bytes?
No. The current Delete action hides the item and records a deletion time. The object bytes remain on the Mac.
Does Clear history delete provider transcripts?
No. It clears the saved iPhone snapshot and hides rows. Provider transcript files remain on the Mac.
Can I share from any iPhone app into Pairling?
From apps that offer supported share items. Pairling’s Share Extension accepts text, URLs, images, videos, and files and copies them into a protected app-group inbox for transfer.
Which coding CLIs can Pairling show?
Pairling shows the providers that the Mac runtime detects and that the current provider registry supports.
Support
Check the paired Mac, prepare a safe report, or remove access.
Run the safe check
Before you contact support, open Terminal on the paired Mac. Run this command:
The plain report shows status and recovery steps. It does not include the full JSON diagnostic.
Read the result
Each check starts with [ok], [warning], or [error]. Follow the recovery text for each warning or error.
If all checks show [ok], reproduce the problem once. Record the exact action and result.
Prepare the report
Include this information:
- Describe the action that you tried.
- State the result that you expected.
- State the result that Pairling gave you.
- Give the iPhone model, iOS version, Mac model, and macOS version.
- Give the Pairling app build and CLI version.
- Copy only the reviewed
[warning]and[error]lines.
Remove private data
Review every line before you send it. Remove personal names, account names, local paths, private host names, IP addresses, and device identifiers.
Do not send JSON diagnostics, tokens, proof secrets, provider keys, environment variables, transcripts, prompts, or raw logs.
Remove access now
If you do not recognize a connection, open Known Macs in Pairling. Select the Mac, choose Forget Mac, and confirm the action.
If the Mac is reachable, Pairling first asks it to revoke the device. Pairling then removes the iPhone credentials even if that request fails.
This action does not delete coding session files.
Contact Pairling
Email the reviewed report to support@pairling.dev. Use a short subject that names the failed task.
For setup and feature instructions, use the Pairling Docs. For data handling details, read the Privacy Policy.