Skip to content

Releases

BOA v1.1.1

Choose a tag to compare

@mrpickles007 mrpickles007 released this 18 Nov 18:15

BOA 1.1.1

A patch release: documentation only, no change to any tool, hook or template. A project on 1.1.0 updates with the
conservative update procedure of the 1.1.0 notes (docs/02-install-and-wiring.md, "Re-installing and upgrading");
nothing in the project needs a decision for this release.

Fixed

  • Updating the plug-in of a runtime's marketplace that was added at a release tag. Verified on the published
    1.1.0 in a throwaway configuration: for a marketplace added with #<tag>, the marketplace update command and the
    plug-in update command do not move it ("already at the latest version"), and adding the marketplace again at the
    new tag over the old one fails (its source does not match the entry the runtime already knows). The route that
    works: remove the marketplace, add it again at the new tag (<owner>/boa#vX.Y.Z), install the plug-in again (the
    remove also uninstalls it), then restart the session; one boa@boa is listed afterwards and the runtime cleans up
    the old cache folder. A marketplace added without a tag follows the default branch, and there the two update
    commands apply as before. The commands are in references/runtimes.md (the runtime's profile, "Updating the
    skill"); docs/02-install-and-wiring.md points to them.

New

  • The one-step plug-in install in the README's "Get BOA": /plugin install boa --marketplace <owner>/boa, for a
    runtime whose marketplace offers it (the versions that have it are in references/runtimes.md).

Get it

The release archive boa.tar.gz attached to this release (sha256 1b36e652de762ffd01c1cab86fb0aa166734f42402cf5f0ffc9f48c32dd9714e), the repository
itself, the open agent-skills CLI (npx skills add <owner>/boa) or a runtime's plug-in marketplace: the README's
"Get BOA".

BOA v1.1.0

Choose a tag to compare

@mrpickles007 mrpickles007 released this 18 Nov 17:34

BOA 1.1.0

A minor release: new features, nothing removed. A project on 1.0.1 or earlier updates with the conservative update
procedure below; read "Before you update" first.

New

  • A conservative update to a new release. Updating an installed BOA loses nothing the project or its agent
    changed: a file BOA installed and the project changed since is kept, the new version parked in .boa/pending/ and
    merged by the agent with git's three-way merge against the old release's rendering; an edited AGENTS.md block is
    kept; the project's own memory types and marker words get the release's new entries and keep their own. The
    package now carries a VERSION file, and the project records the installed version. The procedure, step by step:
    docs/02-install-and-wiring.md, "Re-installing and upgrading".
  • The pointer mode for an existing AGENTS.md (BOA_AGENTS_BLOCK=pointer, new key; full stays the default):
    BOA's rules go into their own file, docs/boa-rules.md, and AGENTS.md gets only a short marked block that
    points to it, with the precedence rule (the project's own rules win until a reconciliation task aligns them). The
    agent suggests it for a brownfield or refactor project whose AGENTS.md holds its own rules, and when AGENTS.md
    plus BOA's rules would pass a runtime's instruction-file size cap and the runtime cannot raise the cap at project
    level. The stack plug-in (.boa/stack/) and the marker
    words (.boa/markers.json) are now versioned in the project and never overwritten by a re-install.
  • A plan keeps its own column names. A plan column of .boa/markers.json may carry aliases: an existing
    project's own header names, accepted by every tool that reads the plan and kept by a language change.
  • Resuming in another runtime. A project paused in one agent runtime can be resumed by another on the same
    repository: the new agent wires its own runtime first, leaves the other runtime's wiring untouched and never
    bootstraps an installed project again.
  • Agent reuse. The lead resumes the same agent for the next round of a task while its context is moderate, and
    starts a fresh agent of the same role when the context has grown large (BOA_AGENT_FRESH_TOKENS, new key, default
    200000), rounds have piled up or the cache has expired.
  • Content rules for everything that leaves the machine. Commit messages, branch and tag names, pull or merge
    request titles and bodies and release notes are checked against the same rules as files (secrets, forbidden names,
    the product language, trailers), by the project's own hooks and tools.
  • The project's user documentation is kept current. A change that alters what a user of the project sees
    updates the project's user documentation in the same change, and a docs sweep checks every user chapter before a
    release, a milestone closure and the end of the project.
  • Remote runners, stated more precisely. With a runner configured but not reachable, a train stops and reports;
    with no runner the gate runs locally. Several runners are supported: each recorded with its capacity, slots and
    share, admitted and monitored on its own, picked by free capacity, a down one skipped and reported. The manual run
    of an expensive CI job takes a validated suite filter, and the full matrix runs once at the end.
  • How a bounded run is stopped. A run stopped at its timeout, by an interrupt, by a hangup or by the end of the
    agent session is stopped whole: the command and every process it started, its own cleanup given a bounded grace,
    then forced; no orphan, no leftover. The wiring proves it with a planted hanging case and an interrupted run.

Faster

  • Memory search. Identical results in the same order, less time as the memory grows. Measured 2026-11-18 side by
    side on the same quiet CPU-only host with 8 CPUs, before and after: a --query search that finds keyword matches,
    5.4 to 4.4 s at 10,000 memories, 8.8 to 6.1 s at 20,000 and 14.3 to 7.8 s at 50,000; one that falls back to meaning,
    8.3 to 4.7 s, 13.8 to 6.6 s and 31.9 to 11.6 s; a search without --query, 1.5 to 0.4 s, 2.9 to 0.7 s and 6.9 to
    1.3 s; a warm with nothing to do, 3.5 to 0.6 s at 10,000 and 7.5 to 1.2 s at 20,000; 1,000 new memories written into
    a bank of 1,000, 10,000 or 50,000 at once, 13.7 to 0.4 s, 94 to 1.2 s and 492 to 5.7 s. Peak memory is equal or
    lower. The vector cache is now a compact binary file (.boa/embed/cache/memory-vectors.bin), about 23% smaller than
    the old JSON one; the old JSON cache is deleted by the first save and rebuilt as needed.

Safer

  • The guard treats metadata changes (mode, owner, times, access lists) as writes to their targets, judges moves of
    the main branch's ref, and reads the scratch layout from BOA_SCRATCH_GLOB.
  • BOA's tools refuse to write through a path that is not a regular file (a device, a pipe, a socket, a directory; a
    link judged by its target), with a message naming it, before anything is written; the memory writer refuses such
    an input file before reading it.
  • Shipped texts name no runtime outside the runtime profiles; the profiles record verified install, update and
    uninstall commands for more runtimes.

Licences

The licence split changes: the texts BOA writes into a project (the templates and the references) are CC BY 4.0, the
code BOA copies into a project (the context-gate skill, the stack plug-in template, the memory types and markers
files) is MIT, and everything else stays AGPL-3.0-only. boa install writes docs/boa-notice.md into the project:
the one notice both licences ask for. The README's "Licence" section explains the split; REUSE.toml maps it file by
file.

Before you update

  • New config keys: BOA_AGENTS_BLOCK (default full) and BOA_AGENT_FRESH_TOKENS (default 200000): add them
    to .boa/config.env (the update procedure's step 5).
  • The traceability check's test files: the template's BOA_TEST_GLOBS is now empty until the agent sets the
    project's own layout at wiring; a project keeps the value it already has.
  • A release without a recorded version: 1.0.1 and earlier wrote no version into the project; the update
    procedure dates the installed release from .boa/installed.list.

Get it

The release archive boa.tar.gz attached to this release (sha256 c6e0a68378e06f15f072d5f5b57335bc7631827a03bcdf7db9d93eaeecf7bc02), the repository
itself, the open agent-skills CLI (npx skills add <owner>/boa) or a runtime's plug-in marketplace: the README's
"Get BOA".

BOA v1.0.1

Choose a tag to compare

@mrpickles007 mrpickles007 released this 16 Nov 18:21

BOA - Build On Autopilot, README update: the memory layer (typed memories, the 17 base types, hybrid search, supersede-only, easy to extend) now has its own section.

BOA is a skill that teaches an AI coding agent a complete, proven way of working: a lead agent plans the project into parallel lanes, each task goes through a builder, an adversarial reviewer, a tester and an integrator, with safety guards, persistent project memory, pause and resume, and a final requirements check. It works for new projects (greenfield), existing ones (brownfield) and refactors, on Linux, macOS and Windows.

Get it:

  • Claude Code: /plugin marketplace add mrpickles007/boa#v1.0.1, then /plugin install boa@boa; start with /boa:build-on-autopilot.
  • Any runtime with skills (Codex, Gemini CLI, OpenCode, ...): unpack boa.tar.gz below and put the boa folder in the runtime's skills folder; see references/runtimes.md.
  • Runtimes without skills: follow KICKOFF.md.

Prerequisites: git 2.31+ and Python 3.11+.

Licences: BOA's code is AGPL-3.0-only; the templates and every other file BOA writes into your project are MIT-0; the logo is all rights reserved (it may be shown in copies and modified versions of BOA to identify BOA). See LICENSE, LICENSES/ and REUSE.toml.

boa.tar.gz sha256: 4cf80bde9ab046a85827c7e658b94ed4cf0fc486aca743f698bf75d1614674ca

BOA v1.0.0

Choose a tag to compare

@mrpickles007 mrpickles007 released this 16 Nov 18:10

BOA - Build On Autopilot, first release.

BOA is a skill that teaches an AI coding agent a complete, proven way of working: a lead agent plans the project into parallel lanes, each task goes through a builder, an adversarial reviewer, a tester and an integrator, with safety guards, persistent project memory, pause and resume, and a final requirements check. It works for new projects (greenfield), existing ones (brownfield) and refactors, on Linux, macOS and Windows.

Get it:

  • Claude Code: /plugin marketplace add mrpickles007/boa#v1.0.0, then /plugin install boa@boa; start with /boa:build-on-autopilot.
  • Any runtime with skills (Codex, Gemini CLI, OpenCode, ...): unpack boa.tar.gz below and put the boa folder in the runtime's skills folder; see references/runtimes.md.
  • Runtimes without skills: follow KICKOFF.md.

Prerequisites: git 2.31+ and Python 3.11+.

Licences: BOA's code is AGPL-3.0-only; the templates and every other file BOA writes into your project are MIT-0; the logo is all rights reserved (it may be shown in copies and modified versions of BOA to identify BOA). See LICENSE, LICENSES/ and REUSE.toml.

boa.tar.gz sha256: 969b1e5be4403c93e8452d0ed00670af7df65ebb7642eb2dc7ce0abe8d730f05