Agent Mesh
A mesh pairs your devices into one network, so a session on your laptop can see — and hand work to — sessions on another machine: the always-on box at home, the workstation at the office, a teammate's machine with the right access.

Pairing
One device creates the network and mints a single-use invite; the other joins with it. Both steps end at the same place: a human on each screen comparing what they see before anything is admitted.
On the first device:
lop network init <name>
It creates this device's identity and member row and starts the relay under a user service supervisor — launchd on macOS, systemd --user on Linux. --no-start leaves the relay stopped; a host with no user supervisor runs lop network serve in the foreground.
By default it binds 0.0.0.0:4097; a device that should only dial out passes --listen-address 127.0.0.1 and is reachable only where it connects.
lop network invite --role read --expires 30m
--role is read, drive or admin; --expires is how long the token stays open; --device <id> binds it to one device id so only that device may redeem it. The token is written to a 0600 file and the command prints only the path — never paste the token itself anywhere.
On the second device:
lop network join @<token-file>
Joining shows six digits. Compare them with the code the inviting side shows, and confirm only if they match. --verify compares the 160-bit fingerprint instead. Three bad tries burn the invite. When nobody is at the keyboard, --park starts the pairing and waits: the inviting side answers the queue with lop network confirm <invite-id>, the joining side finishes with join --confirm <code>. No agent path can complete the comparison — that is the interlock, not a gap.
Before admission, a credential share list names what the new device will be given: each credential reads will be served or not offered. The owner may only remove rows from that list, and the joined receipt names the final set. The list appears only when both builds are new enough; an older build on either side shows no list at all, and an absent list does not mean there is nothing to share.
After pairing, lop network credential share <name> --with <device> lends one credential to one device, and lop network credential revoke <name> --from <device> takes it back.

Roles and grants
A role decides what a member may do on your device:
readsees: it can list and view sessions.driveadds the controls: list, view, prompt, steer, stop and slash.adminholds the full vocabulary, including membership changes.
Beyond the role, lop network member grant adds capabilities to a member one at a time — for example move, delete, unattended or broker_credential:
lop network member grant <network> <device-id> move
lop network member grant <network> <device-id> delete
lop network member grant <network> <device-id> unattended
lop network member revoke <network> <device-id> <capability> takes a grant back. unattended is what lets a peer start sessions on this device without approval prompts.
Onboarding another machine
Approval records are how one machine gets set up to reach another:
lop network approvals list
lop network approvals show <apn_id>
lop network approvals request --host <host> --network <network>
lop network approvals approve <apn_id>
lop network approvals deny <apn_id>
lop network approvals withdraw <apn_id>
lop network approvals run <apn_id>
Since 0.84.6 the signed network-only enrollment is the narrow path: it joins the mesh and provisions no logins, tools or account access.
lop network approvals request --network-only \
--host <host> --network <network> --credential-ref <ref>
lop network approvals approve-network-enrollment <apn_id> \
--request-digest <digest>
lop network approvals run <apn_id>
A desktop client that advertises mesh_onboard: 1 exposes the same restricted path.
Readiness is a separate question from membership:
lop network ready --peer <device> --json
Do not offload work on a FAIL. A warn marks equipment that is named but does not hold the verdict.
Across devices
- Sessions across devices —
lop network sessions --peer <peer>lists what that device is running;--all-peersmerges every peer's list.--createstarts one there,--senddelivers a turn,--steerinjects into a running turn,--peekwatches,--stopends it. - Move a conversation —
lop sessions move <id> --to <peer>hands it over, and--to localbrings it home. The session keeps its id and its transcript; the copy on the device it left is deleted unless--keepis given, which leaves the original running and mints a new id for the copy.--waitblocks for the receipt. A wake travels with the move; monitor state does not. A turn in flight refuses the move rather than being interrupted. - From the TUI —
/new remote <peer>starts a session on another device, and/move --to <peer|local>moves the current one.


Trust and incidents
- Removing a member —
lop network member rm <network> <device-id>revokes it and rotates the shared secret. A removed member that wants back in needslop network identity rotatefirst. - Leaving —
lop network disconnectstops trusting the network, closes links and deletes the local secret; the audit trail stays. - An incident —
lop network panicbroadcasts a revoke, rotates the secret, bumps the epoch and marks the network untrusted here. Every other device must be re-admitted before it can connect again. - Re-admitting —
lop network trust <network> --activemarks the network active again on this device. - Diagnosis —
lop network doctor,lop network logandlop network statusanswer reachability, epoch and install-state questions, andlop network peersshows what is reachable right now.