Skip to content

v0.16.0

Choose a tag to compare

@JamesMoriartyDecripto JamesMoriartyDecripto released this 01 Nov 22:37
· 204 commits to main since this release
ebc9b06

Added

  • Unattended Dev Squad runner (#320): node tools/squad/runner.mjs works issues labelled squad:go on one OpenRouter key, with no session and no SDK, one at a time. The procedure is in code (triage, worktree, plan, steps, review and security, lead-judge, fix rounds, verifier, draft PR, gate); the models only judge. It stops at a draft PR or with squad:failed and the reason. Limits (usdPerIssue, minutes, fixRounds, pollMinutes) are in squad.json, and a lock allows one runner. New role lead-judge (default Claude Sonnet 5.5) and architect default GPT-6.1 Terra, both from the #362 benchmark. New runner files: runner.mjs, runner-core.mjs, runner-deps.mjs, runner-gh.mjs, runner-plan.mjs, runner-judge.mjs.
  • Dev Squad tower, unattended runner (#320): a ninth layer shows how runner.mjs works labelled issues with no session: poll squad:go, claim, a code-driven lead, the new lead-judge role, limits, a draft-PR stop point and squad:failed. Model choices come from the #362 benchmark: lead-judge Claude Sonnet 5.5, unattended architect GPT-6.1 Terra. Role card roles/lead-judge.md.

Known limits

  • Unattended runner (#320): five external acceptance replays each stopped safely, with the work committed and the reason on the issue; none has yet reached the draft PR on its own. The last stop: a fix that needed a test file outside the fix scope. Project checks run in the runner's process, next to its OpenRouter key and GitHub token (#375): run it only on trusted repositories.

Removed

  • Dev Squad Claude Agent SDK backend (#355): examples/dev-squad/src (the webhook pipeline on @anthropic-ai/claude-agent-sdk), its deploy files, Claude Code settings, prompts, memory and sample logs, and their tests. The squad depends on no SDK: one OpenRouter key, the user's own session as lead in any harness.

Fixed

  • Unattended Squad role prompts explicitly require the machine-readable result in the finish report; the judge and verifier receive the original issue alongside the plan, preserving requirements omitted by a summary. A kept finding can name up to 5 supporting files its fix must edit; every path on a fix step's Files: line must be a concrete regular file outside secret paths, and plans or fixes whose files reach .github/, tools/squad/ or package.json (also through a directory, glob or + entry) need a person; mentioning those files in the issue text does not stop it (#320). The architect's plan steps hold only code changes and list only the files each must edit; checks, review, verifier and the draft PR stay with the runner (#320). A fix round's Files: entries are optional: they bound where the coder may write, so a finding fixed in another file than the one it quotes no longer stops the issue; (optional) entries now count for a step's write scope and commit, as their meaning implies. Findings still kept after the last fix round are listed in the draft PR instead of stopping the issue; a security finding stops it unless its severity is clearly medium or low (#320).
  • Temp files no longer fill the disk (#357). Each test run uses its own TMPDIR, removed at the end; folders left by crashed runs are swept after 24 h. On 2026-10-31, 2205 leftover folders had filled a /tmp quota. steps.sh deletes its output folder when every step is green, and its own folders older than 7 days. run.mjs prunes role logs beyond the newest 200 that are older than 14 days (new runner file log-prune.mjs).

Changed

  • Dev Squad favours the simplest change (#367): every role prompt asks for the minimum that meets the task, with no abstraction, option or check it does not ask for; the reviewer also flags unneeded complexity and duplicated mechanisms; security names the existing guard before proposing a new check.
  • Focus mode draws no cross-layer link (#360): with a layer focused in the tower view, the selected node's links to other layers are hidden too, since they ran up to layers the camera hides. The node panel lists them under "Across layers".
  • Dev Squad tower (#355): examples/dev-squad now models the OpenRouter runner in tools/squad: lead in your harness, triage, plan and task files, coder steps, packed review and security, merge gate, setup, cost ledger and models. The role node ids are unchanged. New role cards (roles/*.md), a sample squad.example.json, the task template and a nested runner-loop tower replace the coder and researcher towers. squad init installs this smaller bundle.
  • Squad steps.sh (#353): each step commits only its own files: the write dirs, the folders of its Files: entries and the paths those entries match. It no longer stages every tracked change, and local edits from before the run are never staged; a step that modifies one of them is RED. Steps already committed are skipped on a rerun. The coder may write the folders its Files: line names. The script runs from a temporary copy, so a step can edit steps.sh. New runner file step-scope.mjs.
  • Focus mode hides cross-layer links (#348): with a layer focused in the tower view, links that do not touch it are no longer drawn, and links that leave it show only for the selected or hovered node and its related nodes, at full strength. They used to stay at 10% and cross the camera's view of the focused layer. Overview and map view are unchanged.
  • Dev Squad SDK reference (#347): the deprecated quick-fix route is gone. Triage routes to full, needs_info or reject; a trivial issue gets a one-step plan from the lead and the same review, verification and approval gates. The tower no longer shows the quickfix node. The sensitive-area rule that forces a human plan sign-off now also reads the issue body, not only the title and the model-chosen areas.