Release notes

How versions work

A version names one build of BLOM at https://blom.boundarylayerlabs.com. Everyone there uses the same build, so the current version is yours.

• The middle number goes up with each release that changes what BLOM does, and the last number with a release that only fixes something.
• Each version also names the parts your agent works with: the MCP contract, which BLOM's MCP server reports when your agent connects; the primer, which blom_read_primer returns; and the CLI, whose --version prints its number.
• Changes to these Docs and to this website come in releases of their own, listed here as Docs and website. They don't change BLOM's version.
• The BLOM method has a version of its own, which the method shows.

Dates are the day each release went live, in UTC.

Every version

Docs and website, 9 November 2026

• These release notes, with every version of BLOM. The current version shows under the Docs home's title and at the foot of every Docs page's sidebar.
• The CLI describes --key, which calls BLOM with the key your agent's setup keeps, and The MCP tools and the Docs home list twenty tools, with two reads that record nothing.
• Connect Codex or Claude Code checks the key with blom whoami --key, and its bash commands keep the key for that terminal only.
• What BLOM tells your agent, The MCP tools, Document headers, and four more guides describe what BLOM 0.4.0 changed, such as primer 5 and the Governed by line as a record part.
• Teams, People and access, Limits, Settings, and Pricing no longer describe adding or renaming a team, or a starting credit: BLOM has neither.
• Your PDLC and its gates says that an organization set up with a team keeps its one PDLC at that team.

BLOM 0.4.0

9 November 2026. Agent setup that keeps each key to its tool, two reads that record nothing, and a primer that tells your agent more. MCP contract 1.1, primer 5, CLI 0.1.0.

New

• BLOM's CLI takes --key claude-code, --key codex, or --key agent, and acts as the agent whose key your setup keeps for that tool, without printing the key. On Windows it reads your account's own variable, so it works in a terminal opened before the setup. If you downloaded the CLI before this version, download it again: it still reports version 0.1.0, and only the new download has --key. See The CLI.

Changed

• Connect Agent's setup prompt keeps each tool's key in a variable of its own, such as BLOM_KEY_CLAUDE_CODE or BLOM_KEY_CODEX, and checks it with blom whoami --key when BLOM's CLI is on your computer. See Connect Codex or Claude Code.
• Editing only a document's Governed by line keeps the revision you have: the line is a record part now. A revision recorded before this version counts the first such edit as a change, once. See Document headers.
• A product's open proposal of items can be replaced only by whoever made it or by an Administrator. Anyone else's new proposal is refused while it's open.

For agents

• Two reads that record nothing, blom_read_documents and blom_read_task: twenty MCP tools in all. See The MCP tools.
• blom_read_standards reads a standard's revision in force by its documentId alone.
• Primer 5 gives the agent its key's reach and expiry, your task types, what each phase is for, and each gate's purpose and requirements. Its method text tells the agent that where a repository's own instructions conflict with your standards, it follows the repository's and raises the conflict with you. See What BLOM tells your agent.
• MCP contract 1.1. A refusal names its cause in error.reason where it has one, and never for a record the agent can't find or may not see. Each tool advertises the text limits it enforces. blom_claim, blom_complete, and blom_propose_items carry destructiveHint. The server reports the contract's SHA-256 with its version when your agent connects, and the primer carries both.
• GET /api/v1/me gives an agent its key's reach and expiry.

Fixed

• Connecting by hand never shows the key you type. The PowerShell lines read it hidden, and pressing Enter without a key changes nothing. The bash lines turn tracing off before they use it.
• The setup prompt finds the Claude Code that the Claude desktop app bundles when claude isn't on your PATH.

Docs and website, 8 November 2026

• Thirty Docs guides now say only what BLOM does, each claim checked against BLOM's code, and two reference guides are new: Document headers and Write a standard.
• Limits lists about thirty more limits, among them a Git file's 1 MiB.
• Pricing marks each feature that isn't built Coming, and says that GitHub, Design Lab, and webhooks are switched off on https://blom.boundarylayerlabs.com for now.
• Security says what's in place today.

BLOM 0.3.1

7 November 2026. A fix to signing in. MCP contract 1.0, primer 4, CLI 0.1.0.

Fixed

• When GitHub or Google hasn't verified your account's email address, the sign-in page says so: verify the address there, then sign in again. On GitHub, that's Settings, then Emails. Before, the page said only that the sign-in didn't finish.

Docs and website, 6 November 2026

• Three new pages on this website: Coordinate Claude Code and Codex on one codebase, Keep specs and code in sync when AI agents write the code, and BLOM, Jira, and Linear. Every page's footer links them.
• How it works, Pricing, Enterprise, Security, and the Docs home open with one line on what BLOM is.
• Four lines on the home page and the Docs home now say that a claim shows who holds each step.
• For search engines and AI assistants: robots.txt, a sitemap, llms.txt and llms-full.txt, structured data on every page, a sharing card, and icons.

BLOM 0.3.0

4 November 2026. Removing members, usage counts, and edits that never overwrite someone else's. MCP contract 1.0, primer 4, CLI 0.1.0.

New

• Administrators remove a member, or change a member's role, on People and access, each with a reason. A removed member's records stay, and the agents they answer for stop acting. See People and access.
• Settings shows an organization's Administrators its usage: agent actions, reads, and calls past the daily cap, by day, by caller, and by product.
• A Job's description sits at the top of the Job, and anyone who may edit the Job edits it there.
• When you save a standard's text, a task's brief, an initiative, or a Job's description that someone changed after you started, BLOM saves nothing and keeps what you wrote. Choose Show the newer version, then Keep my changes on the newer version to carry your changes onto it.

Changed

• One person can found up to five organizations.
• Assigning a report takes over another holder's live claim on it, as assigning a Job does.
• The Privacy Policy's version of 3 November 2026. Everyone agrees to it at their next sign-in.
• BLOM's screens carry no explanatory notes. These Docs explain instead.
• Items to Jobs says when what's in Production is still being read, or can't be said, rather than showing a guess.
• The phone check says that BLOM shows your number only to you.

For agents

• Primer 4 covers notes, mentions, and reviews: an agent leaves a short note on a task with blom_add_note, a note's mentions put it in those people's and agents' queues, and blom_record_review records a review on its Job.
• BLOM counts each agent's actions and reads, day by day, in its organization's usage.

Fixed

• Fixes to leaving an organization, and to joining it again later.

BLOM 0.2.0

4 November 2026. Product View, Items to Jobs, default standards, and BLOM's CLI and public API. MCP contract 1.0, primer 3, CLI 0.1.0.

New

• Product View shows one product, and each item has a page of its own. See Product View.
• Items to Jobs assigns items to Jobs, with dependencies, notes, reviews, and sub-Jobs. Assign takes the place of the old claim controls. See Items to Jobs.
• BLOM's default standards arrive as drafts to approve, and the register tells you when BLOM ships a newer default. See Standards.
• Token use: agents report the tokens they used with their completions, and anyone can enter use from a tool that reports nothing. See Token use.
• Switch organizations from the rail, choose your default organization, and leave one.
• Three themes, Light, Soft, and Dark, on your profile. Light is the default.
• A Help menu, with Send feedback and Contact support, which names service@boundarylayerlabs.com.
• The Terms of Service's version of 2 November 2026.

Changed

• A new rail. Process is now PDLC, and Agents is now API keys. The work list, Initiatives, Coordination, Product summary, and Teams and products left the rail, and Atlas View still opens them.

For agents and developers

• Nine more MCP tools, eighteen in all: blom_read_primer, blom_read_items, blom_read_standards, blom_draft_standard, blom_propose_items, blom_add_note, blom_record_review, blom_send_feedback, and blom_dismiss_default_notice. See The MCP tools.
• Connect Agent gives you a setup prompt for Claude Code or Codex, and API keys holds each agent's keys. See Connect Codex or Claude Code.
• BLOM's CLI, version 0.1.0, which you download from BLOM, and the public API, with its OpenAPI document. See The CLI and The public API.

Fixed

• An approval binds the revision you read. If a standard changes while the approval dialog is open, nothing is approved, and the dialog says so.
• When signing out fails, BLOM says your session is still active and lets you try again.

Docs and website, 3 November 2026

• A new website at https://boundarylayerlabs.com, with How it works, Pricing, Enterprise, BLOM for documents, the BLOM method, and Security.
• These Docs, with 33 guides and a search.

BLOM 0.1.0

23 October 2026. BLOM's first version at https://blom.boundarylayerlabs.com. MCP contract 1.0.

For people

• Sign in with GitHub or Google, verify your phone number by text, and agree to the Terms of Service and the Privacy Policy. BLOM asks again whenever either changes.
• Create an organization in one step. BLOM sets it up with its first product and BLOM's default process.
• See your teams, products, and the items below them, and add or rename an item on its page, with a reason.
• Capture a task as a Job or a report. Set its priority, initiative, brief, and next action, move it through your PDLC's gates, and close it. A gate records its result and blocks nothing.
• Your queue, the work list, Initiatives, and Coordination, which shows the claims in progress, product by product.
• Claim a next action, renew the claim, and give it back. A claim gone stale can be taken over.
• Process: edit a draft of your PDLC and approve it.
• Standards: a register by category. Write a standard in BLOM, save its revisions, and approve one for Adopt.
• People and access: invite people with a link you copy, as a Viewer, an Editor, or an Administrator.

For agents

• An Administrator registers each agent, with the person it answers to, and issues its credential, shown once, with the commands that connect Claude Code or Codex.
• Nine MCP tools: blom_read_queue, blom_read_work_list, blom_capture_task, blom_claim, blom_renew_claim, blom_release_claim, blom_complete, blom_export_context, and blom_return_closure.

Related