Skip to content

v2.6.0

Choose a tag to compare

@github-actions github-actions released this 12 Nov 02:56
44891ea

Minor Changes

  • 9bdb63d: /build <N> in the desktop app now asks one question first: run the build here, or in a sub-session. It recommends the sub-session when your session has already started other sessions or sits outside N's checkout. A sub-session starts in the checkout of N's repository (found one folder down when you are above it, or asked when there are none or several) and runs building there, and an answer you give in your own session to its question is passed on to it in your words. In a terminal nothing changes: /build builds here without asking. The choice lives in a new shared skill, delegating.
  • 9bdb63d: A session can now start a build with the new building skill: tell it "use building for #N" and it builds N exactly as /build N does, so an agent such as a Chief of Staff session can start a build without anyone typing /build. The build's steps, references and credits move from build to building; /build still works as before and now hands the issue to building.
  • 9bdb63d: Every worker is now a subagent. The desktop and bg Drivers are gone, and so is --driver: spp dispatch <issue> takes no flags and writes the brief without starting claude --bg, spp plan no longer records or renders a Driver, and spp next no longer puts a driver on its dispatch actions. Passing --driver to either command is a usage error. building no longer asks which Driver to use at the first Wave; its approval question now comes first in its message, so a parent session sees it. An Epic whose plan comment still records a Driver builds as before, with subagent workers.
  • 9bdb63d: A build resumed after its session died now asks about the work its lost workers left behind. spp next <epic> --resume returns each Sub-issue that is claimed, with no open or merged pull request and no assignee, as a hand-back saying worker lost, and building passes --resume on the first spp next of each run, so you choose whether to hand the issue back or start a worker on it again. spp next, spp wait, spp wave plan and the Epic board no longer read the claude agents session list: spp wait no longer prints t-<N> done lines, and the board lists only its own session's subagent workers, so its attach button is gone.

Patch Changes

  • 9bdb63d: spp next and spp wave plan take --running <tickets>: the tickets the build started a worker on, until that worker reports back, count as in flight, so neither command dispatches them again, and a ready ticket that overlaps one is held. Without the flag nothing is held that way. building keeps that list and passes it on every spp next, and starts each worker's Agent description with t-<N>, so the Epic board links the worker to its row. The board's worker entries drop their kind field, and a failing agent list read shows as agent list: <message>.
  • 9bdb63d: spp next and spp wave plan share one parser and one error message for the flag. building passes each running ticket in the form the dispatch action named it, and resumes a worker by the agent id its Agent call returned.
  • 9bdb63d: A resumed build no longer starts a fresh worker on a branch another worker left. When a fix round, a rebase or a settled design needs a worker that died with an earlier session, building asks you whether to hand the issue back or take the pull request over. spp brief's first step again only cuts sdd/<N>-<slug> from the base and confirms it, and a restarted lost worker starts on that fresh branch, so a branch the lost worker pushed is yours to delete or the issue goes back. spp next --running now holds a running ticket in any state, landed included: neither it nor its fix pull requests are routed again while its worker works, and main-gate waits for it. spp wave plan --running holds each one until it lands, with the reason running, its worker has not reported back. building keeps each worker's agent id for the rest of the session and puts an issue back on the running list when it resumes its worker.
  • 9bdb63d: building: each answer to the dead-worker question now leaves a mark spp next reads, so the same fix or merge stops coming back. Taking a pull request over puts its issue on the running list until you say you are done; handing back a fix pull request closes it with its open findings, so the main gate can run. spp brief's first step now stops BLOCKED when origin already has the ticket's branch or cannot be reached, and the brief tells the worker never to force-push.
  • 9bdb63d: Every question building stops on now opens with one line, #<N> waits on you: <question>: the first Wave's approval, a lost worker, a red Verify after a merge, a design to settle and an issue it cannot build. delegating relays your answer from a parent session to any of them, not only the Wave approval. /build on a Sub-issue or a raw issue now stops with the reason before it asks where to run, and starts no sub-session. Restarting a lost worker removes its local worktree and branch once you agree.