@evident-ai/cli 3.6.1-dev.6d23da1 → 3.6.1-dev.6e5719c

package/README.md

@@ -63,6 +63,21 @@ Show the currently authenticated user for the current endpoint.
 evident whoami
 ```
 
+### `evident status`
+
+Check whether the configured credentials can reach Evident. It resolves
+credentials the same way `evident run` does: `EVIDENT_RUNNER_KEY` /
+`EVIDENT_AGENT_KEY` → `EVIDENT_TOKEN` → credentials stored by `evident login`,
+then calls `GET /me` to confirm they are accepted.
+
+```bash
+evident status
+```
+
+Options:
+
+- `--json` — Output in JSON format.
+
 ### `evident run`
 
 Connect to Evident and serve your runner. `evident run` authenticates, resolves
@@ -98,10 +113,13 @@ Options:
   healthy when the runner starts it itself (default: `180`). On expiry the runner
   warns and comes online anyway rather than failing. Env:
   `EVIDENT_OPENCODE_START_TIMEOUT` (seconds).
-- `--opencode-version <v1|v2>` — Which OpenCode major version to launch: `v1` or
-  `v2` (default: `v1`). Env: `EVIDENT_OPENCODE_VERSION`. When selected, the CLI
-  starts or attaches to `opencode2` and authenticates its local requests with the
-  generated server credential when it starts the process. V1 remains the default.
+- `--opencode-version <v1|v2|auto>` — `auto` (default) checks for a running server
+  on the selected port, then uses your installed binary if no server is identified.
+  Use `v1` or `v2` to skip server-protocol detection. If both protocol probes require
+  credentials, the CLI reports the ambiguity rather than guessing. Env:
+  `EVIDENT_OPENCODE_VERSION`. When `evident run` starts V2, it generates a server
+  password for its requests. If you started a released V2 that needs a password this
+  command does not have, the CLI identifies it but does not join it.
 - `--litestream-config <path>` — Start `litestream replicate` for the OpenCode
   session database with this config file. Use this for runner images that persist
   the session database; the file is produced by `runner-synchroniser litestream-config`.
@@ -184,6 +202,12 @@ Options:
   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`.
+- `--session-archive` — Opt in to uploading full OpenCode transcripts as JSON
+  archives to the runner's durable-state bucket. Off by default. Env:
+  `EVIDENT_SESSION_ARCHIVE` (set to `on`, `true`, or `1`; the flag wins).
+- `--session-archive-interval <duration>` — How often changed sessions are
+  archived (default: `1h`). An invalid value warns and falls back to `1h`. Env:
+  `EVIDENT_SESSION_ARCHIVE_INTERVAL` (the flag wins).
 - `--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.
@@ -192,6 +216,12 @@ Options:
   runner collects nothing and refuses any queued file, telling you why. Use
   `--enable-file-sync-to ~/.claude` to connect a Claude subscription from the
   web — see the website's Model providers doc.
+- `--enable-file-sync-to-exact-file <path>` — Let the runner write files Evident has
+  queued for it to exactly this one file; it does not grant the directory holding it.
+  Repeatable (up to 16); each value must be absolute once a leading `~` is
+  expanded, and the filesystem root is rejected. Use
+  `--enable-file-sync-to-exact-file ~/.local/share/opencode/mcp-auth.json` for
+  OpenCode's MCP token store.
 
 ## Global flags
 
@@ -233,7 +263,7 @@ targets the **production** Evident platform by default.
 - `EVIDENT_OPENCODE_START_TIMEOUT` — Equivalent to `--opencode-start-timeout`
   (seconds); the flag wins if both are set.
 - `EVIDENT_OPENCODE_VERSION` — Equivalent to `--opencode-version`; the flag wins
-  if both are set. Defaults to `v1`.
+  if both are set. Accepts `v1`, `v2`, or `auto`. Defaults to `auto`.
 - `EVIDENT_SESSION_CLEANUP_MAX_AGE` — Equivalent to `--session-cleanup-max-age`;
   the flag wins if both are set.
 - `EVIDENT_SESSION_CLEANUP_MAX_COUNT` — Equivalent to
@@ -242,6 +272,14 @@ targets the **production** Evident platform by default.
   flag wins if both are set.
 - `EVIDENT_SESSION_CLEANUP_INTERVAL` — Equivalent to
   `--session-cleanup-interval`; the flag wins if both are set.
+- `EVIDENT_SESSION_ARCHIVE` — Enable or disable full transcript archives. Off by
+  default; accepted values are `on`/`true`/`1` and `off`/`false`/`0`. The
+  `--session-archive` flag wins if both are set.
+- `EVIDENT_SESSION_ARCHIVE_INTERVAL` — Equivalent to
+  `--session-archive-interval`; default: `1h`. The flag wins if both are set.
+- `EVIDENT_SESSION_ARCHIVE_FLUSH_MS` — Graceful-shutdown archive flush budget in
+  milliseconds (default: `2000`). The flush is best-effort and may leave changed
+  sessions for a later hourly run.
 - `EVIDENT_SESSION_DB_PROVENANCE_STATE` — Override the path where the CLI stores
   session-database provenance state (default:
   `~/.local/state/evident/session-db-provenance.json`).
@@ -263,8 +301,7 @@ evident login
 
 ### 2. Create a runner
 
-In the Evident web app, create a runner (it runs in local mode). Note its runner
-ID.
+In the Evident web app, create a runner. Note its runner ID.
 
 ### 3. Run it on your machine