Is it safe to skip tests?

hushrun skips a check only for the exact files, command and check name that passed, signed by your team. It doesn't see environment variables, tool versions or services, so a check that depends on them needs a name for each. When in doubt, it runs.

What does it work with?

Any language, and any command that exits 0 when it passes: tests, lint, typecheck, builds. On macOS, Linux and Windows, in coding agents' sandboxes and in any CI.

How is it different from a build cache?

Nx, Turborepo and Bazel reuse task results inside a build system you adopt. hushrun wraps the commands you already have, in any repository, and shares results between laptops, agents and CI. It works alongside them. How they compare.

What does the hosted service see?

Check names, results, commands, digests and run links. Never your source code or your secrets. Results can also stay on your own machine, and then nothing is sent.

Can someone help us set it up?

Yes. Leave your email in the form below, and Camilo, who builds hushrun, will write to you. You can also start free today.

Never check the same code twice

Lint, tests, typecheck, builds: if you or your agent already ran it on this exact code, hushrun skips it everywhere else, CI included. Skips are free.

Start free Ask for help

Free to start, with GitHub.

Or run this at your repository's root:

$ npx hushrun init

It finds your checks, asks whether to sign in or keep results on this machine with no account, and shows every change before making it.

youon your laptop

lintran
typecheckran
e2eran

your agentsame code

lintskipped
typecheckskipped
e2eskipped

CIafter the push

lintskipped
typecheckskipped
e2eskipped

A check runs once for the same files. Change a file, and it runs again.

Put hushrun in front of your checks. The command you already run stays the same.

Like hushrun run lint -- eslint. npx hushrun init finds your checks and makes the change for you.

It hashes the files
The same files give the same digest, on any branch, commit or machine.
It records each pass, signed
By your laptop, your agent or CI, in a log your team shares.
It skips what already passed
Wherever the same check meets the same files. Anything else runs.

you, on your laptopyour agent, same code

$ hushrun run lint -- eslint
hushrun: lint running: no pass yet for this exact code
hushrun: lint passed in 1s; it won't run again on this code
$ hushrun run typecheck -- tsc --noEmit
hushrun: typecheck running: no pass yet for this exact code
hushrun: typecheck passed in 0.5s; it won't run again on this code
$ hushrun run e2e -- playwright test --project site
hushrun: e2e running: no pass yet for this exact code
hushrun: e2e passed in 16s; it won't run again on this code

$ hushrun run lint -- eslint
hushrun: lint skipped: this exact code passed 1 min ago (saves 1s)
$ hushrun run typecheck -- tsc --noEmit
hushrun: typecheck skipped: this exact code passed 1 min ago (saves 0.5s)
$ hushrun run e2e -- playwright test --project site
hushrun: e2e skipped: this exact code passed 1 min ago (saves 16s)

Real hushrun run output, on this site's own checks.

Nothing skips without proof. Change one file, and the check runs.

same files, same digest
The exact files
Same files, same command, same check. Otherwise, it runs.
a member's machine, your agent, your CI: one log
Signed by your team
A pass counts only when a member's machine, one of your org's agents or your repository's CI signed it.
no proof for one check, so that one runs
When in doubt, it runs
No pass, or one hushrun can't verify: the check runs, and exit codes don't change.

Skips are free. So is the CLI.

hushrun/hushrun, every CI run9 to 11 Nov 2026, oldest first

290checks, in 26 CI runs

171skipped: already passed

1 h 55 minof checks not run again

The CLI is free, and so is the hosted service, up to 2,000 recorded checks a month. Prices are on the pricing page.

ran: no pass yet for this exact code
skipped: this exact code already passed

Counted from the repository's public job logs. A column is one CI run, and a row is one check.

Questions teams ask first

Is it safe to skip tests?: hushrun skips a check only for the exact files, command and check name that passed, signed by your team. It doesn't see environment variables, tool versions or services, so a check that depends on them needs a name for each. When in doubt, it runs.
What does it work with?: Any language, and any command that exits 0 when it passes: tests, lint, typecheck, builds. On macOS, Linux and Windows, in coding agents' sandboxes and in any CI.
How is it different from a build cache?: Nx, Turborepo and Bazel reuse task results inside a build system you adopt. hushrun wraps the commands you already have, in any repository, and shares results between laptops, agents and CI. It works alongside them. How they compare.
What does the hosted service see?: Check names, results, commands, digests and run links. Never your source code or your secrets. Results can also stay on your own machine, and then nothing is sent.
Can someone help us set it up?: Yes. Leave your email in the form below, and Camilo, who builds hushrun, will write to you. You can also start free today.

Try it on one repository

Start free

$ npx hushrun init

Want help setting it up?

Leave your work email, and we'll write back.

Never check the same code twice

Put hushrun in front of your checks. The command you already run stays the same.

It hashes the files

It records each pass, signed

It skips what already passed

Nothing skips without proof. Change one file, and the check runs.

The exact files

Signed by your team

When in doubt, it runs

Skips are free. So is the CLI.

Questions teams ask first

Try it on one repository

Want help setting it up?