openclaw - 💡(How to fix) Fix Checkpoint store grows unbounded on VPS (18GB/session) [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#72130Fetched 2026-04-27 05:34:26
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
0
Author
Timeline (top)
closed ×1commented ×1

Root Cause

Root cause (初步分析):

  • Checkpoints use a git-backed content-addressable store
  • Binary blobs (, , session JSONs) are stored with near-zero delta compression
  • Checkpoints are created on every terminal command, not just meaningful state changes
  • No retention policy, no size limits, no compression

Fix Action

Fix / Workaround

Workaround: Manual deletion of \ periodically

RAW_BUFFERClick to expand / collapse

Description: The Hermes checkpoint store grows to multi-GB per session, making it unusable on server/VPS deployments.

Observed: 5 sessions over ~2 days on a VPS produced ~18GB in .

Storage math:

  • 18GB / 5 sessions = ~3.6GB/session
  • With 10 agents on one machine: ~36GB/session, potentially terabytes/month

Root cause (初步分析):

  • Checkpoints use a git-backed content-addressable store
  • Binary blobs (, , session JSONs) are stored with near-zero delta compression
  • Checkpoints are created on every terminal command, not just meaningful state changes
  • No retention policy, no size limits, no compression

Impact:

  • VPS: disk exhaustion within days
  • Multi-agent: projected multi-TB/month per machine
  • Not suitable for any server deployment

Environment:

  • VPS (not desktop)
  • Hermes Agent running on OpenClaw gateway
  • Version: 2026.4.24-beta.1

Expected behavior:

  • Checkpoints should either: (a) not be enabled by default on server deployments, (b) have bounded retention/size limits, (c) use delta compression for binary blobs

Workaround: Manual deletion of \ periodically

Additional notes:

  • Each checkpoint commit stores full binary snapshots of SQLite state.db and JSON cache files
  • Git's delta compression works poorly on these binary blobs
  • Temp pack files () were also accumulating during active sessions

extent analysis

TL;DR

Implement a retention policy or size limits for checkpoints to prevent excessive storage growth.

Guidance

  • Review the checkpoint creation process to determine if checkpoints can be created only on meaningful state changes instead of every terminal command.
  • Consider implementing delta compression for binary blobs or using a more efficient storage mechanism.
  • Evaluate the feasibility of enabling compression for SQLite state.db and JSON cache files.
  • Develop a script to automate the manual deletion of checkpoints periodically, as a temporary workaround.

Example

No code snippet is provided as the issue does not imply a specific programming language or API.

Notes

The provided information suggests that the issue is specific to server/VPS deployments, and the workaround may not be suitable for all environments. The root cause analysis highlights the need for a retention policy, size limits, or compression to mitigate the storage growth.

Recommendation

Apply workaround: Implement a script to automate the manual deletion of checkpoints periodically, as this is a temporary solution that can help mitigate the issue until a more permanent fix is available. This is chosen because it is a concrete step that can be taken immediately to address the problem, even if it is not a complete solution.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING