Repository navigation
kabane 1.0.0-beta.0
Pre-releasekabane 1.0.0-beta.0
The first beta of kabane 1.0. It brings kabane onto current OpenTUI (0.8) and the current Agent Client Protocol stack (SDK 2.x, claude-agent-acp 0.99, codex-acp 2.5). It uses the new protocol features as they are meant to be used, so that kabane stays a thin wrapper that relays everything a harness asks to you.
Install it next to nothing else you care about first:
bun add -g kabane@betalatest stays on 0.3.0. A 0.3.0 install never updates onto a beta by itself. A beta install follows the beta channel with kabane update, up to the stable 1.0.0 when it ships.
Before you try it, back up your tracker. Opening your tracker with 1.0.0-beta.0 runs forward-only migrations (6: drops old permission-answer decisions; 7: agent_activities.author). Reinstalling 0.3.0 afterwards is not a rollback. See docs/getting-started.md, "Updating", for a consistent backup of the configured database.
Your harness can ask you things now
- AskUserQuestion and harness forms reach you. kabane now advertises ACP form elicitation. Before this, claude-agent-acp disabled AskUserQuestion under kabane and declined MCP elicitations, and codex's
request_user_inputforms were blocked the same way.- In the loop, a form becomes tracker questions: choices, multi-select, text, numbers and yes/no.
- In the board copilot, a form is filled one field at a time: digits for choices, toggles plus enter for multi-select, y/n, a text input; Esc declines.
- kabane never answers on your behalf.
- Withdrawn requests close. When the harness withdraws a permission request or a form, the loop's question closes as "withdrawn" and the copilot drops the prompt. Before, it stayed open, answering nobody. Stopping a loop claim closes its open questions the same way.
- Harness notices are shown. For example, "Auto mode unavailable for this model, using Accept edits". Before, kabane mislabelled that fallback as your own setting.
- Your terminal knows when kabane is waiting. The board reports OSC 7501 program status: blocked on a permission or question, working, or idle. Terminals that support it (Rex today) can show it; others ignore it.
- Multi-select and free-text answers from the board for loop questions, consistent with
kabane loop answer(1, 3or labels). The board and the loop judge an answer by the same rules. - Questions left by a runner that died close as withdrawn, so nothing stays pinned on the task.
The copilot knows your harness
- The harness's own slash commands (and Claude's skills) appear in the
/picker after kabane's shortcuts, labelled with the harness. A prompt starting with one, like/compact, goes to the harness exactly as typed. - Context usage ends every footer:
ctx 42% · $0.31. - Notices show their severity: warnings in the accent colour, errors in the failed colour, on the copilot and the loop alike.
The event log reads like a conversation
- Each tool call is one collapsed row: status, tool, first line of its arguments, duration. Click it, or press
tto open every row. The copilot's calls carry their real tool names, inputs and diffs too. - Runs of reads and searches fold into "explored · N reads, M searches".
- Edits open as diffs: unified, or split on wide terminals.
- The agent's words render as markdown.
- A toggled row keeps its place on screen.
The board on OpenTUI 0.8
- Copy over ssh lands on your machine.
ycopies through OpenTUI's clipboard: OSC 52 to your own terminal when the session is remote, the system pasteboard locally. xclip and wl-copy are no longer needed. - The theme follows your terminal live. Switch light or dark and the open board recolours, markdown included.
- One animation clock drives every spinner, so an idle board stops waking up.
- Platform fixes: retained paint, synchronized output over ssh, a fix for the Dvorak Ctrl+J binding, and a clean terminal restore after quitting over a slow link.
- Fixed rows stay visible beside long lists. Renderer teardown is awaited, so setup hands over to the board cleanly.
ACP
- SDK 2.1.0 on the stable v1 entrypoint.
- Adapters: claude-agent-acp 0.99.1 and codex-acp 2.5.0.
- codex 2.x makes
read-onlya real read-only sandbox, and renamesagentto "Auto review". - Both adapters now honour
promptRequiredfor an idle steer.
- codex 2.x makes
- Modes go through ACP session config options, which the spec says supersede session modes.
session/set_modestays as the fallback. kabane still only selects the harness's own auto mode, from its manual mode, and never overrides a mode your settings chose.
The loop
- An interrupted claim resumes in its harness session (
session/resume) instead of restarting blank. - A run moves the parent to in_progress and flags it for review when it completes.
- One fixer session takes every lens finding.
- Runs default to a worktree.
- A dead runner can be restarted, and runner liveness is safe against PID reuse.
- Tool-permission answers stay out of the decision log.
Also
- Config is discoverable and manageable from inside the app (
kabane config); sync and db keys are protected, and secrets are redacted on read. - Copilot permission requests queue, and a digit answers only a question that has been on screen long enough to read.
- kabane-launched sessions get an MCP server that codex does not replace (
kabane-session). - Release tooling: beta releases (
X.Y.Z-beta.Non npmbeta, as a GitHub prerelease); waiting for npm to serve a publish before calling it partial.
Known limits in this beta
- OpenTUI 0.8.1/0.8.2, SDK 2.4 and claude-agent-acp 0.100 were held back by a 5-day release-age policy. They follow in a later beta.
- Gemini was not exercised live; its paths are covered by tests.
- The live board checks for copilot permission status, multi-select AskUserQuestion and harness-initiated withdrawal were blocked by a harness usage limit during verification. They are covered by in-process protocol tests.