Repository navigation
1.8.0 and 1.8.1 were never published: their work is here, with what followed them.
-
no-find(base, on in every project,updateincluded):find,bfs,fd,locateandmdfindare refused as commands, anywhere in a line, past wrappers andxargs, unless the user's prompt that turn asks for one by name ("use find to …"; a question about one asks nothing). The refusal says where to look: the order's sources with their paths, the layout's folders, Glob and Grep on a named folder. A BANDWARP agent'sfind / -name QwertyPlayer.hsearched a Mac's whole disk for a minute and a half for a file the order lists in~/projects/synthcore(KWB-154). Its selftest, 18 cases, each law seen red. -
The status line and
statusshow an agent from its first minute: a worktree on the order's own branch (work/<order>-<name>) is that order's agent, "not started yet" while its branch has nothing of its own and nothing runs in it; a merged one untouched for two hours is left out unless work runs in it. Where no heartbeat hook runs yet, an agent's last call comes from Claude Code's own transcripts. The lead's own work (its builds, its gates) shows on its order's row beside its agents. -
Logged for the next release: KWB-151 (the same warning flags are not the same law on every compiler), KWB-152 (the kit is not proved the same on Linux, macOS and Windows), KWB-153 (a test the kit runs has no memory or time limit), KWB-155 (a file in one worktree read as a copy of itself in another).
-
The runs as a tree, in
statusand the status line: a project, its orders under it when it has more than one, each order's agents under the order (├,└,│); a lead working alone is said on its order's row ("lead on W9 …"), never as a row of its own; a run in a worktree is named by its project (VSYNTHGT (ui-look)), never the worktree's folder. Once other machines are listed every run says where it runs, this machine's too (PC:,MAC:; remotes.json's"name", elsemacon macOS andpcelsewhere). The process check measures the lead's checkout as well, so a lead's build shows its processes, cores and memory.test/run-remotes.test.mjs. -
KWB-149: a build yields with
niceon every system; on macOS it ran undertaskpolicy -b, background work, which macOS keeps on the efficiency cores: a Mac's build used about 2.5 cores of 18. KWB-150: a job takes the core budget divided by the jobs running as it starts, its own counted, never less than its slot's share: a build alone on a quiet machine had compiled at-j 3.test/core-budget.test.mjs. -
KWB-148:
toJsonwrites an object that appears twice side by side in full both times; only an object inside itself is a circle.test/json-helper.test.mjs. -
The runs of other machines:
~/.config/claude-packs/remotes.jsonlists them (name,sshas~/.ssh/confignames the host, anddir, a project there whose kit answers).statusand the status line ask each for itsstatus --jsonover ssh, with no password prompt, a 5-second connect limit and 20 seconds in all, from the background refresh, so nothing waits on a machine that is asleep; its runs show asMAC: SHOPwith their agents, measured on that machine. A machine that cannot be reached, or whose kit has nostatus, is a red row that says so.status --dirasks no machine.test/run-remotes.test.mjs. -
The kit's status line (
base): every project shows what is working and where it is. The top line starts with the kit version that project runs (from its lock), then the model and effort, the context used, and the 5h and 7d quotas on a subscription or the session's cost on API billing; the model shows red when a fallback swapped it from the one pinned in the user's settings. The second line has the branch, its uncommitted files, ahead and behind, the last tool with its target and the last shell command, read from the session's own transcript. Below them, every unattended run on the machine:PROJECT [bar] NN% > agent > step [bar] NN%, an agent quiet for 30 minutes in red. The runs are found in the background at most every 30 seconds and drawn from a cache, so a render never waits (about 70 ms); any feed that is missing or broken draws nothing.initandupdatewire it in.claude/settings.jsonwithrefreshInterval: 1where the project has no status line of its own; a project's own is kept and the install says so;layout.json"disable": ["tools/statusline.mjs"]takes the kit's out.test/statusline.test.mjs. -
Every agent's sign of life, kept by the hooks, never by the agent:
heartbeat(base, async on every tool call before and after, on by default withupdatetoo, since it refuses nothing) writes what each agent did last into the main checkout's.claude/logs/heartbeats/<worktree>.json. Each refresh also checks what really runs in each agent's worktree (processes, cores and memory from/proc, or onelsofcall on macOS) and whether its build waits for a slot of the build queue (the slot layout is one file now,hooks/lib/build-slots.mjs, read bybuildqand the check). An agent's row:♥ 12s ⚙ 13 proc · 1.3 cpu · 322M ram READ <target>,⟳while a call runs, columns aligned and as wide as their widest value; red when it is stuck by the evidence, no call for 5 minutes or a running call with nothing working in its worktree. A project's percent counts each agent's own progress, so it moves while the lead waits on its agents.heartbeat --selftest, its worktree case,test/run-status.test.mjs. -
One JSON helper (KWB-146):
packs/base/hooks/lib/json.mjs,toJson,parseJson,readJsonandwriteJson, none of which throws: a circular reference, a BigInt, an Error and atoJSONthat throws are each written, bad or missing text gives the fallback, and a file is written whole through a part file. Everything new in this release calls it, andlib/global.mjs's strict reader is built on it.test/json-ratchet.test.mjscounts the rawJSON.parseandJSON.stringifycalls left in the kit (560) and is red if the count rises, until the migration takes it to zero.test/json-helper.test.mjs. -
The run readers (
run-status.mjs,run-discovery.mjs) live in the hooks lib, where the installed status line reaches them;lib/run-status.mjsre-exports them.status --json [--out <file>]prints the report as data. -
claude-packs status: where every unattended run stands. It finds the runs alive on the machine from theirrun.shprocesses (or one project's orders with--dir), and prints one line per project,NAME [bar] NN% X of Y items left, N agents, then one per agent,> name > step [bar] NN% what it is doing, or the lead's current step when no agent runs.--watch <minutes>prints it again on every tick. The unit is the item, a step's numbered items plus one for its Done when; the run's ownstatus.jsonand each agent'sagents/<name>.jsonin its worktree win, and an order without them is counted from itsprogress.mdlines, a step marked done counted whole. A status file that is not JSON is ignored, never a crash. The work-orderPROMPT.mdnow tells every run to keep both files.test/run-status.test.mjs.