@evident-ai/cli 3.1.1-dev.fe0815c → 3.2.0

package/README.md

@@ -117,6 +117,19 @@ Options:
   `--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`.
@@ -161,6 +174,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.