hey-dave diagrams
How D.A.V.E. is built: the system, a turn, the permission gate, delegation, persistence and the stage roadmap. Each page is interactive: pan, zoom, search, and guided views.
Design
System mapCLI and UI, the runtime, AgentLoop, gate and sessions, providers, tools, extensions, subagents and the vault.
docs/architecture.md
The background daemonOne daemon per user: it supervises session hosts, owns the Telegram bot and a loopback API, and comes back after a reboot as a user service.spec 14 · stages 86–91
Where state is written and readConfig transactions, session JSONL and replay, checkpoints for /rewind, and the vault through DaveState, synced through Google Drive.specs 01, 06, 07
Workflows
One turn of the agent loopPrepare, compact, stream a provider round, gate each tool call, run tools, repeat or finish.
core/loop.py · spec 03
Permission gate evaluation orderHard denies, deny rules, plan and confine, always-ask, grants and reads, and the card.core/permissions.py · spec 03
Slash command resolutionRegistry lookup, hidden aliases, help and usage, remote and busy gates, then the handler or file prompt.skills/commands.py · spec 04
Delegating a chargedelegate, the write-grant card, SubagentRunner, the child loop and the report drained into the next turn.core/subagent.py · spec 09
Plan
Core redesign: stages 66–74 plannedTask records, interruption and return, time, portable memory, context controls, General work, retained integrations and fresh rollout.
specs 11–12 · docs/plan/core-redesign-stages.md
Build roadmap: stages 01–110The stages grouped in build order, from the v1 foundation through the Task redesign and the background daemon to the latest product follow-ups.docs/plan/00-overview.md
Claude and Devin over ACP plannedStage 27: external agents as roster workers, with your rules and your own sign-in.docs/plan/stage-27-acp-agents.md