MOSHLINE / DOCSField manualOpen +Close −
Moshline field manual / P0
Know what is connected. Know what can act.
Install the Host Helper, understand which approval routes can reach an agent, and recover a Mac daemon without guessing. These pages describe current behavior, including safe fallbacks.
00—03 / OPERATING PATHS
Choose the result you need
Start with setup when the host is new. Use the operating pages when a connection, approval, or background service needs explanation.
Start / 00
Install and pair a host
Run Quick Setup, scan the Host Helper QR, connect the terminal, then verify agent events.
Open operating path →Host / 01
Host Helper
Understand setup, health checks, independent updates, compatibility, and the files installed on your host.
Open operating path →Control / 02
Approvals and Confirm on Mac
See which paths can remotely approve, which remain host-local, and what happens when a relay expires.
Open operating path →Repair / 03
Host daemon is not reachable
Inspect and restart the macOS LaunchAgent when Doctor cannot reach the daemon or attach socket.
Open operating path →ROUTE INTEGRITY
Truth before convenience
Moshline never treats a visible approval card as proof that the phone can answer it. The event route, provider protocol, relay deadline, and risk policy decide which action is shown.
- 01The agent process, repository, and credentials remain on your host.
- 02A real SSH/Mosh terminal remains the full-context recovery path.
- 03Unsupported or expired remote decisions fall back to the provider on the Mac.
- 04Host Helper and App releases are independent and use a versioned host protocol.