Jev CLI — joshLong145

For noul answers, no. The CLI derives certainty locally as |p - 0.5| times 2 and marks those rows with an asterisk in the table so you do not mistake it for a model-supplied score. choice and score answers do carry the API's own confidence, so the two are not comparable and the asterisk is the only thing telling you which is which.

No. Jev evaluates every question in one call in parallel, so two packs become a single request carrying all eight questions, which the README demonstrates with --dry-run and jq. What does multiply cost is the window: --window 25 by default batches 25 records per call, --window record is one call per record, and --window whole sends the entire input as a single state.

It tries not to. Records the pattern rejects are kept verbatim under _unparsed and counted in a warning, because a log whose format drifted mid-file is itself a finding. On non-JSON input every transform is scored by parse rate over a sample and the run stops to list the candidates if nothing wins or two tie, and a filter matching nothing is an error listing the values the field actually holds.

Redaction runs strictly before the first byte reaches the SDK, and matched values become the literal placeholder rather than disappearing, so whether a request carried credentials stays answerable. Filtering also runs before projection and redaction, so you can filter on an identifier and then scrub it. Every answer is anchored to the lines it came from, and text logs need a transform you write yourself unless they are syslog.

Run ./scripts/install.sh, which puts jcli on your PATH via uv and needs no sudo; then set TYPESAFE_API_KEY, use --api-key-file, or put the key in ~/.config/jcli/config.toml.

--window sets grouping: a number, default 25, gives that many records per call so neighbours share context, record gives one call per record for per-item triage, and whole sends the entire input as one state; every mode is also capped by --max-state-bytes.

Five built in: logs.triage with is_incident, severity, category and actionable; logs.anomaly; security.audit; security.finding; and agent.session, and jcli packs init can scaffold your own.