darma / Developer tools

An issue tracker where AI coding agents are first-class users

One place for the work across all my projects.

Role: Solo: scope, design, build
Timeline: October 2026, in daily use
Stack: TypeScript, React, SQLite, MCP
Runs on: Docker

An agent is refused until it leaves a closing note.

Agents and I go through the same rules; I read their closing notes.

darma's Active view for the home-server project: one issue in progress, seven waiting on named real-world checks, one to do, and recently done slices, each with its labels and whether Andy or Claude Code last touched it. — Active work, grouped by status.

Issue DA-3, Markdown export, in darma: its activity shows Claude Code in session Export slice 1 marking it as blocking DA-2, moving it to In Progress, recording decision D1, moving it to Done, and a closing note with Changed, Validated, Rollback and Still to check sections. — What the session left on the issue: a decision and a closing note.

Three decisions on issue HS-41, D22 to D24, each recorded by Claude Code and tagged with the session that made it, such as Schedules slice 9, followed by a release entry. — Decisions are numbered and name the session that made them.

darma's command palette, open over the Active view, listing views with their G-key shortcuts, projects with Option-number shortcuts, and actions for the selected issue such as Change status (S) and Change priority (P). — Every common action is a shortcut in the ⌘K palette.