Docs
Everyday commands
The handful of commands that cover most days with Kanbus, for people and for agents. Every command accepts --json for scripts.
Create and change issues
kbs create "Implement the OAuth flow" --type task --priority 1 --label auth
kbs create "Session expires during upload" --type bug --parent acme-4e3b31
kbs update acme-aeec87 --status in_progress --assignee you@example.com
kbs comment acme-aeec87 "Validation runs on blur now."
kbs close acme-aeec87
kbs create prints the new issue's id. Types follow the hierarchy in .kanbus.yml (initiative, epic, task, sub-task) plus the standalone types bug, story and chore. Statuses follow the workflow, so an issue can only move along the transitions it allows.
Find work
kbs list # every issue, grouped by status
kbs list --status in_progress
kbs list --search "landing page"
kbs ready # open issues that nothing blocks
kbs show acme-aeec87 # details, dependencies and comments
Connect issues
kbs dep acme-aeec87 blocked-by acme-91be04
kbs dep tree acme-4e3b31
Keep the board in git
kbs commit # commits project/issues
kbs validate # confirms every issue file parses
Kanbus writes files but never commits them for you. Run kbs commit whenever you commit code, and make it the last step of every agent's task.
Tag agent work
When an agent creates or changes an issue, it records who it is, so the board can show which product, model and session did the work.
kbs create "Write the release notes" \
--agent-platform "Claude Code" --agent-model "Claude Sonnet" --agent-name "Release notes"
Set KANBUS_AGENT_PLATFORM, KANBUS_AGENT_MODEL and KANBUS_AGENT_NAME in the agent's environment to avoid repeating the flags. Read about agent provenance