Disk Cleanup

Automated disk space recovery for OpenClaw deployments. Covers 12 cleanup categories that OpenClaw does not handle natively (as of 2026.3.13).

What OpenClaw Already Handles (skip these)

• - Session store: session.maintenance config (pruneAfter, maxEntries, rotateBytes)
• Sandbox containers: sandbox.prune config (idleHours, maxAgeDays)
• Context pruning: contextPruning config (cache-ttl mode)

What This Skill Handles (the gaps)

#	Category	Typical Growth	Trigger
1	Memory SQLite .tmp-* orphans	Hundreds of MB from failed reindex	Always
2

Memory SQLite VACUUM | Fragmentation after heavy use | --aggressive | | 3 | Docker images/volumes/build cache | GB from sandbox rebuilds | Always | | 4 | Gateway logs (/tmp/openclaw/*.log) | Grows daily | >3 days old | | 5 | /tmp OpenClaw temp files | Patrol/board/cron artifacts | >24h old | | 6 | Workspace .prebind.* backups | Hundreds of MB per backup | >7 days old | | 7 | Delivery queue old entries | Grows with message volume | >7 days old | | 8 | systemd journal | GB on default VPS configs | >500MB | | 9 | npm/yarn/pnpm/bun/prisma/node-gyp cache | GB from skill/plugin installs | >100MB | | 10 | Rotated syslogs + btmp | SSH brute-force logs on public VPS | Always | | 11 | Git workspace .git | Auto-commit growth (board-move etc.) | >200MB | | 12 | QMD/migration artifacts | Stale after backend switch | Auto-detected |

Quick Start

Run directly:

CODEBLOCK0

Schedule as Cron Job

Weekly Sunday 04:00 CET (recommended):

CODEBLOCK1

Or integrate into an existing infra-health-check script by adding a disk usage threshold trigger:

CODEBLOCK2

Environment Variables

Variable	Default	Description
INLINECODE9	INLINECODE10	OpenClaw state directory
INLINECODE11

$(pwd) | Agent workspace root |

Exit Codes

• - 0 — Success (cleaned or nothing to clean)
• INLINECODE14 — Error during cleanup

Output Format

Last line is machine-parseable:

CODEBLOCK3

Safety

• - --dry-run previews all actions without deleting
• SQLite VACUUM only on --aggressive and only when fragmentation ≥5%
• Docker prune only removes dangling (untagged) images; named images are safe
• btmp is truncated (not deleted) — system expects the file to exist
• Journal vacuum installs a persistent 500MB limit to prevent regrowth
• Git gc uses --auto by default; --aggressive only with flag