cockpit

Cockpit

A hosted, API-first project tracker for me and my coding agents, evolved from Mercury’s built-in kanban.

Shipped · live

2026

pythontursovercelpwaagentsrest-apimcp

Why

Mercury’s task board sat inside a custom agent-orchestration platform, with its own runtime and agent tooling. As portable AI coding tools got capable on their own, keeping that platform running just to have a task board stopped making sense.

So I rebuilt the tracking piece on its own: a hosted service with a tool-agnostic HTTP API that any agent runtime can call. It now holds my roadmaps, work, and decisions without depending on Mercury’s runtime.

How it’s built

I built the tracker and took it through a hosted production cutover: Python on Vercel, a canonical Turso database, GitHub owner sign-in, and scoped agent access. The API exposes phases, milestones, tasks, and first-class decisions, with revision checks and an append-only event history.

It is now my working portfolio tracker. Browser, CLI, and local stdio MCP clients use the hosted API; remote OAuth MCP provides read-only access. Vercel publishes Preview from staging and Production from main. The cutover included backup and restore verification, browser acceptance, and production read/write checks before the old local database was archived.

Phase to Milestone to Task hierarchy, with first-class decisions linked to the work they constrain
Revision-guarded edits and idempotent API mutations to protect concurrent agent work
Append-only, per-item audit event log plus a project-wide event feed
Decision workflow: lock with rationale, reopen with a reason, and create linked follow-up work
Installable hosted PWA with GitHub owner sign-in and scoped agent credentials
Self-describing OpenAPI contract so agents discover routes without re-deriving them from docs
Human notes and feedback kept separate from agent notes and feedback on every ticket

Demo

Demo on a throwaway board in hosted production, with my other project names blurred. An agent reads the board from the CLI, a stale write gets a 409, the retry with the current revision moves the card, then the ticket handoff, the roadmap and the iPad view.0:53 runtime

Screenshots

Cockpit cross-project dashboard with burn rate, open load, projection and a seven-day flow sparkline for each of nine projects — Cross-project dashboard: hosted production, project names redacted

Cockpit kanban board with triage, to-do, in-progress, review-ready and decision columns above project burn metrics — Board: work moves through triage to review, with task titles redacted

Cockpit roadmap tree nesting phases, milestones, tasks and locked decisions with progress bars and done states — Roadmap tree: phase to milestone to task, with decisions in line

Cockpit phase line plotting seven release phases with completion, milestone diamonds and a focusing-here marker — Phase line: where active work sits across the release plan

Cockpit decisions view with locked and open decisions, the chosen option highlighted and an owner on each — Decisions: options, the locked choice and its owner, with content redacted

Cockpit health page listing server status, code version, runtime, uptime and project count with the database address redacted — Health: the deployed revision and runtime, inspectable in production

Cockpit dashboard on a tablet in portrait with the navigation collapsed to icons — Tablet: the same dashboard with a collapsed icon rail

Cockpit kanban board on a tablet in portrait with scrolling columns — Tablet: board columns scroll within the viewport

Cockpit phase line on a tablet in portrait — Tablet: phase line

Cockpit decisions list on a tablet in portrait — Tablet: decision log

Links

Hosted production for my own portfolio, verified September 2026. Vercel and Turso are canonical; the former local SQLite board is an archive. Used by me and my agents, with no claim of external customer adoption.

Back to the shelfBrowse all projects