JevTO / Documentation

JevTO privacy, remote ranking, and troubleshooting

Captures and recall are local. Remote Jev ranking depends on your mode and configuration; setting an OpenRouter key is an opt-in in the default auto mode.

Know your active mode

Mode and network behavior
Mode	Behavior
`auto` (default), no key	Deterministic local selection; no Jev request.
`auto`, OpenRouter key present	Eligible output with a goal can use Jev under a current-workspace policy. Cache hits, unrankable output, and fallback can avoid a call.
`rules`	Deterministic selection with no Jev request, even with a key present.
`adaptive`	The explicit route requires a remote policy and `--allow-remote-jev`.

Terminal

jevto run --mode rules -- cargo test --workspace
jevto doctor --json

For automatic agent hooks, set JEVTO_MODE=rules in the environment of the agent process. doctor reports mode and conditional network eligibility without contacting a provider or displaying the key.

What remote ranking sends

JevTO may send the session goal plus bounded snippets or line-shape digests of the command output or diff being ranked to Jev through OpenRouter. In auto mode, the implicit policy is limited to the current workspace. Requests are capped at 64 KiB, use an eight-second timeout, and are cached by content.

Secret-looking goals and sections are filtered, but a pattern filter cannot guarantee removal of all sensitive data. Use rules-only mode for material you cannot send to a third party. Provider usage is separate from JevTO's local output estimates; consult your provider account for billing and data terms.

Jev ranks candidate evidence; local code owns permissions, protected-line rules, and fallback. A provider error or unsuitable response falls back to the rules view. “No relevant evidence” can be a successful remote request that still falls back. Missing usage or cost remains unknown, not zero.

Local capture and retention

The default capture store is %LOCALAPPDATA%\JevTO on Windows or ~/.local/share/jevto on Unix-like systems. You can select a separate store with the global --store-dir option.

Stdout and stderr are stored separately with hashes.
The default retention is 24 hours and the store ceiling is 1 GiB. Do not treat captures as permanent backups; use jevto purge to remove expired captures.
The store is not encrypted at rest. Output can contain secrets even though command arguments and environment variables are not separately stored.
The Claude auto-route stores your prompt locally as the session goal.
The CLI does not send telemetry. Rules-only selection makes no provider call.

What “exact recall” means

Recall returns the historical bytes in the selected captured stream or section, without rerunning the command or generating a paraphrase. It cannot recover bytes a host never provided, an incomplete oversized capture, or a capture that was purged. Check the receipt and completeness information for the run.

Terminal

jevto recall CAPTURE_ID
jevto recall CAPTURE_ID --stream stderr --lines 1:10

Full recall restores both original streams. Line-range and section recall print the selected bytes to stdout; --stream selects the source for a line range.

Troubleshooting and reports

If a hook is not routing, start with jevto doctor --json, test the explicit wrapper, and inspect the installer's preview. Unsupported shell syntax should stay native. See integration removal commands to undo project hooks.

Use a sanitized fixture in bug reports. Do not post provider keys, raw private captures, or your full agent configuration. For security issues, follow the security policy.