communication-protocol

Goal

• Keep build chat clear and predictable.
• Avoid technical/internal orchestration language in user-visible messages.
• Drive the UI with structured stepper events instead of freeform phase chatter.
• Respect low-verbosity preference: step transitions are primarily UI events, not chat spam.

Roles

• Frontend: renders chat + timeline from backend events.
• Backend (Tidy): starts build session, runs OpenClaw turns, stores events.
• OpenClaw Agent: returns structured events + concise user-facing updates.

Session Inputs (from backend to OpenClaw)

Environment variables passed to each turn: