cac10af5e1
- Add enginePaused field to Settings type with soft-pause semantics (drain queue, don't kill agents) - Gate scheduler, triage, auto-merge, and periodic merge retry on enginePaused - Add Pause and Stop buttons to dashboard Header replacing single toggle - Wire enginePaused state through App with optimistic toggle and unpause resume logic - Add tests for scheduler, triage, dashboard CLI, Header, and App covering pause behavior
@dustinbyrne/kb
AI-orchestrated task board CLI. Create tasks, and let AI agents specify, execute, and deliver them — powered by pi.
What it does
kb is a kanban-style task board where AI does the heavy lifting. Toss in a rough idea and the AI engine writes a full specification, resolves dependencies, executes the work in isolated git worktrees, and hands you the result to review and merge.
Tasks flow through five columns: Triage → Todo → In Progress → In Review → Done.
Installation
npm install -g @dustinbyrne/kb
Authentication
kb uses pi for AI agent sessions and reuses your existing pi authentication. You can also authenticate directly through the dashboard UI.
If you don't have pi set up yet: npm i -g @mariozechner/pi-coding-agent && pi then /login.
Usage
Start the dashboard
Launch the web UI and AI engine:
kb dashboard
kb dashboard --port 8080
Create a task
kb task create "Fix the login redirect bug"
kb task create "Update hero section" --attach screenshot.png --attach design.pdf
Manage tasks
kb task list # List all tasks
kb task show KB-001 # Show task details, steps, and log
kb task move KB-001 todo # Move a task to a column
kb task merge KB-001 # Merge an in-review task and close it
kb task log KB-001 "Added context" # Add a log entry
kb task pause KB-001 # Pause a task (stops automation)
kb task unpause KB-001 # Resume a paused task
kb task attach KB-001 ./error.log # Attach a file to a task
Typical workflow
# 1. Create a task — it lands in triage
kb task create "Add dark mode support"
# 2. Start the dashboard — AI specs the task and begins working
kb dashboard
# 3. Check progress
kb task list
kb task show KB-042
# 4. When it reaches "in-review", review the changes and merge
kb task merge KB-042
Columns
| Column | What happens |
|---|---|
| Triage | Raw idea. AI writes a full task specification. |
| Todo | Specified and ready. Scheduler waits for deps. |
| In Progress | AI is executing the task in a git worktree. |
| In Review | Work is done. Review the changes and merge. |
| Done | Merged and shipped. |
How it works
- Triage processor — An AI agent reads your project, understands the codebase, and turns your rough idea into a detailed specification with steps, file scope, and acceptance criteria.
- Scheduler — Resolves dependency graphs and moves tasks to in-progress when ready. Independent tasks run in parallel.
- Executor — Creates an isolated git worktree and spawns an AI agent to implement the spec step by step. At each step boundary, a separate reviewer agent (different model, read-only) independently checks the plan or code. Verdicts: approve (proceed), revise (fix issues), or rethink (change approach). Review depth scales with task complexity (levels 0–3, assigned during triage).
- You review — Inspect the changes and merge with
kb task merge, or toggle auto-merge in the dashboard.
Standalone binary
Prebuilt standalone binaries are available that require no Node.js runtime. You can also build one yourself with Bun:
bun run build.ts
See the GitHub repository for platform-specific binaries and build instructions.
Full documentation
For architecture details, development setup, and contributor info, see the project README.
License
ISC