Repository navigation
kabane 0.3.0
The first release since 0.1.0. It covers everything prepared for the unpublished 0.2.0
and what came after.
Loop extension (new, opt-in)
kabane loop drives a parent issue's subtasks to completion through coding harnesses
(Claude Code, Codex, Gemini) over ACP, from a detached runner. Turn it on with
"extensions": ["loop"] in config.json, or ask the copilot with /setup.
- Start a run from the board (
aon an issue) or withkabane loop start. A form shows
the run's settings before it fires; per-project defaults and gates go in
.kabane/loop.json. - Ready subtasks are claimed continuously up to a concurrency cap, in dependency order
(blocks,blocked_by,follows). Human tasks stay in the plan but are never dispatched. - Gates (named shell commands) run after each subtask and reopen it on red. An opt-in git
worktree with checkpoints you can roll back to. Verifier lenses review finished work and
file findings as child issues. - Each run is a board tab with one lane per agent session. Steer it from there: message an
agent, pause, skip, next, stop. - Harness permission requests are relayed to you, never answered by the loop. Answer them on
the board or withkabane loop answer. - Budgets for wall time, concurrency, continuations and spend (where the harness reports
it), plus stall and deadlock detection. Agents park blocked work withwaiting, and parked
work is never nudged or counted as a stall.
Board
- Tabs and attention over agent questions, replacing the sidebar.
- The copilot gets
/setup: it sets the copilot's harness and model and turns extensions
on, without editing JSON by hand. - Many fixes to tab, lane, banner and key handling in narrow panes.
CLI, MCP and core
- Concise agent reads (
responseFormat: concise) with bounded receipts and context chunks. - MCP accepts familiar comment and work-log input shapes.
- Official extensions are opt-in by name; an unknown name warns once.
kabane --versionnames the commit when run from a checkout.- A session waiting on a human is never swept as stale.
- Harness launches keep your own
CLAUDE_CODE_EXECUTABLEandCODEX_PATH.
Releases
- Verified, resumable releases and an explicit self-update.