Features
Features
Everything Kanbus does, from the command line your agents use to the board, the wiki and the policies that keep a project honest.
One CLI for every issue operation. Create, update, query and close work from the terminal, with plain output that coding agents can read and act on.
A local web console that shows your issues as a live board, read straight from the files in your repository and refreshed the moment anything changes.
Every issue is a JSON file in your repository. There is no separate database to run or sync, and your backlog gets history, branches and review from Git.
An optional notification layer that tells boards, agents and watchers about changes as they happen, before a git pull, while Git stays the source of truth.
Markdown pages in your repository that pull live issue data through templates, so status pages, roadmaps and reports are rendered from the board instead of copied from it.
Turn a labeled issue into one controlled coding-agent run that ends in a pull request and an issue in review, with your team deciding what starts and what merges.
Tag every issue and comment an agent writes with its product, model and session name, so a board shared by several agents stays readable.
Project rules written in Gherkin that block invalid changes and give agents the right guidance at the moment it applies, instead of in one long upfront prompt.
Run your own commands before and after Kanbus operations, with a stable JSON payload, so validations, notifications and integrations plug into the CLI without forking it.
Mount the Kanbus projects of sibling repositories into your workspace and query all of their issues from one place, without moving any files.
Keep personal or exploratory issues on your own machine, out of Git, and promote them to the shared board with one command when they are ready.
Pull issues from a Jira project into your repository as Kanbus files, so coding agents can read the context with the same tools they use for code.
A metrics view in the console that counts issues by status, type, project and scope, using the same filters as the board.
Use the Kanbus CLI and board on an existing Beads project without converting it, and migrate to one file per issue when you are ready.
Kanbus describes the board and nothing else. How your team specifies behavior, uses branches or keeps code risk down comes from methodologies you choose, replace or write yourself.
Open the Kanbus board in a VS Code tab, next to your code, with live updates as you and your agents change issues from the CLI.