For long-running tasks, automatic compaction, persistent goals, heartbeats, schedules, autonomous mode, and retained subagents preserve progress across turns and terminal sessions.[1] Daemon-backed sessions keep running when the terminal disconnects and can be reattached later using prime-agent attach <agent> — see Daemon architecture for the underlying implementation.[1]
/goal keeps an objective and its progress active across turns until it is completed, paused, or cleared.[1]
As of v0.2.9, scheduled heartbeat prompts steer by default — interrupting the current turn — with a steer/follow_up delivery mode selectable via /heartbeat --steer|--follow-up and the rlm_heartbeat skill's delivery_mode argument.[2] In v0.3.3, the bundled orchestration heartbeat skill was removed from the model system prompt.[3] A heartbeat is a scheduled prompt automatically injected into a running agent's turn cycle, enabling self-correction or progress reporting without requiring a human message. Heartbeat delivery timing and mode determine when and how Prime Agent receives steering feedback during long-running task execution.
deleteRlmSubagentRuntime in SubagentRuntimeHost accepts an optional session parameter; the session is absent when the target child is still in a passive (snapshotted but not resident) state.[4] A passive subagent has its state saved to disk but is not actively consuming memory or compute; it can be restored to a resident (active, in-memory) state on demand.
Sources