T06 · System Persistence
- Location
SKILL.md:151- Finding
Recurring cron job enables persistent autonomous agent execution
- Content
View full analysis
Heartbeat" \ --schedule "every 30m" \ --agent-id "" \ --session-key "agent::main" \ --session-target "isolated" \ --message "Read HEARTBEAT.md if it exists (workspace context). Follow it strictly. Do not infer or repeat old tasks from prior chats. If nothing needs attention, reply HEARTBEAT_OK." \ --delivery "announce" ``` ### Technical Analysis The documented workflow registers a recurring cron job that invokes an isolated agent every 30 minutes. The scheduled job survives completion of the original skill invocation and instructs the agent to read and follow persistent instructions from `HEARTBEAT.md`. Because the effective behavior is stored in a mutable workspace file, later changes to `HEARTBEAT.md` can alter what the recurring agent does without changing the reviewed cron command. The documentation does not prescribe an expiration time, execution limit, restricted tool policy, or mandatory confirmation immediately before creating the schedule. This is persistent cross-session execution and therefore matches `T06: System Persistence`, even though persistence is presented as an intended feature. ### Attack Path 1. A user or agent follows the extraction workflow and creates a new agent workspace. 2. Instructions are placed in the workspace's `HEARTBEAT.md`. 3. The documented `openclaw cron add` command registers a job that runs every 30 minutes. 4. The initiating session ends, but the cron job remains active. 5. Each scheduled invocation starts an isolated agent turn and directs it to follow the workspace instructions. 6. If `HEARTBEAT.md` is subsequently modified, future turns may execute the changed instructions with whatever tools and permissions are available to the extracted agent. ### Im ...[truncated 484 chars]- Remediation
View remediation
