Use cases
Use cases
The same small set of files supports very different kinds of work. Here is how people and agents use Kanbus today, and which way of running it each one needs.
Local files
Agents record what they did and what is next, so a new session or a compacted context picks up where the last one stopped.
Files in the cloud
Everyone works from the same repository, and board changes ride along with the code they describe.
Local files
Follow work across many repositories
One board view across several repositories, while each repository keeps its own issues.
Local files
Hand issues to a fleet of agents
The issue router dispatches labeled issues to Codex or OpenCode and tracks each one through review.
Local files
Run editorial and other pipelines
Define your own issue types and stages, and let hooks enforce what each stage needs before work moves on.
Files in the cloud, with the hosted board (preview)
Show progress to people outside the repository
A hosted, signed-in board for people who follow the work but never open a terminal.
S3 and DynamoDB in the cloud (preview)
Put a board inside your own product
Use the Kanbus API and board components as the work queue inside an app of your own.