What Is This?
Kanbus is a simple way to keep project context with your code so people and AI helpers can pick up where you left off.
Why this exists
Work context gets lost when it lives in chats, docs, or someone's head.
When you ask an AI assistant for help, you end up with instructions and decisions scattered across chat logs, sticky notes, and temporary files.
Switch computers or tools, and that context disappears. Hand a task to a teammate or an AI agent, and they have to rebuild the story from scratch.
In plain English
A shared project notebook that lives with your code.
Kanbus stores tasks as small files right next to your code. That makes your repository the source of truth, and Git becomes the paper trail.
Any tool can read those files: a CLI, a board in your editor, or an AI helper. Everyone sees the same story.
Why Kanban?
A simple visual flow that started on Toyota factory floors and now powers tools like Jira.
Kanban means "signboard" in Japanese. Toyota used it to visualize work-in-progress on the factory floor so teams could see what was blocked, what was next, and keep flow steady.
Modern tools like Jira popularized the same pattern for software: columns for To Do, In Progress, and Done. Kanbus keeps that familiar board but stores the cards as plain files in your repo, so developers and AI helpers see the exact same source of truth.
What it's good at
Practical wins you feel immediately.
- Handing off work without losing context
- Switching computers or AI tools without re-explaining everything
- Keeping private scratch notes locally and sharing when ready
- Pulling Jira issues into your repo so agents can work on them
- Keeping living docs that update from real task data
How you use it
You keep work in one place, and your tools stay in sync.
Create a task, add notes, and update its status. Kanbus saves those changes as files, and Git keeps the history.
When you or an AI helper open the repo, the full context is already there.