These docs are written for contributors and future coding agents. They explain how Adadex is put together, where state lives, and how local terminal agents are coordinated.
Adadex has three main layers:
- agent-facing files in
.adadex/coordinations/<coordination-id>/, which hold context, todos, and handoff notes - runtime state under
~/.adadex/projects/<project-id>/state/, which tracks terminals, UI state, transcripts, and app metadata - live sessions in the API process, where WebSocket connections are attached to PTY-backed Codex CLI terminals
- Installation
- Quickstart
- Mental Model explains the boundaries between coordinations, terminals, worktrees, and runtime state
- Coordination explains the file-backed context model and how Deck reads it
- Runtime and API explains terminal lifecycle, WebSockets, hooks, persistence, and restart behavior
- Working With Todos explains how checkbox lines become progress and worker inputs
- Orchestrating Child Agents explains parent/worker spawning, shared mode, and worktree mode
- Inter-Agent Messaging explains the in-memory channel queue and delivery rules