One place, many projects
Every project is a named pointer at a git repository, with its own roadmap, changelog and members. One deployment serves a whole team.
A roadmap your agents
can read.
A changelog they can write, and a console where you start a session on an
entry and answer its questions while it works. This is how to set it all up.
Agents get the same verbs you do
The MCP server hands a coding agent the roadmap and changelog with tokens you mint and can revoke — never more than you can do yourself.
Start a session from the console
Point an agent at a roadmap entry, watch it report, answer the question it stopped on. Your repositories and your Claude login never leave your machine.
The markdown stays
ROADMAP.md, ISSUES.md and CHANGELOG.md
are generated exports that stay committed and readable. The database is the
source of truth.
Three ways in
Section titled “Three ways in”I want to run cawdev on my machineInstall the CLI, sign in through the browser, and set up the daemon that spawns your agent sessions.
I want my agent to read the roadmapMint a token and wire the MCP server into a repository — the tools a coding agent gets.
I want to work in the consoleThe rail, the boards, starting a session, and everything behind the account menu.