Skip to content
Hitchless

Bug reproduction and fix verification for GitHub repos

Every bug report, reproduced before you open it.

Hitchless picks up new issues on your repo, reproduces the bug on the version it was reported against, and hands your team a failing test and a likely cause. When the fix lands, it proves the fix works.

Free for open source. No code changes, no CI config.

Bug Session refresh drops the user after 15 minutes #2841
mk

After upgrading to 4.2.1 our users get logged out mid-session. Can't tell why. Happens "sometimes".

hitchless Reproduced 4 minutes after the report

Fails on v4.2.1 and still fails on main.

$ npx vitest run repro/session-refresh.test.ts
 FAIL  refresh keeps the session alive past expiry
   expected session.user to be defined, got undefined

Likely cause src/session/refresh.ts lines 41 to 58

Fix verified. The same test passes at a1f93c2.

Why teams use it

The slowest part of fixing a bug is proving it exists.

Time to triage

Minutes, not days

Issues arrive already sorted: reproduced, likely, needs more detail, duplicate, or not a bug. Triage becomes a read, not an investigation.

Time to reproduce

Zero engineer hours

No checking out old tags, no guessing at the reporter's setup, no "works on my machine". The failing test is waiting in the issue.

Time back

Start at the fix

Engineers open an issue that already says where it breaks and how to see it. The hours that went to setup go to shipping.

How it works

From "can't reproduce" to a verified fix.

  1. 1

    Connect a repo

    Add Hitchless to a GitHub repository. There is nothing to install in your codebase and nothing to add to CI. It learns how your project builds and runs.

  2. 2

    Bugs get reproduced

    For each new bug report, Hitchless builds the version it was reported against and works out a small test that fails because of the bug. Then it checks whether your latest code still has it.

  3. 3

    Fixes get verified

    When a fix lands, the same test runs against it. You see that it failed before the fix and passes after, so "fixed" means fixed.

What you get

Evidence on every issue, in the place your team already works.

A test that fails

One command you can run yourself, with its output. Not a description of a bug. The bug.

The right version

Reproduced on the version the reporter used, then checked against your default branch, so you know if it is still live.

A likely cause

The files and line ranges most likely responsible, ranked, so the first hour is not spent finding where to look.

Duplicates caught

Reports that fail the same way are linked together, so ten issues about one bug become one piece of work.

Noise filtered

Feature requests, questions and reports missing key details are flagged up front, before anyone spends time on them.

Proof the fix works

The reproduction becomes the acceptance test. It has to fail before the fix and pass after it.

Without Hitchless

  • An issue sits until someone has a free afternoon to dig in.
  • Three rounds of "which version?" and "can you share steps?"
  • An engineer rebuilds an old release to find out it was a config mistake.
  • The fix ships. Nobody is sure it fixed the reported case.

With Hitchless

  • Every bug report is picked up within minutes of being filed.
  • The version, the failing command and its output are on the issue.
  • Reports that are not bugs are labelled before they cost anyone time.
  • The fix is checked against the exact failure the user hit.

Safe on your repo

Built for engineers who read the fine print.

A tool that runs your code and writes on your issues has to earn it. These are the rules Hitchless runs under.

Isolated every time
Each reproduction runs in its own throwaway environment that holds none of your secrets and is destroyed afterwards.
Evidence or nothing
A reproduction only counts if it fails for the reported reason, and fails the same way again. If Hitchless is not sure, it says so.
Quiet until you say so
Start in watch-only mode and review results on your dashboard. Nothing is posted on your issues until you turn posting on.
Never as you
Hitchless only ever writes as its own GitHub app, never from a person's account, and signing in gives it no access to your code.

Pricing

Free for open source. One price for everything else.

Priced per repository. No seats, no usage meters, no surprises.

Open source

For public repositories.

$0forever

  • Bug reproduction on every new report
  • Fix verification
  • Likely cause and duplicate detection
  • A public results page for your project
Start free
For teams

Private repositories

For your company's code.

$99per repo, per month

  • Everything in Open source
  • Private dashboard for your team
  • You choose who can see each repo's results
  • Unlimited people on your team
Get started

Questions engineers ask

Which repos does it work with?

Repositories on GitHub. We are onboarding in small batches, so sign in, tell us which repo you want, and we will get it running.

Do I have to change my code or my CI?

No. Hitchless works from your repository and its issues. There is no SDK, no workflow file and no config to maintain.

What happens when it cannot reproduce a bug?

It tells you that, and what it tried. A result is only called reproduced when there is a failing test that fails for the reported reason. Anything less is labelled as likely or not reproduced.

Will it start posting on our issues right away?

No. Every repo starts in watch-only mode. You see the results on your dashboard first, and posting to issues stays off until you ask for it.

Is our private code safe?

Each reproduction runs in an isolated environment with no access to your secrets, and that environment is thrown away when the run ends. Results for a private repo are only visible to the people you choose.

How does pricing work for several repos?

Public repositories are free, with no limit on how many. Each private repository is $99 a month, with no per-seat charge.

Stop reproducing bugs by hand.

Connect a repo and let the next bug report arrive with its own failing test.

Get started with GitHub