@evident-ai/cli 3.2.1-dev.978ce0d → 3.2.1-dev.a675493

package/README.md

@@ -111,7 +111,10 @@ Options:
   `7d`, `24h`). Setting this (or `--session-cleanup-max-count`) is what enables
   cleanup — there is no separate on/off flag. An invalid value is warned about
   and ignored, which can leave cleanup off if it was the only rule set. Env:
-  `EVIDENT_SESSION_CLEANUP_MAX_AGE`.
+  `EVIDENT_SESSION_CLEANUP_MAX_AGE`. With cleanup off, a runner whose local
+  session store has grown large warns once at startup, on the runner's page,
+  naming this flag — turning cleanup on both stops the store growing further
+  and reclaims disk space already used by deleted sessions.
 - `--session-cleanup-max-count <n>` — Keep only the newest N OpenCode sessions
   by last activity, deleting the rest. Also enables cleanup; combines with
   `--session-cleanup-max-age` as OR. A session with a turn actively in progress
@@ -132,7 +135,9 @@ Options:
   `EVIDENT_MAX_ACTIVE_SESSIONS`.
 - `--session-cleanup-interval <duration>` — How often the cleanup sweep runs
   (default: `1h`). An invalid value falls back to the default rather than
-  disabling cleanup. Env: `EVIDENT_SESSION_CLEANUP_INTERVAL`.
+  disabling cleanup. Each sweep also reclaims disk space freed by the sessions
+  it deleted, so the store shrinks rather than merely stopping its growth. Env:
+  `EVIDENT_SESSION_CLEANUP_INTERVAL`.
 - `--enable-file-sync-to <dir>` — Let the runner write files Evident has queued
   for it into this directory — it collects them as part of the polling it
   already does, so they land a couple of seconds after you hand them over.