T06 · System Persistence
- Location
SKILL.md:78- Finding
Persistent Recurring Agent Execution Through Scheduled Jobs
- Content
View full analysis
0 → sessions_send to main: list timed-out topics, suggest creating tasks in tasks/\n" }, "sessionTarget": "isolated", "delivery": { "mode": "none" } } ``` ```json { "schedule": { "kind": "every", "everyMs": 86400000 }, "payload": { "kind": "agentTurn", "message": "【Daily Multi-Topic Board Maintenance】\n\nStep 1: Update aging days\n- Read memory/multi-topic.md\n- For each 🔥 Pending entry: today - discovered_at = days\n- IF no days field → append to entry\n- IF days changed → update in place\n- Write back to multi-topic.md (only touch the days field)\n\nStep 2: Timeout stats and alert\n- Count entries: days >= 3 AND task = none\n- IF > 0 → sessions_send to main: N topics 3+ days with no task: [topic names]\n- IF = 0 → silent end\n" }, "sessionTarget": "isolated", "delivery": { "mode": "none" } } ``` ### Technical Analysis The bootstrap procedure creates cross-session behavior rather than limiting execution to an explicit, current-session invocation. The recurring jobs are configured to: - Run autonomous agent turns every four hours and ...[truncated 2657 chars]- Remediation
View remediation
