Jev Harness CLI

Run npm install -g @jev-harness/cli for a global install, or use npx @jev-harness/cli without installing. A TYPESAFE_API_KEY must be present in the environment before either binary will work.

jev is the unified command line covering ask, models, classify, and eval, so you can debug question design and run evaluations without building an adapter. jev-gate is a small CI and subagent gate that makes one Jev judgment over a git diff, a file, or stdin.

TYPESAFE_API_KEY is required. TYPESAFE_BASE_URL, TYPESAFE_DEFAULT_MODEL, and JEV_TIMEOUT_MS are also honored when set.

The bad item is written as an error line, its index and reason go to stderr, every successful item is still written, and the exit code is 1. Because core's withMapReduce is atomic, a batch rejected with 400, 413, or 422 is retried item by item, up to twice the calls for that batch.

Failures that say nothing about a single item still abort with exit 1 and are not retried item by item: a missing key, 401 or 403, 429, 5xx responses, and network errors.

Cost is one request per item, meaning items multiplied by questions worth of judgments, plus one reduce call when a reduce runs. The --concurrency flag sets item judgments in flight and defaults to 4.

No. The state is sent to TypeSafe's hosted Jev API, so secrets and credentials should not be piped in. The tool is a semantic acceptance check and does not replace tests, linters, typecheckers, or security scanners.