v0.9.0

capcom — v0.9.0 — 2026-10-18

This release adds standing Parents, issues that exist only to group their children and never show up as work to pick up, and lets capcom ui show both panes at once on a narrow, tall terminal.

Breaking changes

• Marking an issue standing moves the store to format 5 — the first time any command leaves an issue marked standing, .capcom/config.yaml is raised to format: 5 with a warning, and older capcom releases can no longer read that repository; new repositories from capcom init start at format 5. What to do: upgrade capcom everywhere the repository is used, including teammates' machines and CI, before anyone marks an issue standing.
• The agent instructions in AGENTS.md read as out of date after upgrading — the capcom block now tells agents never to claim or close a standing issue, so capcom check and capcom agents --check report an existing block as stale. What to do: run capcom agents once to refresh the block.

New

• Standing issues — capcom create --standing or capcom update <id> --standing marks an issue as a parent that only groups its children, and capcom update <id> --no-standing removes the mark, even in the same call that claims the issue with --status. capcom show prints standing: true, --json output carries "standing": true, and a closed or in-progress issue cannot be marked.
• Standing issues never come up as ready work — capcom ready, capcom prime, the ready list in capcom ui and the now ready: line after capcom close all leave them out, while their open children stay ready as usual. capcom ready --all lists one with the reason standing: holds children, and capcom show prints ready: no (standing: holds children).
• Claiming or closing a standing issue is refused — capcom close <id> and capcom update <id> --status with an in-progress status fail with a message telling you to run capcom update <id> --no-standing first; closing several ids at once still closes the others.
• capcom check catches a standing issue that is closed or in progress — it reports it under the code standing, at the line holding the mark, and says how to fix it.
• capcom ui knows about standing issues — the detail pane shows standing: yes, and trying to claim, close or move one into an in-progress status shows a notice pointing to capcom update <id> --no-standing instead of changing anything.
• capcom ui shows both panes on a narrow, tall terminal — below 90 columns and at least 25 rows, the list sits on top and the details below, split by a rule you can drag or move with < and >; a double-click resets it to a third of the screen. The position is remembered between sessions as ui.stacked_ratio in state.yaml, and shorter terminals keep the one-pane view.

Docs & install

• Manual covers standing issues — the file format reference documents the standing key and store format 5, and the pages on issues, JSON output, the session briefing and the agent instructions explain how standing issues behave.
• Glossary defines Standing Parent — a new entry explains the term, and the entries for Ready, Parent and format version now account for it.
• Smoother demo in the README — the demo animation now zooms back out more slowly after the agent closes an issue.