Nothing that passed here runs again

What your machine reuses Checks, tests, compiled code.

hushrun: lint skipped: this exact code passed just now (saves 0.2s)
hushrun: unit passed in 3s; reusing 98 tests saved about 1s; it won't run again on this code
hushrun: build: 319 of 360 crates reused, 41 built, saving about 3m 39s

• A check that passed here

  When a check passed on this machine on the same files, it skips and exits 0, whatever the branch or the commit. So a second worktree, a fresh clone or your agent's next run skips what you already passed. Change one file, and it runs.

  How a skip works

• Tests that already passed

  When a check's code changed, it can leave out the tests that already passed on the files they read, and run the rest. Results on this machine are enough. It's off until you turn it on, check by check.

  What it works with

• Compiled code

  Code compiled once is kept, and a later compile with the same inputs reuses it, in any worktree or fresh clone. It's free and needs no account. It's off until you turn it on, once per machine.

  What it works with

Each line is hushrun's output as its docs print it: an example of what it says, not a measurement.

Set it up on your machine One command, no account.

At your repository's root, run npx hushrun init --local. It sets the repository up as init does, without an organization, and shows every change before making it.

1. It wraps your checks

   Each check runs through hushrun where it is, in a script or in CI's files. The command you type stays the same.

2. It gets your agent ready

   It writes the files coding agents read, so your agent runs the checks the same way. A coding agent runs init itself with --yes.

3. It checks before a push

   npx hushrun ready says which checks haven't passed here. The pre-push hook holds a coding agent's push until they pass, and only warns you.

4. Turn on more reuse when you want it

   Test reuse is off until you set tests for a check in hushrun.yaml. Reusing compiled code is off until you run hushrun build on, once per machine.

Everything --local sets up, and how to share later: Use hushrun without an account.

Questions about local use

Do I need an account?

No. npx hushrun init --local needs no sign-in, no organization and no machine key. Skips, test reuse and compiled-code reuse all work with results kept on this machine.

Does it work with my coding agent?

Yes. init writes the files coding agents read, so your agent runs the checks through hushrun: it skips what you passed on the same files, and you skip what it passed. The pre-push hook holds its push until the checks pass here.

Does CI skip what passed on my laptop?

Not with results kept here: CI doesn't see them, so it runs every check. For that, results go through an organization, free to start. CI with hushrun

How long are results kept?

30 days after the run. hushrun checks for old results at most once a day.

What does it cost?

Nothing. The CLI is free, and so is keeping results on your own machine.