From 75e6696d9d0e97a4860cb4c1b2bb4a1f01c46ff3 Mon Sep 17 00:00:00 2001 From: Gustavo Madeira Santana Date: Mon, 23 Feb 2026 14:53:46 -0500 Subject: [PATCH] Docs: link cron run-log config from sessions cleanup --- docs/cli/sessions.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/cli/sessions.md b/docs/cli/sessions.md index 658fe50da72..4ed5ace54ee 100644 --- a/docs/cli/sessions.md +++ b/docs/cli/sessions.md @@ -60,6 +60,8 @@ openclaw sessions cleanup --json `openclaw sessions cleanup` uses `session.maintenance` settings from config: +- Scope note: `openclaw sessions cleanup` maintains session stores/transcripts only. It does not prune cron run logs (`cron/runs/.jsonl`), which are managed by `cron.runLog.maxBytes` and `cron.runLog.keepLines` in [Cron configuration](/automation/cron-jobs#configuration) and explained in [Cron maintenance](/automation/cron-jobs#maintenance). + - `--dry-run`: preview how many entries would be pruned/capped without writing. - In text mode, dry-run prints a per-session action table (`Action`, `Key`, `Age`, `Model`, `Flags`) so you can see what would be kept vs removed. - `--enforce`: apply maintenance even when `session.maintenance.mode` is `warn`.