A local-first Kanban board that runs your AI coding agents. Every card can launch a Paseo agent in its own git worktree — the board tracks the agent live and moves the card through To Do → In Progress → Review → Done as work happens.
Running several AI coding agents in parallel gets messy fast: which agent is on which task, in which worktree, and which ones are waiting on you? Paseos Kanban turns that into a board. A card is a task is an agent — launch it, watch it progress, answer its questions, review the result, done.
- One agent per card — launch a Paseo coding agent from any card, in a fresh git worktree off any base branch, or attached to an existing worktree.
- Live reconciliation — the board polls the Paseo daemon; a running agent pulls its card into In Progress, a finished one pushes it to Review. Your manual moves are never overridden.
- In-app agent replies — answer an agent's permission prompts and questions without leaving the board.
- Command palette —
⌘Kfor cross-project task search and quick actions. - Kanban you'd expect — drag-and-drop between and within columns, markdown descriptions with images, inline editing, board and list views.
- Per-project scratchpads — freeform rich-text notes next to each board.
- Light & dark themes, English & 中文 — theme follows the system by default.
- Local-first — all data lives in a SQLite database (sql.js/WASM) persisted to your browser's IndexedDB. No server, no account, nothing leaves your machine.
git clone https://github.com/anup-a/paseos-kanban.git
cd paseos-kanban
./start.sh # installs deps on first run, boots the board + bridgeOpen http://localhost:5173. Ctrl-C stops both services.
The board works standalone as a plain Kanban app. For agent features, install
Paseo and run paseo daemon start.
Manual run / PATH install
Manual (two terminals):
npm install
npm run dev # http://localhost:5173 (the board)
npm run bridge # http://127.0.0.1:7677 (Paseo sidecar)
npm run build # type-check + production build
npm test # vitestAdd to PATH — symlink the launcher into a directory on your PATH:
mkdir -p ~/bin
ln -sf "$PWD/start.sh" ~/bin/paseos-kanban
echo 'export PATH="$HOME/bin:$PATH"' >> ~/.zshrc # bash/zsh; fish: fish_add_path ~/binThe board is a browser app and the Paseo daemon exposes no plain REST CRUD, so a tiny
local bridge sidecar (paseo-bridge/server.mjs) is the seam:
browser ──/paseo (Vite proxy)──▶ bridge ──execFile──▶ paseo CLI ──▶ daemon
- Projects in the sidebar come from Paseo — the distinct git repos it has agents in (worktrees resolved to their parent repo), plus any repos you register. A card launches its agent in the selected repo.
- Agent config (provider + model, fetched live from Paseo, and the worktree choice) can be set at task creation — then the card launches in one click.
- Worktrees — create a new one off any base branch, or attach to an existing worktree (including the main working tree).
- Polling — the board polls
paseo lsevery 5s and reconciles agent state onto cards. Per card you can send a follow-up, stop, or archive the agent.
Provider defaults resolve from ~/.paseo/orchestration-preferences.json. Config:
PASEO_BRIDGE_PORT (7677), PASEO_BRIDGE_REPO (repo the agents work on). The bridge
binds to 127.0.0.1 only — don't expose it.
React + Vite + TypeScript. Data access is isolated behind a repository layer, so the SQLite backend can be swapped for a server API without touching the UI.
src/
db/ sql.js init + IndexedDB persistence + React context
domain/ types, fixed columns, search
repositories/ project & task CRUD (the only place SQL lives)
hooks/ useProjects / useTasks bridge repos to React state
components/ Sidebar, Board, Column, TaskCard, CommandPalette, …
paseo-bridge/ localhost sidecar wrapping the paseo CLI + daemon websocket
Card ordering uses fractional position values, so a move or reorder updates a single
row. Design docs for the bigger features live in docs/plans/.