The Views
Board, List, Documentation and Graph over the same files, plus the ticket timeline and Settings.
Every view reads the same .lovelace/ files through the same index. None of them
is a separate store: close the app and the whole project is still there, in plain
text.
Board
Tickets grouped by status, one column per status in schema.yaml order. Drag a
card to any column to change its status. Card order within a column is yours and
persists in board-order.yaml. While an agent works a ticket, its card carries a
live ring and an elapsed timer.
List
The same tickets as a dense table, grouped by status. Filter by type, assignee or any custom enum field; select rows for bulk status moves.
Ticket detail
Open a ticket and every field renders from your schema definitions at runtime, so custom fields appear automatically with the right input per type. The body is a block editor that compiles to Markdown with round-trip fidelity. Comments, session records and commits carrying the ticket ID sit together on one timeline.
Documentation
The documentation/ tree as a navigable hierarchy. A directory’s index.md is
its landing page; documents past their review_by date are badged stale; mermaid
fences render as diagrams.
Graph
The wiki-link graph across your documents. Drag nodes to arrange them; positions are saved machine-locally, never committed.
Settings
Ticket types, fields, statuses, priorities and actors, edited through forms generated from the same schema and written back through core validation. The Integrations section shows whether the Claude Code, OpenCode, and Codex assets are installed; the project digest and session history are viewable here too.
Beyond the views: search covers titles and bodies across tickets, documents and sessions, and you can open several projects at once, one per tab.