pullboard

Your board catches its own repeats

Pullboard now turns a failure that keeps coming back into a rule with its proof. Rigor runs by itself: it names the files that keep colliding and proposes how to split them, and it carries your code and test quality rules as checks it runs on every change. Its new rules arrive as drafts, and only you approve them. Sentinels watch for something wrong right now: a board holds its own watches, which you approve and which report to their owner, and Rigor can draft one when a check could watch a repeat.

Added

• The view shows blueprint fit proposals with their reasons, and sentinel drafts for you to approve. (#762, #920)
• pullboard stats and pullboard digest say what the board caught: work a reviewer sent back and the gap it named, merges that went back instead of landing broken, flaky tests proven, and stuck states. It stays quiet unless someone asks. (#816)
• Pullboard tracks flaky tests, including CI runs: a test that goes red and green on the same tree is filed once with its runs, and can stop blocking landings until its fix is verified (pullboard flakes quarantine on, off by default). (#887, #918, #813)
• pullboard queue shows the work queue with release breakpoints, rank, route and who holds each item, and pullboard health names queue faults: a route nobody serves, an item nobody can take, a rank out of order. (#797, #798)
• A recurring job declares its cadence with pullboard loop declare, and a missed run shows in health. (#815)
• Optional two-tier landing: accepted work lands on your local trunk in seconds, and pullboard publish pushes only a head the whole suite passed (landing.publish set to separate; off by default, except that pullboard init turns it on in a repo with no remote). (#801, #963)
• A reopened item can wait for its own builder first, for a time you set (claim.reopenFirstRefusalMinutes; off by default). (#954)
• A spec row an agent marks approved by hand shows as agent-approved, with the agent and commit, until you confirm or decline it. A setting, spec.agentApproval, chooses flag (the default), allow or refuse. (#960)
• GET /api/v1/settings reports the board's settings, each with its scope, its value and where it comes from, read-only; secrets show only as set or not set. spec.agentApproval joins the list in the next release. (#968)
• pullboard publish records each full-suite run, so a flaky test it sees is filed like any other. (#975)

Safer by default

• A rule cannot lose its test silently: spec check fails when an approved row's gate file was deleted or renamed. (#809)
• The board runs a revert control before it accepts a fix, a gate that rejects everything is an alarm and not a pass, and a check whose pipe hides its exit status is refused. (#810, #811, #812)
• A verdict from the session that built the item is refused, and a change that edits an existing test or gate file says why. (#921, #814)
• Lane branches, merge commits, docs and view files never name your machine or quote you. (#892, #893, #894, #895)

Your board on your phone

• A board of any size opens on a phone from a small snapshot, then streams its full history while new moves arrive. The relay holds snapshots up to 64 MB, and an account nearing its storage quota is warned before any write is refused. (#903, #946, #949)
• A linked board opens in Safari and other WebKit browsers. (#976)
• A move still succeeds while the relay is down: it waits in an ordered outbox and is sent when the relay is back. A slow or lost relay reply never fails a local move. (#922, #919)
• The hosted page shows a screen right away on iPhone Safari, names the real reason a signed-in browser sees no board with the one step that fixes it, and never flashes another screen first. (#897, #899, #900, #901, #904, #932)
• In Safari, app.pullboard.dev now finds the board running on your computer. (#977)
• pullboard.dev now mentions a board that is waiting for approval on your phone. (#985)

pullboard.dev opens your board, and pairing just works

Open pullboard.dev on any device and it takes you to your board one clear step at a time. pullboard init offers to share the board with your phone in one Enter, and pullboard view keeps running in the background, so your phone always has a board to open.

Added

• Relay and pairing:
  • pullboard init offers to share your board with your phone in one Enter.
  • pullboard view keeps running in the background.
  • The view links this machine's boards to pullboard.dev in one sign-in, from a card you can close and bring back.
  • Approving a link on your phone delivers the board without another command.
  • pullboard relay devices lists phones and joined computers by name.
  • A lost phone can be revoked without that phone's approval.
  • A revoked browser is refused and told it was removed.
  • pullboard relay on --all says who signed in, what it linked and what it waits for.
  • The hosted page says how far behind this machine Pullboard is.
• Roadmap:
  • Each milestone sums its items by state, with an estimate at today's pace; on a slow day it estimates from the last 24 hours, or says it's too early to tell.
  • Finished milestones sit under Shipped, and the Roadmap opens on the current release.
  • A blocked item shows a dot and expands in place to say why.
  • pullboard roadmap lists the work to ship first.
• Rigor:
  • pullboard rigor notices a failure cause that repeats.
  • pullboard rigor draft turns a repeated cause into a draft row with its proof, waiting in Needs you.
• pullboard health names every stuck item, why it's stuck, and who moves it next.
• pullboard digest writes a readable briefing of one board.
• pullboard gate set "<command>" sets the project gate in one step. A board without a gate is told that command with the test command Pullboard found (such as make test), never a hand edit of pullboard.json.
• pullboard watch follows the board's live event stream.
• pullboard next:
  • follows the coordinator's ranking inside a release;
  • names the item and the seat to work in across an agent's lanes;
  • in the main checkout, points a newcomer to their lane.
• A newcomer working alone can start their reviewer with one command.
• An agent in a lane worktree can draft a spec row and cite it at once without editing a file outside its lane; every writer takes its row id from one allocator on the board, so two drafts never share an id.
• An item that fails twice at one route moves up a route by itself; at the strongest route it stays with its builder.
• An accepted item that conflicts with the trunk reopens for a main merge with pullboard reopen <id> --conflict <file>, and its accept stays recorded.
• A person's waiver also covers the submit and landing gates.
• A ruling the person approves becomes doctrine every agent reads, and a decision names the items it changes.
• A test that escapes to landing is proposed as a submit invariant.
• pullboard init:
  • takes a product and an architecture blueprint together;
  • grants the agent the permissions the Pullboard loop needs;
  • commits its own setup files, or offers to in one Enter.
• Blueprints:
  • A blueprint fits the repo before you approve it.
  • Its questions default from the repo they land in.
  • Each rule names its source.
  • Its starter items land in a build lane.

Changed

• pullboard submit runs the static style checks first, in seconds.
• pullboard init says the one line that matters first, and folds the rest.
• A board building without spec rows is no longer told to draft the spec first.
• Only test files that start a browser wait for a browser slot, and a short check never waits behind whole suites.
• The gate pool serves the current release first.
• A check that's already green on main holds the item until the person accepts it.
• Agents ask the person only through the coordinator.

Fixed

• An agent can't mint relay tokens from its worktree.

Open your board from pullboard.dev

pullboard.dev now lists the boards on this machine beside your linked boards, so one page opens all of them. Link every board once with pullboard relay on --all, pair your phone from the QR it prints, and open pullboard.dev on any device.

Added

• pullboard.dev lists the boards on this machine together with the boards you linked, and opens either kind.
• The phone page can be installed to your Home Screen, and it asks the browser to keep its storage, so a paired phone stays paired.
• pullboard lane add <lane> --owns <path> makes a lane, and pullboard init proposes lanes for the folders it finds.
• A Doctrine rule can carry a check and a count: that only falls: pullboard submit refuses a change that makes a touched rule's count rise.
• With landingShards in pullboard.json, the landing gate splits its tests into shards that run in parallel, locally or on registered runners.
• Machine settings, all off unless you set them:
  • gate.queue.reviewsFirst: the gate pool admits reviews before submits, with gate.queue.agingMinutes bounding every wait.
  • gate.memoryFloorMB: the gate pool holds new work while free memory is under the floor, and names the biggest processes.
• Every bundled blueprint's starter items carry a criterion and a check, so the first item can be built and verified.
• pullboard spec answer <id> "<choice or text>" records your answer to a pending blueprint question, from your terminal or the view. An agent is refused.
• pullboard init puts new agent worktrees inside the repository, in .claude/worktrees. Boards without the setting keep them beside it; set "worktrees": "beside" in pullboard.json to choose.

Fixed

• pullboard accept says how to land the item, and pullboard land --dry-run catches a missing origin.
• A gate blocked by an agent's sandbox stops with SANDBOX_BLOCKED, asks the person, and names any test file the agent edited.
• A waiver given after a gate stopped early runs the gate again.
• The view loads an item's full detail only when you open it.
• The page's Needs-you list comes from one place, so the panel, the list and the counts agree.
• pullboard resume on a board it cannot write refuses by name, with the step to fix it.
• pullboard resume names pullboard lane add instead of a script.
• A person move is refused from a remote SSH shell whichever SSH variable the shell carries.
• pullboard blueprint save reads back a question with three or more choices.

Blueprints, MCP, and refusals that tell you what to do next

0.8.28 never reached npm: one runner test hung on Linux CI, and that's fixed here. Everything listed under 0.8.28 in the changelog ships in this release too.

Added

• Blueprints.
  • pullboard blueprint add <name> files a blueprint's rules as draft spec rows for your approval, with its starter items.
  • pullboard init --blueprint <name> starts a new board from one.
  • pullboard blueprint save turns your board's approved rules into a blueprint you can reuse.
  • The ten blueprints from the gallery are bundled.
• pullboard mcp: an MCP server over stdio. An agent's own client can read the board and coordinate on it: board status, show an item, shout, capture an idea. It uses the same moves and refusals as the CLI, and it can never act as the person.
• pullboard runner add <host> --slots <n> --browser <n>: a test run waiting in the gate pool can run on another machine over SSH. A runner uses its own machine's browser slots. Nothing changes unless you add a runner.
• submitInvariants in pullboard.json: with "submitGate": "landing", pullboard submit still runs these test files on every submit.
• The Roadmap shows the work to ship first, with shipped work below it.

Fixed

• Every refusal ends with a next step that works.
• pullboard init says when the gate command it found can't run on this machine. In an existing repo, the first gate after init says to commit the files init wrote. pullboard init --help lists --blueprint.
• pullboard worktree <lane> from the main checkout creates and joins the worktree for the session that owns the checkout. Another session is still refused. Without a model, it names the --model flag to add.
• pullboard add refuses a build item in a lane that owns no files and names the lanes that do. A review item that names the work it reviews (--after <id>) is still accepted.
• When ~/.pullboard can't be written, for example inside an agent's sandbox, commands refuse with MACHINE_HOME_NOT_WRITABLE, name the folder and say how to fix it.
• A declined spec row keeps its text, and the view shows the reason it was declined.
• A relay connection failure names its cause.
• The API refuses blank shout text the same way the CLI does.
• The README's worktree command includes --model.

Corrected 16 Oct: an earlier version of these notes listed gate.memoryFloorMB, which is not in 0.8.29 and ships in a later release, and an internal test-suite change.