Skip to content
Local OperatorDocs

Workflow automations

Note:

Preview. The full automations guide is being written. These primitives ship today; the guide will cover each one end to end.

Wake pipelineA scheduled wake, fired with or without a terminal openSchedule a wakelop wake create <session> "in 30m" "…"The due time arrivesstored with the session — survives restartsRuntime is livethe session's own scheduler fires itno supervisor neededNothing is runningthe wake supervisor starts a runtimethe session then fires on loadA turn runs — as if a message arrivedmissed while the machine was off? skipped, not replayed60 s minimum recurrence · 16 schedules per session
A scheduled wake, fired with or without a terminal open
  • Scheduled wakes that survive a closed terminal. The agent's wake tool schedules a future turn ("check the build again in 30 minutes"). Schedules persist with the session, and a small wake supervisor starts a runtime when a session's wake is due — even if the terminal that scheduled it is long gone. lop wake status shows the next due wake and whether the supervisor is running.
  • Background jobs that report back. task always runs in the background, bash can (background=true), and every settled job auto-delivers its result when the session is idle. jobs peeks at new output since your last look.
  • lop exec --background detaches a whole task with a log file and exits immediately — the building block for cron jobs and CI steps.

A nightly loop, a build watcher, a research sweep that reports in the morning: all of them are the same three primitives arranged differently.

Schedules are visible where they run — a wake panel in the TUI, a Schedules page in the desktop app:

The wake panel above the TUI composer: two scheduled wakes with their next time, recurrence and message.
The wake panel in the TUI: what this session has scheduled, before it fires.
The desktop app's Schedules page: each task with its next run, cadence and run count.
The same schedules in the desktop app, with run history.

Aida, the built-in chief of staff, is the same machinery on a daily cadence — see Always-on & proactive agents.