Shipmoor blog
Notes from the loop between agent and merge.
Engineering posts on the detectors that catch AI failure modes, product notes on the Shipmoor surface, and perspectives on what changes when agents write most of the diff.
Shipmoor 0.10.0: one CLI, a useful Free plan, and unlimited Pro
Shipmoor 0.10.0 replaces Community and IC with one account-based CLI: 30 days of full Pro for new personal accounts, a recurring Free workflow with four independent monthly allowances, and unlimited Pro for $19/month.
Read post-
A real Go regression, two Shipmoor tools: reviewing Alertmanager PR #2689
A hands-on walkthrough of Shipmoor Code Review and Claim Check on a public Alertmanager pull request that made optional maintenance callbacks panic on the default nil path.
Read -
Blast Radius: what else did that change touch?
Shipmoor 0.9.0 adds shipmoor blast, a change-blast-radius query over a committed link graph. It reports which acceptance obligations became suspect because their realizing code moved, and which code became suspect because an obligation moved while the code did not. Every link is authored by a human or minted from causal evidence when an obligation graduates to the deterministic floor. No lexical inference, ever, and the sparse graph that policy produces is reported as a gap rather than filled with a guess.
Read -
Shipmoor 0.9.0: less waiting between a code change and a trustworthy answer
Shipmoor 0.9.0 removes avoidable serial model-call waves from Code Review and Claim Check, adds phase-level timing, introduces an explicit no-plan option, runs independent filtering and judge work concurrently under bounds, and reuses frozen decompositions across rounds without weakening the verdict.
Read -
Shipmoor 0.8.0: the authoring loop closes Claim Check's last gap, and Test Evidence stops trusting a green checkmark
Shipmoor 0.8.0 ships the Claim Check design end to end: an acceptance set with a real approval step, a fix packet that names the exact test to write, and a tag-bound authoring loop that graduates a judgment call to the deterministic floor for good. Test Evidence joins as a companion producer that checks whether your tests actually passed, whether the suite quietly shrank, and whether a kept test was gutted, before Claim Check ever trusts a bare exit code.
Read -
Shipmoor 0.7.0: Claim Check gives a binding verdict on whether a change did what the author claimed
Shipmoor 0.7.0 adds Claim Check. You write an acceptance set of atomic obligations, the deterministic floor decides READY versus BLOCKED, and a bring-your-own intent fidelity judge adjudicates the judgment ACs the floor cannot check. A binding verdict and a VSA attestation, local, no source upload. The 0.7.0 release also splits the entitlement model: claim_check and code_review replace the old cli_pro and intent_scan.
Read -
Shipmoor 0.6.0: a code review that runs your agent, not ours
Shipmoor 0.6.0 adds Code Review, an advisory AI review of your change that runs your own coding agent, locally, with one command. It finds the soft problems the deterministic scan was never built to catch, it never blocks your build, and your source never leaves your machine. The scan gate you already trust is unchanged.
Read -
How an AI lab team runs Shipmoor as a CI gate on a brownfield Python monorepo
A field report on a diff-scoped Shipmoor CI gate across eight services in a complex Python monorepo, alongside Trivy, with SARIF and stable exit codes.
Read -
Shipmoor CLI v0.2.1: a scan output you can read in five seconds
v0.2.1 redesigns the scan output around the moment a reviewer reads it. A one-line verdict, a one-line context, findings grouped by file with blockers first, inline evidence and fixes, and a footer that tells you exactly what to type next. Plus a progressive explain view and color that means something.
Read -
After the agent, before the review: where AI code tooling misses the moment
A category argument for pre-merge integrity checks on agent-written code, and the eight-criterion proof-of-usefulness methodology we used to test our rules against three production-shape open-source projects.
Read -
Introducing the original Shipmoor CLI: verify agent work before review
The v0.2.0 launch record for Shipmoor's local scanner, including its first Python, TypeScript/JavaScript, and Go runs against Flask, Zod, and Cobra.
Read -
Why AI code integrity is the new category
AI-generated changes create a distinct verification problem: structural defects, unsupported claims, weakened tests, and hidden blast radius between agent completion and human review.
Read