JevTO
JevTO Helpv0.1.1 · experimental

JevTO / Documentation

Install JevTO in one command

Paste the command for your platform. The installer downloads the right binary, verifies it, and sets up PATH. No Rust, administrator access, or JevTO account needed.

Experimental v0.1.1. Linux x86_64, Windows x86_64, and macOS Intel/Apple silicon binaries are available. Host integrations have different coverage; see tested integrations.

1. Install JevTO

PowerShell
irm https://jevto.xyz/install.ps1 | iex

Ready in the same PowerShell window. Read the installer.

Terminal · Bash / Zsh
curl -fsSL https://jevto.xyz/install.sh | sh

Open a new terminal after installation. Read the installer.

Windows installs to %LOCALAPPDATA%\JevTO\bin; macOS/Linux installs to ~/.local/bin. The installer uses the published v0.1.1 release and a pinned SHA-256 check, and checks the downloaded binary's version before replacing an existing installation. It does not install agent hooks.

Then run jevto doctor. It checks configuration without calling a provider or printing your key.

2. Connect Claude Code

In the project where you want automatic output selection, run:

Your project directory
jevto init-claude-auto --workspace . --apply

Start a new Claude Code session in that project. Supported simple test, build, lint, search, and Git commands now route through JevTO. To inspect the changes before applying them, run the same command without --apply. The hook records the current prompt locally as its goal; coverage, RTK conflicts, and removal instructions are in the integration guide.

No API key is needed for rules-only selection. If an OpenRouter key is already configured, default auto mode can enable remote ranking. Use a rules-only session to keep selection local.

3. Or try one command directly

In a Rust project, try the following. The explicit --mode rules keeps this run offline even if an OpenRouter key is already in your environment.

Terminal
jevto run --mode rules -- cargo test --workspace

For another project, replace the program and its arguments after -- with your actual verifier, for example python -m unittest -v. JevTO executes that command with your existing permissions; it does not make the command safe or change its side effects.

Look for the failing test, assertion, exit status, and a recall: line. Already-short or unrecognized output may pass through with little or no reduction. A nonzero test exit remains nonzero.

Recall the captured bytes

Terminal
jevto recall last
jevto recall last --stream stderr --lines 1:10
jevto gain

Full recall restores both stdout and stderr to their original streams. For a line range, the default stream is stdout; add --stream stderr for stderr lines. last selects the newest capture. For parallel sessions, use the specific capture ID printed by your command instead.

To retrieve one omitted section, use jevto recall CAPTURE_ID --section SECTION_ID with the identifiers from the view. Recall returns stored bytes without rerunning the command. It is bounded by what was captured and how long the store retains it.

gain summarizes local receipts. Its output estimates are not proof of lower provider bills.

Manual download or source installation

Choose an archive yourself or build from source

Download JevTO v0.1.1

Choose the archive for your OS and CPU, download its matching .sha256 file, and compare the archive's SHA-256 with that file before extracting it.

Release files and checksum tools
SystemArchive suffixChecksum command
Windows x86_64x86_64-pc-windows-msvc.zipGet-FileHash .\jevto-*.zip -Algorithm SHA256
macOS Apple siliconaarch64-apple-darwin.tar.gzshasum -a 256 jevto-*.tar.gz
macOS Intelx86_64-apple-darwin.tar.gzshasum -a 256 jevto-*.tar.gz
Linux x86_64x86_64-unknown-linux-gnu.tar.gzsha256sum jevto-*.tar.gz

Put the extracted executable in a folder on your PATH, then open a new terminal. On Windows, you can also run .\jevto.exe directly from its extracted folder; on macOS/Linux, use ./jevto. Keep the executable in a stable location before installing a hook.

Or build from the tagged source

With current stable Rust installed:

Terminal
cargo install --git https://github.com/mattbaconz/jevto --tag v0.1.1 --locked jevto
jevto --version
jevto doctor

The version should read jevto 0.1.1. doctor inspects configuration; it makes no provider request and does not print your key.

Update, custom location, or removal

Run the install command again to get the version pinned by the current installer. It verifies the replacement before switching binaries. Set JEVTO_INSTALL_DIR for a custom location; set JEVTO_NO_PATH=1 to leave PATH and shell profiles unchanged. Linux prebuilt releases require x64 and a compatible glibc; Linux ARM and musl/Alpine users should use source installation.

To uninstall, first remove any agent hooks you enabled, then delete the installed jevto / jevto.exe. On macOS/Linux, remove the line ending # JevTO from the shell profile the installer named; a .jevto.bak file preserves its contents before first modification. On Windows, remove the JevTO directory from your user PATH. Local captures are separate; see storage and deletion.

Next: your coding agent

Set up Claude Code with a preview-first, reversible project hook. For a recording of the real CLI on a deliberately failing fixture, watch the demo.

If your first run does not work

  • Command not found: open a new terminal. If another JevTO installation shadows this one, use the full path printed by the installer or remove the older PATH entry. The wrapped tool must also be on PATH.
  • Empty recall: check both output streams and use the explicit capture ID. For a line range, select --stream stderr when appropriate. A capture may also have expired.
  • Unexpected networking: the built-in mode is auto. Use --mode rules per run or JEVTO_MODE=rules for your session.
  • No reduction: short outputs may correctly bypass selection. Report an unsupported format with a sanitized example.

Report a bug. Include JevTO version, OS, the command, expected behavior, and a redacted sample. Never attach API keys or raw private captures.