1.16.0 — 2026-10-21

Release Notes

The route map is laid out in reading order, so a workflow with shortcuts and loops reads along its
main path; and the documentation is reorganised around what a person looks for: a first factory
that runs on one CLI, pages for updating and troubleshooting, the design inside the book, and a site
that describes the release you can install.

Compatibility. Nothing a factory does changes. Its route map — on the dashboard and from
layover graph --svg — may look different: columns follow the order its routes are declared in
rather than hop distance, so listing routes roughly in the order work flows keeps the map readable.
layover validate and layover explain say exactly what they said. The first factory,
examples/planner.toml, now runs every agent on Copilot CLI instead of Claude Code, Copilot CLI
and Codex; a factory copied from it before is unaffected. Links to sections of configuration.html
about runners, routes and updating, and of dashboard.html about chains, runs and cost, now land at
the top of the page that held them: those sections have pages of their own. For code that uses
layover-core as a library, diagram::Edge gains a via field.

Changed

• The route map is laid out in reading order, not hop distance. Columns come from a depth-first
  walk from the way in, visiting routes in the order layover.toml declares them; a route that
  closes a loop is drawn back. A production workflow whose analyst may send straight to agents
  several phases on had five agents in one column; it now reads analyst, consults, reviewer,
  developer, tester, operator, messenger. An edge that skips columns crosses each one clear of its
  boxes, a route back runs just below the columns it spans rather than under the whole map, and
  each agent's tooltip gives its hop depth as layover validate measures it. A sweep that spawns
  its reviewer now draws the reviewer's consults after it rather than beside the sweep's entry.
• The documentation recommends a CLI home of the factory's own — COPILOT_HOME,
  CLAUDE_CONFIG_DIR, CODEX_HOME, forwarded with env_from — so a factory's sessions stay out of
  the user's history and its agents never load the user's personal plugins and MCP servers. The
  install guide says how a variable reaches a Tower autostart starts; risk 30 records the hazard.
• The first factory needs one CLI. examples/planner.toml asked for three CLIs and an
  ANTHROPIC_API_KEY, and its Codex reviewer could not reach Layover, so the loop broke at its
  third agent. Every agent now uses the copilot preset.
• The site's root is the latest release's book, rebuilt when a release is published; main's
  is at /dev/, with a banner on every page saying it may describe what no release does yet.
• New pages: Updating Layover, Troubleshooting (by the message you see), Glossary, Runners,
  Routes and joins, and the dashboard's Chains and Runs views, each split from a page that had grown
  past 500 lines. The design documents — architecture, routing, the decision log and the risks —
  are pages of the book, written from docs/ when it is built.
• The decision log is split by topic into docs/decisions/, and the risks of releasing and updating
  into docs/risks-releases.md. Cutting a release moved from the install guide to RELEASING.md.
• The README is shorter, and the book's Status is the one list of what is and is not built. The
  CHANGELOG's older sections are cut to bullets, their Compatibility paragraphs unchanged.
• cargo xtask verify checks #anchors as well as links, absolute links to the repository and the
  site, that every docs/ file is a page of the book, and that every CLI command and flag,
  layover.toml key and HTTP endpoint is in its reference page. cargo xtask book writes the
  design pages.

Install layover-cli 1.16.0

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/KotkaZ/layover-project/releases/download/v1.16.0/layover-cli-installer.sh | sh

Install prebuilt binaries via powershell script

powershell -ExecutionPolicy Bypass -c "irm https://github.com/KotkaZ/layover-project/releases/download/v1.16.0/layover-cli-installer.ps1 | iex"

Install prebuilt binaries via Homebrew

brew install KotkaZ/tap/layover

Install prebuilt binaries into your npm project

npm install @layover/layover-cli@1.16.0

Download layover-cli 1.16.0

File	Platform	Checksum
layover-cli-aarch64-apple-darwin.tar.xz	Apple Silicon macOS	checksum
layover-cli-x86_64-apple-darwin.tar.xz	Intel macOS	checksum
layover-cli-x86_64-pc-windows-msvc.zip	x64 Windows	checksum
layover-cli-aarch64-unknown-linux-gnu.tar.xz	ARM64 Linux	checksum
layover-cli-x86_64-unknown-linux-gnu.tar.xz	x64 Linux	checksum

Verifying GitHub Artifact Attestations

The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:

gh attestation verify <file-path of downloaded artifact> --repo KotkaZ/layover-project

You can also download the attestation from GitHub and verify against that directly:

gh attestation verify <file-path of downloaded artifact> --bundle <file-path of downloaded attestation>