@evident-ai/cli 3.1.1-dev.fe0815c → 3.2.1-dev.0fe02fb

package/README.md

@@ -111,15 +111,33 @@ 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
   is never deleted, regardless of either rule. Env:
   `EVIDENT_SESSION_CLEANUP_MAX_COUNT`.
+- `--max-active-sessions <n>` — Cap how many sessions the runner will have
+  actively working at once (default: unlimited). Counts sessions with work in
+  flight and is per runner process, not global across runners. Once the cap is
+  reached, new work simply stays pending and is picked up on a later poll tick
+  — nothing is dropped or errored — but a follow-up into a conversation whose
+  session is already active is never blocked, since it costs no extra slot. A
+  legitimately long-running turn holds its slot for as long as it runs
+  (bounded only by the 6h absolute processing ceiling), so pick N with that in
+  mind. After a restart the runner re-adopts work it had already claimed,
+  which can briefly push the active count above the cap — that's deliberate;
+  the cap bounds new dispatch, not re-adoption. An invalid value (`0`,
+  negative, non-numeric) is warned about and falls back to unlimited. Env:
+  `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.
@@ -161,6 +179,8 @@ targets the **production** Evident platform by default.
   the flag wins if both are set.
 - `EVIDENT_SESSION_CLEANUP_MAX_COUNT` — Equivalent to
   `--session-cleanup-max-count`; the flag wins if both are set.
+- `EVIDENT_MAX_ACTIVE_SESSIONS` — Equivalent to `--max-active-sessions`; the
+  flag wins if both are set.
 - `EVIDENT_SESSION_CLEANUP_INTERVAL` — Equivalent to
   `--session-cleanup-interval`; the flag wins if both are set.