Editor Link
Editor Link connects your editor to another editor, usually on a different machine, and mirrors it. The editor you sit at shows the other editor's log, profiler, frame stats, cvars and hardware live. When both editors have the same project open, your editor also opens the other editor's documents and keeps them in step, and its viewports show the frames the other machine renders. In Drive mode, your edits, camera, cvar changes and Play/Stop are sent to the other editor and applied there.
The editor that is mirrored is the host. The editor that links to it is the mirror. Typical uses:
- Measure performance on a laptop, a minimum-spec PC or a QA machine from your own desk.
- Edit a scene on a test machine while watching how it runs there.
- Watch what a colleague's editor is doing, or record a soak run for a bug report.
Editor Link connects two editors. To run only the engine side of the editor on another device (for example an Android phone), see Remote engine process below.

What a link carries
Telemetry works between any two editors of the same version. Documents and viewport frames need the same project on both machines.
| Channel | What the mirror gets |
|---|---|
| Machine | CPU, memory in use, GPU and renderer, display, power (AC or battery, battery saver) and editor version. |
| Stats | FPS, frame time, draw calls, triangles, GPU and CPU memory of the host's engine process, four times a second. |
| Log | The host editor's and engine process's log, including the last 2,000 entries from before the link. Shown on the panel's Log page. |
| Profiler | The host engine process's profiler stream. In the Profiler panel, pick Linked editor as the source, or This engine process + <host> (compare) to see both side by side. |
| CVars | The host engine process's cvars, on the panel's CVars page. They can be changed only in Drive mode. |
| Documents | Every document the host shows in a window. A mirrored document opens read-only and follows every change the host makes, including unsaved ones. |
| Layout | The host's panel layout. Your own layout comes back when you unlink. |
| Camera, selection, play state | The camera of the host's focused view, its selection, and whether it is playing or simulating. |
| Viewport frames | The frames the host renders for the active mirrored scene, drawn into your viewport. |
Modes
| Mode | Behaviour |
|---|---|
| Watch | You see the host's documents and numbers, with your own camera and selection. |
| Follow | Your camera, selection and active document follow the host. Needs the same project. |
| Drive | Your edits are sent to the host and applied there as undo steps. This includes your camera, selection, cvar changes and Play/Stop. The host must allow it, and only one mirror can drive at a time. |
The host stays the only writer
A mirror never saves a mirrored document itself. When you unlink, documents the link opened are closed without saving, and documents you had open before linking are reopened from disk.
Letting other editors link to this one
- Open Panels > Editor Link and go to the Host page.
- Turn on Allow other editors to link to this one. The editor listens on TCP port 1062, which you can change in the Editor Link preferences. With Show this editor to others on the LAN on, it also announces itself on UDP port 1063 so other editors find it.
- Give the person linking the six-digit Pairing code shown under THIS EDITOR. It changes every minute, and the previous code also works. After the first link the mirror's machine is trusted and does not need a code again. Forget trusted machines resets that.
- When a mirror asks to drive, the Host page lists it under LINKED EDITORS. Choose Allow Drive or Deny. Revoke Drive and Unlink work at any time.
After five wrong pairing codes from one machine, that machine is locked out for a minute.

Linking to another editor
- Open Panels > Editor Link. The Link page lists the editors found on this network under EDITORS ON THIS NETWORK. Click one, or type its Address (host name or IP; port 1062 by default).
- Type the host's Pairing code.
- Choose the Channels: Mirror documents (needs the same project), Profiler frames and Ask to drive (the host must accept).
- Click Link.
While linked, the Link page shows the host's machine, its live performance numbers, its documents and what the link costs the host (Link cost). It also says whether the projects match:
- Same project, assets match. Documents mirror and render the same as on the host.
- Same project, N assets differ from the host's. Mirrored scenes may render differently until you sync the project.
- Different project: telemetry only. Only log, stats, profiler, cvars and the Stream page work.
Pick Watch, Follow or Drive on the Link page. Until the host allows it, the Drive button reads Drive (ask) or Drive (asked).
Linking over SSH
SSH gives encryption, login, and access through firewalls, VPNs (such as Tailscale) and jump hosts. The editor runs the system's OpenSSH client with your ~/.ssh/config, keys and agent, so it never sees a password. ssh runs in batch mode, so it needs a key, an agent or Tailscale SSH: a password prompt fails.
- On the host, allow links. Turn on SSH tunnels only (listens on 127.0.0.1; no pairing code) to accept SSH tunnels only. The SSH login then counts as pairing.
- On the mirror, under Over SSH, type the SSH host (
user@host, or a host from your SSH config; the arrow button lists them). - Optional: Start there runs a command on the SSH host first, for example
nohup PlasmaEditor -linkServer ssh -project ~/Projects/Harbour >/dev/null 2>&1 &. - Optional: Forward to reaches an editor behind the SSH host (its name or address as the SSH host sees it). That editor needs its link server on for the LAN, and you need its pairing code.
- Click Link over SSH.
Mirrored documents and Drive
With Mirror documents on and the same project on both machines, every document the host shows in a window opens in your editor too, the host's active document comes to the front, and new tabs take the host's layout. Documents the host closes close here too. Documents the host only opens internally, for example to transform assets, are not mirrored.
In Drive mode, the documents are shared both ways:
- Opening an asset on the mirror opens it on the host too, and the mirror then mirrors the host's copy.
- Saving a mirrored document on the mirror saves it on the host, so both projects keep the same file.
- Closing a document tab on the mirror closes it on the host, as if the tab had been closed there. Quitting the mirror or closing its project closes nothing on the host.
- Assets imported or created on the mirror are sent to the host's project once saved, together with the source files they are made from (for example the imported file). Files the host already has are never overwritten: a file that differs on the host stays as it is, and the log says so.
- Transform all on host (Link page header) has the host transform all assets.
- Play and Stop next to a mirrored scene start and stop the game on the host.
A host document with unsaved changes is not closed by a link request; the host log says that it stays open.
Host frames in your viewport
A mirrored scene does not render locally. Its first viewport shows the frames the host renders for your camera, with a caption such as HOST · 58.3 fps · 17.15 ms · rendered on the host. The frames are sized to your viewport, kept to at most two in flight, and sent at lower quality while your camera moves. While the next frame is on its way, the last one follows your camera, so turning the camera slides the image instead of freezing it.
To compare the host's picture with your own machine's, click Local view next to the scene on the Link page (or start the mirror with -linkCompare). A Local View tab opens next to the viewport with this editor's own render of the same camera. Hide local removes it again.
Stream page
The panel's Stream page shows JPEG frames of the host's focused view, for when the projects differ or the host's own window is what matters. Click Stream the host's active view. The caption shows the frame size, the size per frame and the capture and encode time on the host.
Keeping the numbers honest
The host measures the link's main-thread time and traffic, and the mirror shows them as Link cost. Expect well under 1 ms per second for telemetry. Mirrored documents add a little per edit. Frames cost a GPU readback and a JPEG encode per frame on the host, visible as the EditorLink.StreamFrame profiler scope.
For the cleanest numbers, link with Mirror documents off and don't stream. A linked host keeps rendering while nobody sits at it, so it does not go idle.
Recording and replay
While linked, Record... writes everything the host sends to a .pllink file. Replay .pllink... on the Link page plays a recording back at its original pace: log, stats, machine, cvars and profiler. Use it to attach a session to a bug report, or to look at a soak run later.
Command line
Linking can be set up from the command line, for test rigs and machines nobody sits at.
| Option | Editor | Description |
|---|---|---|
-linkServer on / -linkServer ssh | Host | Lets other editors link: on for the LAN, ssh for SSH tunnels only. Overrides the preferences. |
-linkPort <port> | Host | TCP port of the link server (default 1062). |
-linkAllowDrive | Host | Every editor that links (with a pairing code, a trusted token or over SSH) may drive this one without asking. |
-unattended | Host | No popup opens. Message boxes answer with the choice that changes nothing (No, Cancel, otherwise their default) and engine dialogs are cancelled. Each is logged, so a linked editor sees it in the host's log. |
-linkTo <host:port> / -linkTo ssh:<ssh host> | Mirror | Links to that editor at startup, directly or through an SSH tunnel. |
-linkCode <code> | Mirror | The host's pairing code for -linkTo. Not needed over SSH to an SSH-only host, or for a trusted machine. |
-linkDrive | Mirror | With -linkTo, asks to drive and switches to Drive as soon as the host allows it. |
-linkCompare | Mirror | With -linkTo, mirrored scenes get a Local View tab. |
Example: a QA machine runs PlasmaEditor -project <path> -linkServer on -linkAllowDrive -unattended, and your editor runs PlasmaEditor -project <path> -linkTo qa-laptop:1062 -linkCode 123456 -linkDrive.
Preferences
Editor Link preferences (application preferences):
| Property | Default | Description |
|---|---|---|
| Allow Links | off | The link server runs while the editor runs. |
| Ssh Only | off | The server listens on 127.0.0.1 only, so only SSH tunnels reach it. No pairing code is needed then. |
| Announce | on | Other editors on the LAN find this one. There are no announcements in SSH-only mode. |
| Port | 1062 | TCP port of the link server. |
Remote engine process
Every editor document renders in an engine process. That process can also run on another device, while the editor stays on your PC: the device loads its data through Fileserve from your machine and renders the scene you edit.
- In a scene viewport's toolbar, click Activate Remote Process.
- The Remote Connection dialog lists DETECTED DEVICES (Android devices connected over USB). Start builds the engine process for the device if needed, starts it there and connects through the cable. Alternatively, under BY ADDRESS, type the Device IP Address of a device that already runs the engine process and the File Server IP Address it should use to reach this PC, then click Connect. Launch Fileserve starts Fileserve if it is not running.
- Link Camera on Remote Process in the viewport toolbar makes the device use the viewport's camera.
Device setup (Android SDK, USB debugging, the device log) is covered in Shipping.
Troubleshooting
| Problem | Fix |
|---|---|
| The host isn't in the list | Discovery uses UDP broadcast, which doesn't cross routers, VPNs or SSH. Type the address instead. |
| "The host did not answer" | The host's link server is off, a firewall blocks TCP 1062, or the two editors are different versions. |
| "Too many wrong pairing codes from this machine" | Wait a minute, then link with the current code. |
| "ssh ended: Permission denied" | ssh needs a key, an agent or Tailscale SSH. Check that ssh -o BatchMode=yes <host> works in a terminal. |
| "ssh ended: ... Connection timed out" | The SSH host is unreachable or asleep. With Tailscale, check tailscale status. |
| "Different project: telemetry only" | Documents mirror only between editors with the same project open. Use the Stream page to see the host's view. |
| "N assets differ from the host's" | Your project's assets aren't the same version as the host's, so a mirrored scene may render differently. Sync the project. |
| A document won't mirror | It's open here with unsaved changes. Save or revert it first. The log names the document and the reason. |
| The link server could not listen on its port | Another editor on this machine uses it. Change Port in the preferences, or use -linkPort. |
| A popup blocks an editor nobody sits at | Start that editor with -unattended. |