Daily driver loop

The recommended local workflow for developing and operating Flock.

Loop

flock multiplexer ensure  →  flock dashboard  →  flock run  →  flock evolve  →  ./scripts/verify.sh

1. Multiplexer — flock multiplexer ensure starts the in-tree PTY server (~/.config/flock/flock.sock).
2. Dashboard — flock dashboard opens the ratatui control tower (agents, pressure, pane tree). Writes ~/.config/flock/statusline.json for MCP observability.
3. Run — flock run --goal "…" --plugin gridworld (scheduler) or --rlm (verify/act loop with mux pane topology).
4. Evolve — flock evolve --episodes 16 --workspace .flock/episodes mutates topology from episode corpus.
5. Verify — ./scripts/verify.sh before every PR (fmt, clippy, hack, tests, smoke benches, dashboard + socket e2e).

Headless CI parity

CI runs the same smoke surface without a TTY:

cargo test -p flock-dashboard --test integration
cargo test -p flock-multiplexer --test socket_integration
flock run --goal "reach target" --plugin gridworld --rlm

Remote / SSH

flock remote --goal "reach target" --plugin gridworld
flock herd attach --session my-work

See Dashboard and Verify.