How do I install the Openclaw Session Cleanup skill?

Run npx skillmds@latest add dvcrn/openclaw-session-cleanup in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Openclaw Session Cleanup safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Openclaw Session Cleanup?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Openclaw Session Cleanup free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Openclaw Session Cleanup?

dvcrn (@dvcrn) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Openclaw Session Cleanup by dvcrn — Agent Skill

Name: Openclaw Session Cleanup
Rating: 4.5 (4 reviews)
Author: dvcrn

Openclaw Session Cleanup

Diagnose and stabilize long-running OpenClaw deployments that accumulate stale sessions, unreaped agents, browser-control timeouts, gateway websocket 1006 closures, or memory pressure on small VPS hosts. Use when OpenClaw shows too many active sessions, browser control service timeout, gateway abnormal closure, or needs a cleanup/watchdog/sane runtime limits playbook.

dvcrn Updated Sep 8, 2026 32 repo stars

File contents

OpenClaw Session Cleanup

Use this skill when the runtime becomes unstable after long uptime, especially on small hosts such as 1 vCPU / 2 GB RAM.

Trigger Pattern

Treat these as the main signals:

Sessions: 10+ active
Agents: 5+
browser control service timeout
gateway 1006 abnormal closure
repeated gateway disconnects or slow recovery after idle periods

What To Do

Inspect the current runtime state.
Prune stale sessions first.
If the runtime stays unhealthy, clear sessions.
Reduce runtime ceilings for sessions, agents, and browsers.
Add recurring cleanup and a watchdog when the host is expected to run for days.

Immediate Commands

Run:

openclaw sessions
openclaw sessions prune
openclaw status

If the runtime is still unhealthy, escalate to:

openclaw sessions clear
openclaw status

Healthy target after cleanup:

Sessions: 1-3
Agents: 3
Gateway reachable
browser running

Safe Runtime Defaults

For 1 vCPU / 2 GB RAM, prefer:

maxSessions = 5
sessionTTL = 30m
maxAgents = 3
maxBrowsers = 1
swap = 2G

Use the starter config at {baseDir}/templates/openclaw.json.

Automation

Install periodic pruning:

bash "{baseDir}/scripts/install-cron-prune.sh"

Install watchdog unit files:

bash "{baseDir}/scripts/install-watchdog.sh"

Render a tuned runtime config:

bash "{baseDir}/scripts/render-openclaw-config.sh"

Browser Constraint

Treat browser control as the heaviest resource consumer on a small VPS.

Recommended mode:

openclaw browser start --single

Swap

If the host has no swap, add 2G:

fallocate -l 2G /swapfile
chmod 600 /swapfile
mkswap /swapfile
swapon /swapfile
free -h

References

Detailed runbook: {baseDir}/docs/openclaw.session_cleanup_v1.md
Runtime template: {baseDir}/templates/openclaw.json
Watchdog service: {baseDir}/templates/openclaw-watchdog.service
Watchdog timer: {baseDir}/templates/openclaw-watchdog.timer

---name: openclaw-session-cleanupdescription: Diagnose and stabilize long-running OpenClaw deployments that accumulate stale sessions, unreaped agents, browser-control timeouts, gateway websocket 1006 closures, or memory pressure on small VPS hosts. Use when OpenClaw shows too many active sessions, browser control service timeout, gateway abnormal closure, or needs a cleanup/watchdog/sane runtime limits playbook.---# OpenClaw Session CleanupUse this skill when the runtime becomes unstable after long uptime, especially on small hosts such as `1 vCPU / 2 GB RAM`.## Trigger PatternTreat these as the main signals:- `Sessions: 10+ active`- `Agents: 5+`- `browser control service timeout`- `gateway 1006 abnormal closure`- repeated gateway disconnects or slow recovery after idle periods## What To Do1. Inspect the current runtime state.2. Prune stale sessions first.3. If the runtime stays unhealthy, clear sessions.4. Reduce runtime ceilings for sessions, agents, and browsers.5. Add recurring cleanup and a watchdog when the host is expected to run for days.## Immediate CommandsRun:```bashopenclaw sessionsopenclaw sessions pruneopenclaw status```If the runtime is still unhealthy, escalate to:```bashopenclaw sessions clearopenclaw status```Healthy target after cleanup:- `Sessions: 1-3`- `Agents: 3`- `Gateway reachable`- `browser running`## Safe Runtime DefaultsFor `1 vCPU / 2 GB RAM`, prefer:- `maxSessions = 5`- `sessionTTL = 30m`- `maxAgents = 3`- `maxBrowsers = 1`- `swap = 2G`Use the starter config at `{baseDir}/templates/openclaw.json`.## AutomationInstall periodic pruning:```bashbash "{baseDir}/scripts/install-cron-prune.sh"```Install watchdog unit files:```bashbash "{baseDir}/scripts/install-watchdog.sh"```Render a tuned runtime config:```bashbash "{baseDir}/scripts/render-openclaw-config.sh"```## Browser ConstraintTreat browser control as the heaviest resource consumer on a small VPS.Recommended mode:```bashopenclaw browser start --single```## SwapIf the host has no swap, add `2G`:```bashfallocate -l 2G /swapfilechmod 600 /swapfilemkswap /swapfileswapon /swapfilefree -h```## References- Detailed runbook: `{baseDir}/docs/openclaw.session_cleanup_v1.md`- Runtime template: `{baseDir}/templates/openclaw.json`- Watchdog service: `{baseDir}/templates/openclaw-watchdog.service`- Watchdog timer: `{baseDir}/templates/openclaw-watchdog.timer`

Frequently asked questions