Run your coding agent unattended, and trust the result.

DeadReckon is a harness around the agent CLI you already use.
A separate watchdog process, not the agent, decides when the work is actually done.
You get a signed, auditable artifact instead of a chat transcript you have to take on faith.

---

Get started

Install the latest release (macOS / Linux):

curl -fsSL https://deadreckon.sh/install.sh | sh

This resolves the newest release (stable preferred, release candidates included), verifies it against SHA256SUMS, and installs deadreckon. Pin any release tag with DEADRECKON_TAG=<tag>.

Or build from source:

cargo build --release          # binary at ./target/release/deadreckon

Then the whole tool is five commands:

Command	What it does
deadreckon start "build the app"	Kick off a supervised run. Walk away.
deadreckon attach latest	Watch it work live. Ctrl-D leaves it running.
deadreckon status	What happened, and the one thing to do next.
deadreckon list	Find recent runs and plans.
deadreckon finish latest	Apply it to your branch, or export it.

For a higher-level read while it runs, deadreckon attach latest --view narrative shows cited prose plus an evidence-backed visual map.

                   

_{Supervises the agent CLI you already use: Claude Code · Codex · Gemini · Copilot · OpenCode · Pi · or any Anthropic / OpenAI-compatible API.}

Everything else (budgets, undo, multi-step chains, provider routing) is optional power you reach for later. No API keys? deadreckon run "hello" --smoke --sandbox none exercises the whole harness against a faked provider.

Tip

DeadReckon is on the production-release track. The core lifecycle (isolated runs, signed gates, durable state, undo, docs, orchestration, and apply) is implemented and tested; release notes call out any compatibility migrations.

Why it's different

• It can't fake the finish. A separate watchdog (dr-gate) holds a secret the agent process can't read and signs the result with it. No valid signature, no "done." The agent literally cannot mark its own work accepted.
• Walk away for real. Every turn is saved to disk. Close your laptop, lose the network, kill the model, then attach from another terminal and resume from the last completed turn.
• Evidence, not a transcript. Each accepted run promotes to a reviewable artifact: what changed, why, which prompt touched which file, what it spent.

→ The full story (the loop, the mental model, and how it compares) is in Concepts & How It Works.

Documentation

Doc	What's inside
Concepts & How It Works	The loop, the watchdog, the mental model, supported agents, how it compares
HOWTO	Practical usage: setup, providers, sandboxes, configuration, every command
DESIGN	Product and architecture intent
As-Built Architecture	Detailed implementation reference
Resume Semantics · Multi-Run	Crash/resume behavior and concurrency rules
V1 Candidates	Deferred features and roadmap

DeadReckon is maintained as production-release software. The core lifecycle is implemented and tested, alongside multi-agent orchestration (plan / fork / merge), autonomous chains, the provider flight recorder with rewind, and a local self-improvement loop (learn / improve).