Skip to content

Releases

v0.9.0

Choose a tag to compare

@github-actions github-actions released this 08 Nov 12:32

kanbo 0.9 shows Markdown in the card dialog and lets a sub-task row drag onto any column. No board migration.

Added

  • The card dialog shows the description and comments as Markdown (headings, bold, italic, code, lists, task lists, tables, quotes, links). Nothing in them is parsed as HTML, and only http, https and mailto links are made.

Changed

  • A sub-task row drags onto any column. A sub-task sits inside its parent's card only while it is in the parent's column; in any other column it is its own card marked "Sub-task of KEY". The parent's bar still counts all its sub-tasks. A card folded into a row shows one level deeper under it.

v0.8.0

Choose a tag to compare

@github-actions github-actions released this 07 Nov 21:42

kanbo 0.8 gives the board page Modular's look, puts sub-tasks inside their parent card, and adds an Analytics view and a List view. No board migration.

Added

  • An Analytics view on the board page (?view=analytics): a range of 4, 12 or 26 weeks or a sprint, figure cards, finished per week, cumulative flow and time in column drawn in SVG, aging work, agents and people tables. It reads the same numbers as kanbo stats and fetches nothing while another view or a hidden tab is showing.
  • GET /issues/metrics on kanbo serve (from, to in unix seconds, or sprint=<id>; the last 12 ISO weeks to now by default), the metrics kanbo stats prints. A read; additive.
  • The board page: a List view (Board / List switch, ?view=list), column badges (a count, n/limit against a WIP limit in amber at the limit, and a lock whose tooltip lists a column's rules), keys (j/k, arrows, Enter, Space, x, /, Esc) and selecting several cards (a box, x, shift- and cmd-click) with a floating bar that sets their column or priority in one PATCH /issues/bulk.
  • The board page ships Geist (variable woff2 in latin, latin-ext and cyrillic, SIL OFL 1.1) under /assets/fonts/; the page's content security policy gains font-src 'self'.

Changed

  • The board page takes Modular's look: Geist type, a near-white neutral palette in light and dark, white cards with a hairline ring on quiet column bays, a 28 px toolbar with Filter and Display menus, status-category and priority icons, and toned label chips. It replaces the strip-board design.
  • Sub-tasks (a card with a parent) now live inside the parent's card as rows with a progress bar (1/3 done), and a waiting or running sub-task is never hidden (the parent shows a Sub-task waiting for you pill). Display → Show sub-tasks as cards (?subtasks=cards) draws them as cards of their own, marked Sub-task of …. The card dialog gets a breadcrumb to the parent, a sibling switcher, a Sub-tasks section and a property grid. "Sub-card" is now "sub-task" on the page.
  • The kanbo init wizard no longer asks "Add a first card?" or "Write these changes?": it asks where the board lives, the card key, the columns and which agents to connect, then writes and prints what it did. --first-card <title> still adds a first card.
  • In a folder with no board of its own, when only KANBO_DB_PATH names an app's database that is older than this kanbo or has no project for the folder, kanbo answers "This folder has no kanbo board of its own … run kanbo init here" instead of blaming the app's database. A binding or --db naming that database keeps the old sentence.

v0.7.0

Choose a tag to compare

@github-actions github-actions released this 07 Nov 07:54

kanbo 0.7 gives agents one way onto the board: the MCP server. The terminal keeps the person's commands. No board migration.

Removed

  • Breaking: the commands kanbo claim, ready, prime, run (all subcommands), card (all subcommands), capabilities and instructions. Agents use the MCP server's tools; people use the board page (kanbo serve) and the commands that stay (init, connect, doctor, uninstall, board, columns, approve, return, sprint, stats, serve, mcp, migrate, roles).
  • Breaking: kanbo init --instructions, --mcp and --global, and kanbo connect --no-instructions and --no-mcp. kanbo writes no instruction block anywhere any more. kanbo init --json no longer has the instructions and mcp fields; kanbo connect --check --json rows lose instructions and gain oldSections.
  • Breaking: the library exports KANBO_TOOL_CLI_EQUIVALENTS and KanboToolCliEquivalent, and the cli field of each tool in the capabilities manifest (manifest version 4). The 17 tool names, their inputs, buildKanboTools, createHttpTransport and includeRunTools are unchanged.

Changed

  • kanbo connect registers only the MCP server, in your own configuration by default (so one registration serves every project; --project writes the project's files), and removes the kanbo section older versions wrote into CLAUDE.md, AGENTS.md and GEMINI.md. A section you edited is kept, with a note.
  • kanbo init writes no agent file, and asks about agents only when one found here has no kanbo MCP registration; with --connect it registers the MCP server as kanbo connect does.
  • kanbo doctor warns about old kanbo sections (and --fix removes them) and about a machine where no agent has the MCP server registered, instead of warning that no section exists.
  • The MCP instructions tell an agent to finish the run it claimed with kanbo_run_finish, and to leave the board alone in a folder that has none.
  • A plain kanbo init makes the project's own board even when KANBO_DB_PATH is set; kanbo init --db <path> binds a project to an app's database.

Fixed

  • kanbo connect --check called kanbo's own Claude Code registration "yours": Claude Code adds an empty env to the entry it writes, which now counts as kanbo's own (an env with a variable is still yours).
  • kanbo mcp stopped at startup when KANBO_DB_PATH named a database it could not use (older than this kanbo, or with no project for the folder). It now starts, and each tool says why.

Upgrading

Run kanbo connect <agent> or kanbo doctor --fix once to take the old kanbo section out of CLAUDE.md, AGENTS.md and GEMINI.md. Agents that used kanbo prime, kanbo claim or kanbo card … in a shell use the MCP tools instead; register the server with kanbo connect.

v0.6.0

Choose a tag to compare

@github-actions github-actions released this 06 Nov 15:54

kanbo 0.6 measures how work flows on a board. No board migration: 0.5.0's index is all the metrics need.

Added

  • kanbo stats: how work flows on the board over a range — cycle and lead time as p50 and p85, cards finished per ISO week, work in progress against each column's limit, aging cards, time in column, returns (moves back into an earlier unstarted or started column, by anyone, split by people, agents and outside writers), first-pass approval, attempts, and one line per agent and per person; --from, --to, --sprint <id>, and --json with the cumulative flow by day. Canceled cards are counted apart.
  • For applications that use kanbo as a library: computeBoardMetrics(history, input, now) and the BoardMetrics types, createBoardOps(store).boardMetrics(input) and .readBoardMetricsHistory(workspaceIds) (a host with workspaces on several boards puts their rows together and computes once), boardMetricsRuns (the counted runs, and the canceled cards' apart), boardMetricsAgentKey, nearestRank, isoWeekOf, utcDayLabel, IsoWeek. BoardErrorCode gains board_metrics_range_invalid (400).
  • BoardStore gains runs.listByWorkspaces(workspaceIds) and comments.listByWorkspaces(workspaceIds, authorKinds); an application that implements BoardStore itself must add both.

v0.5.0

Choose a tag to compare

@github-actions github-actions released this 06 Nov 08:11

Run kanbo migrate after upgrading (on a board file kanbo doctor --fix does it too; on a shared Postgres board run kanbo roles apply after it, as after every migration). 0.5.0 adds two columns to issue_statuses and an index to issue_field_changes. Until the board is migrated, a read or a write is refused (exit 3, "Run kanbo migrate"). An app that keeps the board in its own database adds the same migration and pins this exact version.

Added

  • Flow rules on a column: which columns a card may enter it from (allowedFrom) and the most cards it holds (wipLimit). They are checked at the same door as entry rules, for every writer: an agent moving, creating, bulk-moving or claiming a card against them is refused with board_column_rules_unmet and one line per rule (- allowed_from: Done accepts cards from In Review only, - wip_limit: In Progress holds 3 of 3); a person goes through and is warned. A bulk move is held to a WIP limit as a whole. kanbo columns flow <column> --from <columns|any> --wip <count|none> sets them (a person only, exit 4 in an agent's shell). kanbo prime, kanbo_columns, kanbo columns list and GET /issues/statuses show them. Deleting a column takes it out of every list; a list it empties accepts cards from no column, not from every one.
  • New boards start with the standard flow: Done accepts cards only from In Review (from In Review and QA on a Review + QA board). Existing boards keep their columns as they are.
  • kanbo claim [card], the kanbo_card_claim tool and POST /issues/claim: take a card to work on in one step. The run starts and the card moves from To Do into the board's first work-in-progress column in one write, and two agents never get the same card — the one that loses is told board_nothing_ready or board_card_not_ready (run_active, waiting_for_person, not_in_to_do). kanbo prime, the MCP server's instructions and the orchestrator guide tell agents to claim instead of starting a run and moving the card. kanbo_card_claim is published to every MCP host, including one that passes includeRunTools: false.
  • For applications that use kanbo as a library: createBoardOps(store) gains setColumnFlowRules, applyStandardFlow, claimCard and listColumnEntries. listColumnEntries({ workspaceIds, since, limit }) lists every entry into a column since a moment, in (at, changeId) order, from the cards' own history — so it sees every writer — and never ends a page inside a second. The package root exports readFlowRules, ColumnFlowRules, FLOW_RULES, ClaimCardInput, ClaimedCard, ColumnEntry. BoardStore gains issues.lockById and fieldChanges.listByFieldSince; KanboToolTransport gains cardClaim. BoardErrorCode gains board_card_run_active, board_nothing_ready, board_card_not_ready (all 409) and board_flow_rule_invalid (400).

Changed

  • A card has one run going at a time: starting a second run on a card whose run is still going is refused with board_card_run_active, naming that run — through kanbo run start, kanbo_run_start, POST /issues/:id/runs and an app's own launch alike. Finish or stop the first run before starting another.
  • A card created in a column records that column in its history as a change from no column, filed under whoever created it. The activity feed and the board page's History show it as the card's creation, as before; kanbo card get --include history and GET /issues/:id/field-changes list the row.
  • The instruction block kanbo init and kanbo connect write says "Take work with kanbo claim" (block v3). kanbo doctor reports a v2 block as written by an older kanbo, and kanbo connect or kanbo doctor --fix brings it forward; a block you edited is kept. kanbo instructions agent says the same.
  • A board file a migration behind refuses a read as it refuses a write — exit 3, with the sentence that names kanbo migrate — instead of failing on the missing column. A board whose only difference is its schema stamp stays readable. kanbo mcp on such a file stops at start with the same sentence, as on an outdated Postgres board.

v0.4.0

Choose a tag to compare

@github-actions github-actions released this 04 Nov 19:01

Added

  • The board page shows sub-cards: a sub-card names its parent (click opens it), a parent shows how many of its sub-cards are done, and its panel lists them with their column, waiting or running state and who works them.
  • A card's panel on the board page opens with who made it and who works it, and its History reads as a timeline by day: who, the field, the old value → the new one, when (the exact time on hover), and the before and after text of a description change.
  • The board page filters cards by text, by who works them, by waiting for you, by running, by priority and by label; the filters live in the address and / focuses the search.
  • kanbo serve stops by itself about 5 seconds after the last board tab closes (2 minutes if a tab vanished without a goodbye) when it opened the browser itself; with --no-open, from an agent's shell or without a terminal it still runs until Ctrl-C. The board page tells the server it is open with POST /page/presence, and says plainly when the server has stopped.
  • kanbo serve offers every project kanbo knows (~/.kanbo/projects.json): a project dropdown on the board page, a header line saying the project's folder and where its board lives (a board file, or the Postgres host), GET /projects, GET /issues/workspace and the /projects/:id/issues/... routes. Started outside any project, it opens the most recently used one.
  • kanbo remembers each project folder it opens a board in (and kanbo init binds), in ~/.kanbo/projects.json — the folder's path and when it was last used, nothing else, written at most once a day per project; KANBO_HOME moves the folder. It is the list the board page will offer.
  • kanbo_card_update takes parent, and kanbo card update takes --parent <card>: a card created at the wrong level is put under another card, or back on the top level with "none" (--parent none), and its history records the move like any other field's. A null for parent is read as not given — models send null for the fields they are not changing — so it never takes a card out from under its parent. The MCP server's instructions and the commands kanbo prime prints say so in one line each.
  • For applications that use kanbo as a library: KanboCardUpdateInput.parent (string | null; null is the top level, absent leaves the parent as it is) — a hand-written KanboToolTransport passes it on, and createHttpTransport sends it as parentIssueId, the card's exact id, as for a new card. BoardErrorCode gains issue_parent_cycle, 400 in BOARD_ERROR_RESPONSES.

Changed

  • A card on the board page opens in a large dialog instead of the narrow side panel: title and state on top, description, sub-cards and Comments / History / Runs tabs on the left, the decision and details on the right. Esc, ✕ or a click outside closes it; a board change an agent makes no longer resets your tab or scroll.
  • The board page has a new look (src/serve/page/DIRECTION.md): a strip board of paper and ink, light and dark. Each card carries a coloured edge for its state — orange only for "Waiting for you", blue while an agent runs it ("Running · claude"), green when done — and reads top to bottom as state, title, key and who works it, status line, priority and labels. The board fills the window under the bars and each column scrolls on its own. Only what changed moves: a card that is new or changed column fades in once, a badge calls once when a card starts waiting, a card's window fades in when it opens — never on an ordinary refresh, and nothing at all with reduced motion. On a narrow screen the token field folds into a "Token" button once a token works. History entries from before today show their clock time under their day.
  • The MCP tools that write a card — kanbo_card_create, kanbo_card_update, kanbo_card_move, kanbo_status_line, kanbo_wait_approval — answer with the card compact, on one line, as kanbo_card_list prints it (id, title, column slug, statusLine, waitingFor, parentId, attempt, activeRun, updatedAt), instead of every field pretty-printed: an orchestrator writing its card 20–40 times a session got 5–19k characters back each time — 19k for a one-sentence status line — and read them again on every later turn. Each takes detail: "full" for the whole card, as before. The CLI prints what it printed. For applications that read these tools' answers: they are compact now; pass detail: "full" for the old answer.
  • A write from an agent's shell is filed under the agent's name (claude, codex, cursor, gemini), and one through kanbo mcp under that, else the MCP client's own name, instead of the operating-system user; KANBO_ACTOR_ID still wins. The board page shows the writes of the person who started kanbo serve as You and every other writer by name. Rows written before this keep the OS user name, so on an existing board an agent's old writes now read as You.
  • A comment written from the board page is the person's (authorKind: user), and the page writes under the person at the machine (KANBO_ACTOR_ID in a person's shell, else the OS user) even when kanbo serve was started from an agent's shell, where it used to sign them with the agent's name. A request without the token, or sending x-kanbo-actor: agent, still writes as the server's writer. Rows written before keep what they were written with.
  • Approvals and returns read You on the board page, not kanbo.
  • kanbo card get and kanbo_card_get say who wrote each comment: kanbo_card_get comments gain by (the person's or agent's id, the outside writer's name, kanbo for the board's own lines), a person's approval or return reads author: user, and card get prints krowli (person): …, claude: …, kanbo: Run finished.
  • On the board page an outside writer's chip in Comments has the agent look as in History; "Worked by" names the agent of the latest run (claude · finished) once its run is over; POST /page/presence answers 204 instead of 404 on a server that does not stop by itself, and the page stops sending, so the console stays clean.

Fixed

  • A card can no longer be put under one of its own sub-cards, at any depth: the board operation refuses it (issue_parent_cycle — "A card can't be put under one of its own sub-cards."), so PATCH /issues/:id does too, where it used to write the loop. A loop already in a board's data does not hang the check.

v0.3.0

Choose a tag to compare

@github-actions github-actions released this 28 Sep 13:49

kanbo 0.3 is about getting started without reading anything first — kanbo alone sets a project up or shows its board — about running the same everywhere (Windows included), and about agents spending fewer calls and tokens on the board. Boards need no migration: a board file or Postgres board 0.2.1 wrote opens as it is.

Added

Getting started

  • Bare kanbo: with nobody to ask (no terminal, or an agent's shell) it prints a short hint — how to set a board up, or a few lines about the board — and exits 0. At a terminal in a folder with no board it starts the init wizard; with a board it opens the home screen: the column counts, the cards waiting for you, which agents are connected, and a menu (review waiting cards — approve or send back with a comment —, show the board, open the board page, add a card, connect an agent, get the instructions, change columns, check the setup, update kanbo).
  • The kanbo init wizard: where the board lives (a file in the project, or a shared Postgres database), the card key (suggested from the folder name), the columns (Standard, Simple, Review + QA, or your own), which agents to connect, and a first card — then the full list of changes and one "Write these changes?". Ctrl-C at any question leaves the folder exactly as it was. Every answer is also a flag: --key, --columns <template or list>, --connect <agents>, --first-card <title>, --migrate (create the Postgres tables now).
  • Plain kanbo init (no flags, nothing naming a board) creates a board file of the project's own, .kanbo/board.db, with the standard columns and a card key from the folder name.
  • kanbo connect <agents> (alias kanbo setup) for claude, codex, cursor, gemini or all: the kanbo section in each agent's instruction file and kanbo's MCP server in its settings, --project or --global; --no-instructions, --no-mcp, --check (what is connected; exit 1 when a named agent is not), --remove, --dry-run, --yes. It changes only what kanbo wrote, in the shape it wrote it: an MCP entry or an instruction block you edited is left alone, and removing an entry of your own asks first (default No). A shared AGENTS.md section stays while Codex or Cursor still reads it.
  • kanbo instructions [agent|short|global|orchestrator|mcp|board] prints the text an agent needs, with --copy (clipboard on macOS, Windows, WSL, Wayland, X11, or OSC 52 over SSH) and --markers.
  • kanbo board: the board in the terminal, one section per column, cut to the terminal's width; Done and Canceled show their last five cards unless --all; --column, --json [fields].
  • kanbo columns add|rename|move|remove|template|add-standard, and a menu with kanbo columns alone at a terminal. remove moves the column's cards to --move-cards-to (or asks). To Do can't be removed or renamed to another slug — kanbo ready takes work from it. All of these are a person's (exit 4 in an agent's shell).
  • Column templates: standard (Backlog, To Do, In Progress, In Review, Done, Canceled), simple, review-qa, and ready-made columns (QA, Blocked, …) by name in --columns.
  • kanbo doctor --fix [--yes]: fixes what is kanbo's own — an instruction block from an older kanbo, kanbo's own MCP entry whose Node or script moved, a board with no columns, a board file a migration behind — after one plan and one question (default Yes), then checks again. It never deletes anything. Without a terminal and without --yes it prints the plan and Run kanbo doctor --fix --yes to apply.
  • kanbo doctor checks columns (a board with no columns), install (kanbo running from npx's cache) and update (a newer kanbo, status info); --json findings carry fixable.
  • Update check: every run asks npm once for the latest kanbo-cli, alongside the command (never holding it more than 0.3 s after it finishes; no schedule, no cache). A person at a terminal running a global install is asked whether to update (default No), and a yes runs npm install -g kanbo-cli@latest; a permissions failure points at npm's guide. The home screen shows it with a menu item. Nothing is installed on Windows from the running kanbo (Close kanbo and run: …), in a project's own install (This project installs kanbo; update it here: npm install kanbo-cli@latest) or from npx (npx runs the newest kanbo when you pass @latest: npx kanbo-cli@latest). An agent's shell is told kanbo X is available (running Y). Ask a person to update: npm install -g kanbo-cli@latest; kanbo mcp ends kanbo_prime with the same note; kanbo doctor shows it as a finding. Off in CI, with KANBO_NO_UPDATE_CHECK=1 or NO_UPDATE_NOTIFIER, and for --json, --version, --help and kanbo mcp's own output.

For agents

  • kanbo mcp starts in a folder with no board: every tool answers This folder has no kanbo board yet. Ask a person to run kanbo here., and a board created there meanwhile is picked up on the next call.
  • Agent shells are recognised by the marks their tools document or set: CLAUDECODE=1 (Claude Code), GEMINI_CLI=1 (Gemini CLI), CURSOR_AGENT (Cursor's agent terminal) and CODEX_THREAD_ID (Codex, every shell command it runs), as well as KANBO_ACTOR_KIND=agent. In such a shell the person-only commands exit 4, nothing asks a question, column entry rules refuse instead of warning, and a Postgres board's agent connection string is used. KANBO_ACTOR_KIND=person overrides the marks for a person's own terminal.
  • Every question an agent asks of the board is one call (docs/agent-efficiency.md). kanbo_card_list takes columns, waitingForPerson, returned, parent, hasActiveRun, text, updatedSince (unix seconds, an ISO date-time with Z or an offset, or YYYY-MM-DD for UTC midnight), labels, priority, offset, detail and fields; kanbo_ready takes offset, detail and fields; kanbo_card_get takes include (comments, subCards, runs, history, prs) and commentLimit. The CLI has the same: kanbo card list --column a,b --waiting --returned --parent <card> --active --text <t> --updated-since <time> --label <l> --priority <p> --offset <n> --all, kanbo ready --all, kanbo card get --include <parts> --comments <n>. text ignores case in any script (über finds Über) on SQLite, Postgres and over HTTP alike.
  • Returned cards — sent back by a person and not picked up again (latest decision a return, not waiting, no run) — come first in kanbo_ready (under returned), kanbo ready and kanbo prime, each with the person's comment. A list's card that is waiting or returned carries lastComment (who, the first 200 characters, when); kanbo card list prints it, and a waiting card's status line, under the card.
  • The MCP tools take the argument names agents reached for as well as their own: card also as id, cardId or key; kanbo_card_comment's content also as text; kanbo_status_line's and kanbo_wait_approval's text also as content; kanbo_run_finish's run also as runId or id; kanbo_run_start's agent also as agentName; kanbo_card_move's column also as to. The CLI likewise: kanbo card comment --text, kanbo card status-line --content, kanbo card wait-approval --content. The JSON Schema a client lists is unchanged; both names with different values are refused.
  • A run's finish state also reads completed, succeeded, success, done as finished; error, errored as failed; cancelled, canceled, aborted as stopped. kanbo run start prints the command that finishes the run; kanbo_run_start answers with finishWith.
  • kanbo run start without --session and kanbo_run_start without session record the session of the agent they run under — CLAUDE_CODE_SESSION_ID (Claude Code) or CODEX_THREAD_ID (Codex), when exactly one is set.

For applications that use kanbo as a library

  • createBoardOps(...): queryCards(input) and queryReady(input) (a page of cards, the total and the columns, filtered by the database), renameColumn, moveColumn, removeColumn(workspaceId, column, { moveCardsTo }, actor) (moves the cards in the same write; returns movedCards and unmetRules), addColumn(workspaceId, { name, description, color, category, position }, actor), applyColumnTemplate(workspaceId, columns, { mode: 'seed' | 'add-missing', actor }), readCardAttention(cards, running).
  • Exports from kanbo-cli: suggestCardKey, isValidCardKey, CARD_KEY_PATTERN, COLUMN_TEMPLATES, COLUMN_TEMPLATE_IDS, COLUMN_CATALOGUE, and the types ColumnSpec, ColumnTemplateId, AddColumnInput, ApplyColumnTemplateOptions, ColumnPosition, RemoveColumnOptions, RemoveColumnResult, BoardCardQuery, BoardCardPage, BoardMilestoneCardCount, CardQueryInput, CardQueryResult, CardAttention, CardLastComment.
  • Exports from kanbo-cli/mcp — what a hand-written KanboToolTransport is written against: the types KanboCardQuery, KanboCardPage, KanboReadyPage, KanboCardInclude, KanboCardDetailResult, KanboCardFacts, KanboCardCommentResult, KanboFieldChangeResult, KanboSprintResult, KanboCardCreateInput, KanboCardUpdateInput, KanboRunStartInput, KanboRunFinishInput; the constants KANBO_CARD_INCLUDES, DEFAULT_KANBO_CARD_INCLUDES, DEFAULT_KANBO_COMMENT_LIMIT; and the helpers matchesKanboCardQuery and pageOf.
  • BoardErrorCode gains board_column_name_taken, board_column_not_empty (details.cardCount), board_column_ready_protected, board_column_remove_target_invalid and board_column_structure_requires_user, each with a row in BOARD_ERROR_RESPONSES.

Changed

  • Windows is supported and tested like macOS and Linux (CI on Windows, macOS and Linux, Node 22 and 24): programs are found and started the Windows way, files kanbo edits keep their CRLF line endings and byte order mark, a file Windows holds open is retried, and MCP registrations in your own settings start...
Read more

v0.2.1

Choose a tag to compare

@github-actions github-actions released this 27 Sep 16:54

Changed

  • License: MIT → PolyForm Noncommercial 1.0.0. Free for personal, research, educational and other noncommercial use; selling kanbo or building it into a paid product or service needs a separate license from the author. Versions up to and including 0.2.0 were released under MIT and stay under MIT.

v0.2.0

Choose a tag to compare

@github-actions github-actions released this 27 Sep 10:37

Removed (breaking)

  • The board-copy API: readBoardSlice, writeBoardSlice, deleteBoardSlice, emptyCopyCounts and the BoardSlice / BoardCopyCounts types. Nothing in kanbo used them; copying a workspace's board between storages belongs to the application that owns those storages.
  • Six BoardErrorCode values kanbo never raises, and their BOARD_ERROR_RESPONSES rows: board_copy_conflict, board_mixed_workspaces, board_storage_not_configured, board_storage_not_empty, board_storage_not_prepared and board_storage_unavailable.

Added

  • assertReturnable(issueId, { toStatusName? }, actor) on createBoardOps(...): every reason returnCard would refuse, asked on reads alone, resolving to the column the card would go back to. returnCard runs the same check inside its write.
  • Releases are published to npm from GitHub Actions with npm trusted publishing and provenance.

kanbo 0.1.3

Choose a tag to compare

@Krowli Krowli released this 26 Sep 18:43

Added

  • kanbo init --global: sets up your own agent tools for every project. Writes a global instruction block to ~/.claude/CLAUDE.md and $CODEX_HOME/AGENTS.md (or ~/.codex/AGENTS.md), and to ~/.gemini/GEMINI.md when asked for (--instructions claude,codex,gemini); registers kanbo mcp with Claude Code (claude mcp add --scope user kanbo -- kanbo mcp, printed when claude is not on PATH), Codex ([mcp_servers.kanbo] in $CODEX_HOME/config.toml) and Cursor (~/.cursor/mcp.json). The global block binds no board and no board is created: it tells agents to use kanbo in projects that have .kanbo/. Shows a preview and asks unless --yes; reports written / unchanged.
  • kanbo doctor [--json]: checks the kanbo version, another kanbo earlier on PATH, better-sqlite3, the project binding, that the board opens with a current schema, that every instruction block is the one this version writes, that every kanbo MCP registration's command is on PATH, a real MCP initialize handshake with kanbo mcp, and KANBO_ACTOR_KIND=agent in your own shell. Each finding is ok, warn or fail with a fix; exits 1 on any fail.
  • kanbo uninstall [--project|--global] [--purge] [--yes] [--json]: removes the marked instruction blocks and the kanbo MCP entries (JSON and TOML), leaving everything else in those files; runs or prints claude mcp remove kanbo --scope user. Never touches boards unless --purge, which removes .kanbo/binding.json and deletes the project's board file only after a confirmation naming it (--yes does not answer it).

Changed

  • A stale instruction block is rewritten by running kanbo init again; kanbo doctor says which command. Blocks are not refreshed automatically.