Continue, continued. Now with receipts.
Continue’s provider configuration takes a custom endpoint per model role. Route them all through Haybox and they land in one ledger.
Three steps
Point Continue 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 Continue at the local endpoint
Set the Haybox endpoint in Continue’s provider configuration, for each model role you use.
- 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 Continue
- 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 Continue specifically
Continue’s provider configuration takes a custom endpoint per model role. Route through Haybox and its chat, edit, and autocomplete traffic all land in one ledger, one savings report, one set of rules.
Questions
Autocomplete too?
Yes, classified and accounted like everything else.
Which config file?
The docs quickstart shows the exact block for current Continue versions.
aider · Ollama · Ledger · All integrations
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.