Use case
Runs on Files in the cloud
Share one board across a team
When the board lives in the repository, everyone who can clone the code has it, and every change to the plan is reviewed and versioned with the code.
The problem
External trackers drift from the code. A ticket says done while the branch is still open, nobody can tell which issues a release actually closed, and every agent needs another account and API key just to read the plan.
How Kanbus helps
The board is a folder in the repository, so it branches, merges and ships with the code. The pull request that finishes a task can carry the change that closes its issue, so reviewers see both in one diff. Because each issue is its own file, people working on different issues never edit the same file.
The console shows the board live for anyone running it, and its realtime channel lets several people and agents on one machine see each other's changes as they happen.
What you set up
- Files in the cloud: the board pushed to your shared repository, committed with
kbs commitand pushed at the end of each task. - A unique project key and console port in
.kanbus.ymlfor each repository. - Optional policies and lifecycle hooks, so rules such as "a bug needs a reproduction before it moves to in progress" are checked by the tool, not by memory.