B.O.S.S.

What's new.

Releases that change something you'd actually do, see or rely on — or that add a practice your project now inherits. Refactors, audits and internal work get no entry, so this list is short on purpose.

Generated from the same file boss sync reads when it tells your project what changed since its pin. In a project, boss status shows your pin against what's installed, and /boss-sync brings you forward as a reviewed diff — never a silent update. The full engineering changelog

▸releases
  1. v0.327.02026-09-23

    Run boss sync — BOSS's hooks had been failing silently in any project whose package.json says "type": "commonjs", and sync brings the fix. /measure is now /health's first run; /ai-first-init is gone, and /spec asks per feature which steps need the model. /ship checks the live thing answers and asks who hears if it breaks at 3am; your agents now say what they didn't check. After an MVP unlock, delete "This project is in Quickstart mode" from your CLAUDE.md.

  2. v0.326.02026-09-14

    the ten opt-in hooks no longer land in your .claude/hooks/ at scaffold, switched off, with a JSON block to copy by hand. boss hooks lists them; boss hooks enable <name> copies the file and registers it in one move; boss hooks disable <name> reverses both. A project that already has the files keeps them, and boss sync keeps enabled ones current.

    the conscience says a thing once per session now. A moment whose predicate still holds used to re-fire on every prompt; every frame promised "at most once this session" and nothing kept it. It is kept in code — a small ledger in your person-state (off the repo), keyed by the host's session id. A new session hears it again; a host that sends no session id gets the old behaviour.

  3. v0.325.02026-09-12

    if you installed BOSS as a plugin, /boss:welcome inside a BOSS project now does what the project's own /boss does: say what you're trying to do (or nothing) and it reads where you are and names the smallest next step. In a folder without BOSS it is unchanged.

  4. v0.324.02026-09-12

    boss unlock mvp lays down 16 skills, not 28 — the seven for after launch arrive when your first FEAT ships and the five for an AI product when your app first calls a model; boss status says when, boss sync lays them down. /boss now works on any day, not only day 0: say what you are trying to do (or nothing) and it reads where you are and names the smallest next step, naming the verb after the act. /evidence is the one capture verb — a thing that happened, your notes, or a whole transcript — and /research retires into it; /interview is the prep, only. boss status runs in a sixth of the time. Your docs/loops/ moves to .boss/loops/ on the next sync (docs/ is yours again; the old copies are reported, never deleted without --remove). Nothing you wrote moves.

  5. v0.323.02026-09-12

    four examples in /cost-review, its review template, the cost-budget loop and /practice said a vendor's model names where they meant the cheap tier and the capable tier. They say the tier now. Nothing else in your project changes.

  6. v0.322.02026-09-12

    if you are at MVP or above, /extract is the verb, unchanged in shape — same three signals, same EXTR-NNN record — and it now says plainly when UP is not possible from your machine instead of pointing you at a skill that could not do it either. At Quickstart nothing replaces /boss-learn: keep a reusable pattern as a dated line in your idea doc until you unlock MVP. boss sync will remove the old skill and tell you why (registry/supersedes.json).

  7. v0.320.02026-09-12

    nothing in your project changes. If you build on BOSS's plugin, npm run eval:plugin now runs the door case against a no-plugin baseline and prints the delta — needs a host with claude plugin eval out of early access (tested on 2.1.269).

  8. v0.319.02026-09-12

    /extract's description reads whole again — it said PRINCIPLE #1, YAML treats # as a comment, and your host had been showing it as "Pause and sort patterns — PRINCIPLE" for as long as the line existed. npm run check now refuses # in any shipped description. Nothing else about your surface changed.

  9. v0.318.02026-09-12

    if docs/RESUME.md grows past 200 lines, boss status says so in one line and tells you what to do — move what has shipped to the devlog; don't trim. /close now writes that rule into the RESUME header it creates. And ## 2026-09-12 (what today was about) is a devlog heading boss status can read; before, only a bare date was, so a titled entry made the re-entry line quote an older session.

  10. v0.317.02026-09-12

    /pretotype opens "Test demand BEFORE you build (not /prototype, which builds)"; /prototype opens "Get the idea onto the screen, fast (not /pretotype, which tests demand)". Same skills, same usage; the mis-type now corrects itself at the door.

  11. v0.316.02026-09-12

    the 48 skill descriptions your host reads on every turn went from ~3,650 words to ~2,270 (roughly 4.8k → 3.0k tokens per session). Same skills, same triggers, same Usage - lines; shorter sentences. boss map, boss help and the docs regenerate from the same source.

  12. v0.315.02026-09-12

    the task hygiene moment (v0.293.0) works again on every current model. It used to read your session's TodoWrite list; Claude Code 2.1.268 stopped offering that tool on Opus 4.8+, Sonnet 4.7+ and the Claude 5 family, so the moment had been silent for two weeks and could not say so. It now fires on time alone — the session has run 45+ minutes and nothing in .claude/rules/feature-context.md or docs/devlog.md has moved for that stretch — and hands the judgment ("is anything only in this chat?") to the model, which can see the chat. Writing something down still silences it.

The full changelog