@evident-ai/cli 3.1.1-dev.2b250ad → 3.1.1-dev.2b780b5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -94,7 +94,53 @@ Options:
94
94
  - `-c, --conversation <id>` — Process only this specific conversation.
95
95
  - `--idle-timeout <seconds>` — Exit after N seconds with no pending work (useful
96
96
  in CI to avoid polling indefinitely).
97
+ - `--opencode-start-timeout <seconds>` — How long to wait for OpenCode to become
98
+ healthy when the runner starts it itself (default: `180`). On expiry the runner
99
+ warns and comes online anyway rather than failing. Env:
100
+ `EVIDENT_OPENCODE_START_TIMEOUT` (seconds).
101
+ - `--claude-usage-reporting <mode>` — Whether to report the local Claude Code
102
+ subscription's rate-limit usage to Evident, so it shows on the runner page:
103
+ `auto` (default) reports it when a usable Claude Code login is found on this
104
+ machine and stays silent otherwise; `on` forces reporting and warns loudly (and
105
+ keeps retrying) if no usable login is found; `off` disables it entirely — no
106
+ Claude credential is ever read. An unrecognized value falls back to `auto` with
107
+ a warning. Env: `EVIDENT_CLAUDE_USAGE_REPORTING`.
97
108
  - `--json` — Output in JSON format (forces non-interactive mode).
109
+ - `--session-cleanup-max-age <duration>` — Delete OpenCode sessions idle longer
110
+ than this window (format `<number><unit>`, unit one of `s, m, h, d` — e.g.
111
+ `7d`, `24h`). Setting this (or `--session-cleanup-max-count`) is what enables
112
+ cleanup — there is no separate on/off flag. An invalid value is warned about
113
+ and ignored, which can leave cleanup off if it was the only rule set. Env:
114
+ `EVIDENT_SESSION_CLEANUP_MAX_AGE`.
115
+ - `--session-cleanup-max-count <n>` — Keep only the newest N OpenCode sessions
116
+ by last activity, deleting the rest. Also enables cleanup; combines with
117
+ `--session-cleanup-max-age` as OR. A session with a turn actively in progress
118
+ is never deleted, regardless of either rule. Env:
119
+ `EVIDENT_SESSION_CLEANUP_MAX_COUNT`.
120
+ - `--max-active-sessions <n>` — Cap how many sessions the runner will have
121
+ actively working at once (default: unlimited). Counts sessions with work in
122
+ flight and is per runner process, not global across runners. Once the cap is
123
+ reached, new work simply stays pending and is picked up on a later poll tick
124
+ — nothing is dropped or errored — but a follow-up into a conversation whose
125
+ session is already active is never blocked, since it costs no extra slot. A
126
+ legitimately long-running turn holds its slot for as long as it runs
127
+ (bounded only by the 6h absolute processing ceiling), so pick N with that in
128
+ mind. After a restart the runner re-adopts work it had already claimed,
129
+ which can briefly push the active count above the cap — that's deliberate;
130
+ the cap bounds new dispatch, not re-adoption. An invalid value (`0`,
131
+ negative, non-numeric) is warned about and falls back to unlimited. Env:
132
+ `EVIDENT_MAX_ACTIVE_SESSIONS`.
133
+ - `--session-cleanup-interval <duration>` — How often the cleanup sweep runs
134
+ (default: `1h`). An invalid value falls back to the default rather than
135
+ disabling cleanup. Env: `EVIDENT_SESSION_CLEANUP_INTERVAL`.
136
+ - `--enable-file-sync-to <dir>` — Let the runner write files Evident has queued
137
+ for it into this directory — it collects them as part of the polling it
138
+ already does, so they land a couple of seconds after you hand them over.
139
+ Repeatable (up to 16); each value must be absolute once a leading `~` is
140
+ expanded, and the filesystem root is rejected. Omit it entirely and the
141
+ runner collects nothing and refuses any queued file, telling you why. Use
142
+ `--enable-file-sync-to ~/.claude` to connect a Claude subscription from the
143
+ web — see the website's Model providers doc.
98
144
 
99
145
  ## Global flags
100
146
 
@@ -118,6 +164,20 @@ targets the **production** Evident platform by default.
118
164
  keychain login from `evident login`).
119
165
  - `EVIDENT_API_URL` — Override the API base URL (equivalent to `--endpoint`).
120
166
  - `EVIDENT_TUNNEL_URL` — Override the tunnel relay URL (equivalent to `--tunnel`).
167
+ - `EVIDENT_CLAUDE_USAGE_REPORTING` — Equivalent to `--claude-usage-reporting`; the
168
+ flag wins if both are set.
169
+ - `EVIDENT_LOG_LEVEL` — Equivalent to `--log-level`; the flag wins if both are
170
+ set, and `-v`/`--verbose` also outranks this env var.
171
+ - `EVIDENT_OPENCODE_START_TIMEOUT` — Equivalent to `--opencode-start-timeout`
172
+ (seconds); the flag wins if both are set.
173
+ - `EVIDENT_SESSION_CLEANUP_MAX_AGE` — Equivalent to `--session-cleanup-max-age`;
174
+ the flag wins if both are set.
175
+ - `EVIDENT_SESSION_CLEANUP_MAX_COUNT` — Equivalent to
176
+ `--session-cleanup-max-count`; the flag wins if both are set.
177
+ - `EVIDENT_MAX_ACTIVE_SESSIONS` — Equivalent to `--max-active-sessions`; the
178
+ flag wins if both are set.
179
+ - `EVIDENT_SESSION_CLEANUP_INTERVAL` — Equivalent to
180
+ `--session-cleanup-interval`; the flag wins if both are set.
121
181
 
122
182
  Authentication precedence for `run`: `EVIDENT_RUNNER_KEY`/`EVIDENT_AGENT_KEY`
123
183
  (tied; `EVIDENT_RUNNER_KEY` wins if both are set) → `EVIDENT_TOKEN` →