Multi-project ticket board for tk. Reads .tickets/ directories from local repos. Kanban and list views. Vim bindings. Full markdown. Read-write.
AI coding agents generate tickets. pi-stuff routes all agent coordination through tk — task delegation, progress tracking, inter-agent handoff. Tickets accumulate in .tickets/ directories across every project.
Ramboard gives you one board to see them all. Point it at your repos, get a Linear-style UI over plain markdown files. No database, no sync — the filesystem is the source of truth.
bun installbun run devConfigure which repos to watch in ramboard.config.ts.
| Layer | Choice |
|---|---|
| Runtime | Bun |
| Server | Bun.serve() — no frameworks |
| Frontend | React 19 + Vite + Tailwind v4 |
| State | Zustand |
| DnD | @dnd-kit |
| UI primitives | @base-ui-components/react (headless) |
| Command palette | cmdk |
| Icons | @phosphor-icons/react |
| Fonts | Geist + Geist Mono |
| Animation | CSS first, anime.js for spring physics |
- Board view — kanban columns by status, drag cards between columns, drag to reorder columns
- List view — sortable table with inline status and priority
- Filters — status, priority, tags, type, assignee, project
- Search — fuzzy filter across all tickets
- Vim bindings —
j/knavigation,Enterto open,Escto deselect - Command palette —
Cmd+Kfor quick actions - Multi-select — bulk status and priority changes
- Full-page detail — markdown rendering with GFM support
- Multi-project — one board across all your repos
pi-stuff extensions use tk tickets as the coordination layer between agents:
- teams spawns parallel workers, each claiming tickets from a shared queue
- todos-tk creates, lists, and completes tickets from inside pi sessions
- Oracle & Delphi write research findings as tickets
Ramboard renders these same tickets as a visual board. Agents write .tickets/ files; you drag them across columns.
MIT