Issue tracking that lives in your repository
Kanbus keeps your epics, tasks and bugs as plain files next to your code, so you and your coding agents plan, claim and finish work in the same place, with git as the history.
Get startedSee the ways to run it
Your agents already know how to use it
Kanbus speaks the vocabulary models were trained on: epics, tasks, sub-tasks, bugs, status and priority. An agent can read the board, pick up a task, comment on what it did and close it, with one short command each, and a person can follow along in a live board.
One file per issue
Every issue is a small JSON file in project/issues/. There is no database to run and nothing to sync, and two people editing different issues never touch the same file.
Git is the history
Board changes are commits. You review them in pull requests, branch them with your code and roll them back with git revert, like anything else in the repo.
Built for agents and people
A fast CLI for agents and scripts, a realtime board for people, and a wiki whose pages render live issue data, all reading the same files.
Change the file, and the board follows
The CLI is a thin layer over the files. Whether an agent runs a command or a person edits the JSON by hand, the console picks up the change and every open board updates.
Three ways to run it
Start with files on your own machine. The same board can also be served from the cloud or embedded in an application of your own.
Available now
Install the CLI, run kbs init in a repository and commit the board with your code. This is how Kanbus is used every day.
Preview
Push the board to a hosted git repository so people, agent sandboxes and CI all work from it, with optional live updates and a hosted board.
Preview
The Kanbus API and board components inside your own app, with issues stored in S3 and a DynamoDB catalog.
What people use it for
Agents record what they did and what is next, so a new session or a compacted context picks up where the last one stopped.
Everyone works from the same repository, and board changes ride along with the code they describe.
Run editorial and other pipelines
Define your own issue types and stages, and let hooks enforce what each stage needs before work moves on.
Install it in a minute
pip install kanbus
kanbus init
kanbus create "Write the sign-in form" --type task
cargo install kanbus
kbs init
kbs create "Write the sign-in form" --type task
kbsc
curl -L -o kbs.tar.gz https://github.com/AnthusAI/Kanbus/releases/latest/download/kbs-aarch64-apple-darwin.tar.gz
tar -xzf kbs.tar.gz && chmod +x kbs
./kbs init
Kanbus is free and open source under the MIT license. The Python and Rust command lines behave identically, because both are tested against the same behavior specifications.