aider in your terminal. The ledger keeps score.
aider already lives in the loop Haybox measures: diffs, tests, commits. Point its endpoint at the daemon and every session gets a Waybill.
Three steps
Point aider at the Haybox daemon and keep working. The exact configuration line for your version is in the docs.
- Install Haybox
One binary, Windows, macOS or Linux. It starts a local daemon and detects your hardware.
- Point aider at the local endpoint
Point aider’s endpoint at the local Haybox address.
- Work normally
Nothing about your workflow changes. Watch the Ledger fill: a Waybill per task, and a savings report after thirty days.
Haybox is in private alpha, so step one is the waitlist for now.
What you get with aider
- A shadow report built from your real traffic, not a simulation of someone else’s.
- Local-first routing with acceptance floors under it, so cheap only counts when it holds.
- A Waybill per task: the route, the cost per leg, what verified, and your decision.
- Rules that apply here too — the files you already keep are read natively.
The route, end to end. Illustrative.
Notes for aider specifically
aider users already live in the loop Haybox measures: diffs, tests, commits. Point aider’s endpoint at the daemon and every session gets a Waybill; git-based revert tracking fits aider’s commit-per-change style particularly well.
Questions
Does Haybox interfere with aider’s git commits?
No — it observes; sandboxing applies to the native agent.
Are there benchmarks for aider workloads?
The public methodology covers terminal-agent tasks; see the Benchmarks page.
See what your own traffic says.
Shadow Mode reports on the traffic you already have. Before that exists for you, the calculator will estimate it from your GPU and your monthly spend, and show you every assumption it used to get there.