The CastCodes → Coven demo loop
The five-step path from an open project to a finished agent session — open, launch, watch, inspect, finish.
2 min read
The demo loop is the canonical end-to-end story for working in Coven through CastCodes. It traces a single piece of intent from the moment you open a project to the moment you explicitly finish the session — merge, PR, archive, or sacrifice. The same loop runs from the coven CLI without CastCodes; this guide just adds the visible cockpit on top.
What the loop is for
Every step makes the agent's work explicit. There is no hidden background work, no implicit completion. Intent enters at step 1; an artifact (merged code, PR, archived log, or deleted session) leaves at step 5.
The five steps
| Step | What you do | Where it happens |
|---|---|---|
| 1. Open project | Pick a project root and confirm the daemon is running. | CastCodes project sidebar + coven daemon status |
| 2. Launch session | Choose a harness, write a prompt, kick it off. | CastCodes agent launcher or coven run <harness> "<prompt>" |
| 3. Watch session | Watch output stream into a visible pane. | CastCodes session pane or coven sessions / coven rejoin |
| 4. Inspect changes | Read the diff, run validation, decide. | CastCodes diff view + your usual test/lint commands |
| 5. Finish loop | Merge, PR, archive, or sacrifice. Explicit either way. | CastCodes pane menu or coven sessions archive / sacrifice |
CLI parity
Every step in the loop has a CLI equivalent in the coven reference. CastCodes is the visible cockpit — useful, not required. If you're scripting the loop in CI or working over SSH, the CLI runs the same daemon and the same harness sessions.
Scaffold in progress
This page set is the first pass at the demo-loop docs. Each step page is a scaffold with the right structure, accurate CLI commands, and TODO markers for the CastCodes-side UI details (screenshots, exact menu labels). Track progress under the community/roadmap-loop group in the Docs Issue Plan.
Last updated on