T06 · System Persistence
- Location
SKILL.md:58- Finding
Persistent System Watchdog with Automated Session-Deletion Capability
- Content
View full analysis
`, ruft für `dashboard:*` / `subagent:*` Keys `POST http://127.0.0.1:18791/api/openclaw/sessions/delete` auf. **Fasst `agent:main:main` NIEMALS an** (hard rule im Script). **Log:** `memory/reply-session-heal.log` (AUTO_HEAL / HEALED / HEAL_FAILED Einträge) **Alarm nur bei HEAL_FAILED:** Wenn stats-server nicht antwortet, wird `memory/reply-session-ALARM.md` geschrieben. Sonst silent. **Test manuell:** `bash /root/.openclaw/workspace/scripts/reply-session-conflict-watchdog.sh` ``` ### Technical Analysis The Skill instructs the operator or agent to maintain a systemd timer under `/etc/systemd/system`, causing a watchdog to run every 60 seconds. The watchdog reads gateway logs and invokes an API capable of deleting sessions. A threshold of one matching log event is sufficient to initiate deletion. A systemd timer is a cross-session persistence mechanism. Its effects continue after the Skill invocation and can survive user logout, application restarts, and software updates. The referenced watchdog implementation is outside the audited project, so the claimed restriction against deleting `agent:main:main` cannot be verified. The low threshold and broad `dashboard:*` and `subagent:*` matching rules ...[truncated 1505 chars]- Remediation
View remediation
