Skip to content
OffsiteDocs

Always reachable

By default the Offsite agent runs in your login session. That is enough for most days: the host answers while you are logged in, and sessions survive the app closing, the network dropping and the lid closing.

It is not enough for one case: the machine restarts while you are away, and nobody logs in. Always reachable fixes that case.

What it does

Section titled “What it does”

Offsite registers its agent as a system service, so the host comes back on its own after a restart, before any user logs in.

Platform Mechanism
macOS a LaunchDaemon, installed once with your administrator password
Linux a systemd user service plus loginctl enable-linger <user>

You can switch it on during setup or later from the host’s settings.

What it costs

Section titled “What it costs”
  • One administrator prompt on macOS, at the moment you enable it. macOS shows it as “Offsite wants to make changes.”
  • A background item. macOS will notify you that software from “RapidRocket GmbH” can run in the background — that is the certificate holder, which is Offsite’s publisher. You can review it under System Settings › General › Login Items & Extensions.

Declining costs you nothing else: the rest of Offsite keeps working and the host stays reachable while you are logged in.

What it pairs with

Section titled “What it pairs with”

Always reachable covers the login: the host answers even when nobody is signed in at that machine. Two companions complete the picture:

Details

Section titled “Details”
  • Sessions survive a host restart in two steps: tmux sessions are recreated from Offsite’s own session state, and each agent is resumed with its own CLI mechanism (claude --resume, codex resume), wired per tool. Offsite keeps an archive copy of the resume artefacts so a transcript cleanup on the CLI side cannot orphan a session.
  • Reboot restore is Offsite’s own, rather than global tmux tooling (tmux-resurrect, tmux-continuum) — restore is owned by Offsite’s own state, so it never depends on your tmux configuration.
  • On Linux, a user service without lingering stops at logout. loginctl enable-linger is the whole difference between “survives reboot” and “survives until you log out”.