Skip to main content

Mobile, Schedules & Background Work

Ordinary local work runs while Locus remains available. An opt-in independent runtime can keep selected agents running after the app closes. The mobile companion connects directly to the Mac through its separate mobile gateway.

Scheduled Agents​

Open the Agent page, choose a saved agent, and use Manage Agent → Add → On a schedule. Review its instructions, model, cadence, and workspace. A saved agent can own several chats and triggers; a schedule retains its linked conversation and exact account/model configuration. Its Agent panel shows controls, the next occurrence, and recorded runs. Use Pause or Run now as needed; the mobile companion also supports schedule controls.

Your companion can be that saved agent, but choosing its name or character never activates a schedule or opts it into continued execution. Its animation reflects actual activity; it is not a separate worker.

A scheduled Agent's instructions, next occurrence, and run history

Demonstration data. Enabled status and actual running chats are shown separately.

Use Activity for recent records and Attention for decisions or recoveries. See Agents & Automation for event triggers, connected-service access, and workflows.

By default, Locus must be running and the Mac available for scheduled work to execute. Closing a window is different from quitting the app. To continue after the app closes, enable the independent runtime and explicitly opt the agent into Keep running when Locus closes. The Mac still needs an active login and must remain awake. Remote execution uses an owned host; Locus does not create a hosted cloud worker.

Managed background services​

Use managed background services for dev servers, watchers, and queue workers that should outlive a single agent turn. They appear above Terminal, remain associated with their workspace, and stop only when you explicitly stop them or the owning backend quits.

Locus Mobile​

Mobile Access is off by default. When enabled, Locus creates a private TLS gateway on your Mac and pairs an iOS or Android device with a five-minute, one-use code. The companion pins the Mac certificate and connects over your LAN or Tailscale; there is no Locus cloud relay.

Mobile Access settings

Pairing Locus Mobile

The companion can:

  • create and continue chats;
  • follow streaming work;
  • stop runs;
  • answer one-time approvals; and
  • run or pause schedules.

Terminal, Browser, file editing, permanent permissions, provider settings, and destructive session actions remain Mac-only. Provider credentials and local agent ports are never exposed to the phone.

Independent and remote work​

Use Settings → Runtimes for independent workers, service health, waiting reasons, and Pause, Resume, or Stop. It is available in direct-download wallet-free Locus, with explicit opt-in for continued work. Desktop browser and computer actions wait for the native app even when the model and agent are still running.

SSH & Remote Runtimes explains host requirements, reviewed snapshots, selected account provisioning, durable approvals, and explicit retrieval of returned changes. Portable packages remain candidate artifacts; the 4.0.0 public download does not provision an always-on hosted worker.

The mobile companion is not a general remote-runtime administration client. Existing mobile task and approval endpoints remain compatible with additive task-history fields; runtime installation and deployment controls are on the Mac. Independent execution does not by itself make the Mac's mobile gateway available after the desktop connection closes.