JevTO / Demo

Watch JevTO select a failing test result and recall it

One deliberately failing test among 150 passing tests. The same command, a smaller view, and the original bytes available on demand.

Actual CLI execution on a generated fixture, recorded with VHS. Deliberate typing and reading holds are edited demonstration timing, not a speed benchmark. Rules-only mode; no provider call. Silent video with captions.

Try JevTODownload videoRecording source

What the recording shows

1. cargo test runs 151 generated tests. One test deliberately fails because the parser accepts a leading space.
2. jevto run --mode rules -- cargo test keeps the failure and assertion visible, folds passing-test output, and preserves the nonzero exit.
3. Recall reads the stored stdout. The video shows its first four lines; the verification checks the complete stored stdout and stderr byte for byte. The recording uses a separate demo capture store.

The fixture is synthetic; the commands and their output are real. Recording verification includes the executable version/hash, capture identity, exit status, and recall checks. It is not a live coding-agent task or a savings benchmark.

Help test the next real workflow

Try the explicit wrapper on one verifier in a project you know. Then report your OS, host version, command, whether installation worked, whether you needed recall, and any missing evidence. Reports of “no useful reduction” are useful too.

Share a first-run report · View the repository