What it does

retryfuse is a free, deterministic command-line tool. Given a failed or timed-out call, it decides one of five outcomes and explains why: replay_safe, replay_stored, brake, reconcile_required, or reject_conflict. Evidence is reported as pass, fail, or unknown, and unknown is kept distinct from both.

The acceptance gate

A post-write timeout returns reconcile_required, never a blind retry or duplicate effect. The decision core is pure and versioned (contract version 1), so the same input always yields the same evidence report.

Install and run locally

Requires Node.js 20 or newer. The core and CLI run entirely on your machine.

git clone https://github.com/gitdhillonai/retryfuse.dev
cd retryfuse.dev
node src/cli.mjs INPUT.json            # machine-readable evidence report
node src/cli.mjs INPUT.json --human    # human-readable evidence report

Read the contract reference for the full JSON input, the five decisions and the CLI exit codes; why reconcile beats a blind retry for the failure mode this tool exists to stop; idempotency keys and exactly-once replay for how a key and request fingerprint make a retry safe; braking a retry storm for when repeated failures or budget burn open the circuit; pre-write vs post-write timeouts for why phase decides replay_safe versus reconcile_required; CLI exit codes in CI to gate a pipeline on the evidence report; or see the fixture matrix for the input contract by example, covering positive, negative, malformed, missing-data and adversarial cases.

Status and honesty

Demand for this tool is a hypothesis, not validated paid demand. The local CLI and fixtures are free. A hosted history and team CI policy are a proposed future offer, intentionally not exposed until authentication, tenant isolation, retention and deletion tests pass — see pricing. There are no usage metrics or verification claims on this page by design.