Taskplane

Problem

Coding agents need a shared, conflict-safe place to find, claim, and hand off work — more durable than a chat transcript, more agent-native than a human Kanban board. Taskplane is a local-first, agent-first Kanban board and durable work graph built to be that interface, while still giving humans a clean web board for reviewing project state.

Approach

The stack is a TypeScript modular monolith on Node.js 24 and pnpm, with Hono, SQLite, React, and Vite. Its versioned REST API is canonical — the CLI, web app, and a narrow MCP adapter for coding agents all enforce the same domain rules instead of touching SQLite directly. The MVP hierarchy is Project → Epic → Issue, with stable keys, dependency edges, optimistic versions, expiring agent claims, and append-only activity history. Recent commits add agent-first work graphs: curated diamond, research, and software-delivery templates, human-gate decisions for risky actions, and bounded coordination context for parallel agent lanes. main is the release branch; develop is where feature PRs land first, and every quality gate — lint, typecheck, unit, integration, security, build, end-to-end, accessibility — runs as its own CI job.

Outcome

The repo is private. It ships its own Claude Code/Codex plugin and MCP server, around thirty callable tools in total, and the locally installed build is already at v0.1.5, generated within minutes of today's push. As of this week the board also tracks the portfolio you are reading: the agents that maintain this site file their plans and evidence into a Taskplane project rather than into a chat transcript that expires.