Repository navigation
v0.16.1
One fix, found by measuring the loops rather than reading them, plus the cost
table that measurement produced.
Upgrade
- A scheduled run will now take as long as you told it to. Until this
release both drivers were cut off after ten minutes by a CLI ceiling neither
of them set (see Fixed below), so a nightly job has been finishing far inside
its budget and reporting success. It will now run up toLOOP_ENG_MAX_MINUTES
— 120 minutes for polish, 240 for autoloop — and consume tokens for that
whole time. Nothing to do if those defaults are what you want; lower them, or
exportCLAUDE_CODE_PRINT_BG_WAIT_CEILING_MSyourself to keep the old
behaviour, if they are not. The measured shape of a run is now in the
README's "What a run costs".
Fixed
- An unattended run was bounded by a ceiling neither driver set, twelve to
twenty-four times shorter than the one it did. In print mode the CLI waits
for still-running background tasks, then terminates them and exits 0 —
afterCLAUDE_CODE_PRINT_BG_WAIT_CEILING_MS, whose default is 600000 (10
minutes). Both loops dispatch subagents the harness may run in the
background, so that default, notLOOP_ENG_MAX_MINUTES(120 for polish, 240
for autoloop), was the real bound on every scheduled run. Nothing downstream
could notice: the truncated session exits 0 withis_error: false, a
report-only polish is exempt from the post-run check, and the autoloop driver
reads that exit as a finished round. Found by measurement rather than by
reading — a headless/polish hooks/reportedsubagent_stats
killed.system: 1with 4 of 5 dispatches completed, and still exited 0; the
same scope with the ceiling lifted completed 18 dispatches (4 reviewers,
12 verifiers, 2 workers) in 25 minutes. Both drivers now hand the session
CLAUDE_CODE_PRINT_BG_WAIT_CEILING_MS=0, leaving thetimeoutwrapper as
the single budget it was written to be; exporting the variable yourself still
wins. The suites gained the piece that made this invisible — the stub
recorded argv but not the environment, so a bound the driver never set was
one no assertion could see.
Changed
- The README says what a run costs, from two measured runs rather than an
estimate. A plugin whose pitch is "leave it running" owed a number and had
none. An/autoloopround fixing a failing assertion: 3 dispatches, 25,293
output tokens, 5.7 minutes. A/polishmacro round over four files: 18
dispatches, 354,188 output tokens, 24.9 minutes. The four token classes are
listed apart on purpose — cache reads are 89% of the polish traffic and the
cheapest class, so one summed figure would overstate the load about 9× — and
the dollar column is labelled as the list-price computation it is, which is
not what a subscription pays. The note that makes the table reproducible is
the one that cost the most to learn: readmodelUsage, not the top-level
usageblock, which covers the main thread's last turn and counts no
subagent at all. - The unattended section says how far to trust itself. Closing the audit's
six--allow-writeblockers moved that path from "not production-grade" to
usable, and every guard is now documented mechanism by mechanism — but the
README stated no posture at all, so the only readiness verdict a reader could
find was the one in the audit report, which is untracked and was written
against 0.14.0. The new paragraph says what backs the write path (a test
suite and a live-install smoke) and what does not (a record of long
unattended write runs), and keeps report-only as the mode to schedule first.
Deliberately no assertion count: the README cites none anywhere, and a
hard-coded one goes stale the next time a suite grows.
Live-install smoke: PASS (Claude Code 2.1.278, headless, throwaway
CLAUDE_CONFIG_DIR, GitHub-source install of this release's own content on
main — no source-type disclosure owed). Live cache copies instrumented, so
each verdict is a marker on disk: the evidence-gate's deny() fired with
CLAUDE_PLUGIN_ROOT resolved to the real
plugins/cache/loop-eng/loop-eng/0.16.1 path and the file never landed;
armed from …/0.16.1/…; exactly three SGBLOCK markers then
CEILING-RELEASE on a red contract, with the ledger machine-written
"all_green": false; and /loop-eng:autoloop reached ALL GREEN, left a
two-criteria ledger, and cleared active, gate-count and criteria.sha256
with zero blocks.