NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules
Go modules, #2996 by repository stars
Latest stable
v0.2.1
Last release 1 months ago
13 Oct 2026
Too new to tell
only 2 release windows
Nearly every release is documented
notes for 3 of 3 stable releases
Nothing withdrawn
no release was ever pulled
3 months old
3 releases · first in 2026
Drag across the ruler to compare, or tap a release to open it.
Fixes a price measurement bug and adds a new feature for max findings.
Fixes a price measurement bug and adds a new feature for max findings.
Mole was recording two of the four parts of itself that spend money at $0.00. A run that reported six cents really cost eight, and a --usd ceiling could not bind on the phase that makes most of the calls. If you enforce a dollar budget, re-check it against a single run before turning anything loose.
Fixes — every call is priced, whichever part of mole made it. Pricing was done by whoever happened to build the call… 143 of 185 calls and 127,054 tokens, all free. The rate table is consulted in the ledger now… Declared rates reach every role now too.
New — --max-findings sets how many findings the report is written from, which is what sets its length.
curl -fsSL https://raw.githubusercontent.com/lajosdeme/mole/main/install.sh | sh
Or see the README for Homebrew, AUR, .deb and building from source.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
One column per month.
Four defects in how mole measured itself are fixed in this release. Each one caused it to stop short, or to under-count what it spent. Together they m
Four defects in how mole measured itself are fixed in this release. Each one caused it to stop short, or to under-count what it spent. Together they mean a session now does work it previously skipped — which is the point, and is also a real change to your bill.
On the test corpus, the same Deep question before and after:
before after
claims 317 661
contradictions 32 126
sources read 28 53
spend $0.078 $0.173
ended planner done, max_wallclock,
13 of 25 min using its full clock
If you run mole on a budget, re-check your --usd figures against a single run
before turning anything loose.
A run no longer ends holding work it chose to do. A verification pass proposes a follow-up for every contradiction worth settling and queues only what its budget takes. The rest were discarded — no later pass could find them, because verification judges only unverified claims. One measured run found 32 contradictions, followed up 4, dropped 28, and reported itself finished. They are now deferred and drained before the session can end.
An unpriced model is no longer a free one. A provider renaming what it
reports — deepseek-chat answering as deepseek-flash — made every call ledger
at $0.00, so --usd accumulated nothing and could never bind. The configured
model's rate now prices an unrecognised response. Related: mole ships rates for
every model it can select itself, and you can declare your own (see below).
Tokens a provider billed and did not explain are now charged. Gemini's
OpenAI-compatible endpoint reports internal thinking in total_tokens and in
neither part, so a call billed at 139 tokens was ledgered at 26 — a fivefold
undercount. Reported and diagnosed by @gavmor in #1.
The tool-call ceiling was cutting runs roughly in half. It assumed a lead
costs four calls per source; measured, the figure is a median of 43 and a
maximum of 62. It is now an explicit backstop, settable with
--max-tool-calls.
A limit of zero means every row. Six store queries read 0 as "use a
default" — 500 claims, 200 leads — so a call meaning "give me everything"
returned the first 500. Exports of large sessions were silently truncated, and
the verifier's pairing pool excluded the newest claims from ever being compared.
Declared model rates. A pricing block in the config takes dollars per
million tokens, overriding built-ins, so any provider — OpenRouter included — is
budgetable. mole doctor reports whether every configured model has a rate.
A session clock you can set once. max_wallclock in config, and a clamped
timeout on research.report over MCP. Requested in #2.
stopped_because on the session and in the export. budget_exhausted was
reported for five different endings, only one of them about money. The reason is
now recorded beside the status.
Follow-up lineage in the export. A sub-question spawned to settle a
contradiction carries verify_depth and root_claim_id.
Builds on Windows, via #6 from @ucsandman.
curl -fsSL https://raw.githubusercontent.com/lajosdeme/mole/main/install.sh | sh
Or see the README for Homebrew, AUR, .deb and building from source.
c696058b650c7a06084767d966c7d2f5005d316a Clean up CLA by removing review markers and notes
mole datasetcurl -fsSL https://raw.githubusercontent.com/lajosdeme/mole/main/install.sh | sh
Or see the README for Homebrew, AUR, .deb and building from source.