Skip to content

Docs

How it works

The control / realtime split, a direct-first connection strategy, and the path of a frame.

Nearshell consists of the Mac app, the iPhone / iPad controller, and officially operated account, signaling and relay services.

Accounts and the device console

Your account manages device authorization and subscription entitlements. The console brings your Macs together, with separate connection status and preferences for each. A Mac can host multiple authorized controller sessions.

Connecting

  1. Add a Mac under the same account and pair by scanning or pasting its code.
  2. Coordinate the connection through signaling and verify the paired device’s identity.
  3. Establish an encrypted WebRTC connection, trying direct connectivity first and using TURN when needed.
  4. Open a desktop, app window or terminal workspace from the console.

Video and input

The Mac captures video using system screen-capture capabilities; the controller decodes and displays it. Capture and transmission adapt to content, quality preferences and connection conditions, without promising a fixed frame rate or latency.

Choose the full desktop or an app window and interact through touch, keyboard and pointer controls. Screen Recording and Accessibility permissions govern capture and input injection respectively.

Terminal workspace

An independent service on the Mac hosts Native shell. tmux and Herdr sessions connect through their respective backends, which must be installed on the Mac. Controllers provide text input, selection, copying, scrollback and appearance settings. The runtime coordinates input ownership across controllers.

Updating the terminal service does not restore the original Native process: saved text can return in a new shell. tmux and Herdr sessions remain with their respective backends. Follow the app’s task and save prompts before an update.

Mobile input and viewing

Input drafts support typing and dictation, then send after review without adding Return. Picture in Picture is available separately for remote views and terminals, is off by default, and depends on device and system support.

Read more in the Security model and Getting started.