Using Cards

This page is for people running a project on Cards — solo developers, small teams, and anyone wiring agents into the loop. It covers how a project runs day to day, which setup fits your situation, how coordination works around git (PRs, notifications, changelogs, conflicts), and then documents every operation in detail. Everything goes through the same service layer, so validation, versioning, and events behave identically whether you use the CLI, the HTTP API, the MCP tools, the web UI, or the terminal UI — the examples below show the first three, and the responses are real output from the bundled demo workspace.

Terminal UI: a bare cards on a terminal opens the TUI against the resolved workspace (quit with q; ? for keys). It's serverless and in-process — in scripts and pipes (`cards