Clawdline Root-to-Child Dispatch Setup (Delivery)

Clawdline Root-to-Child Dispatch Setup (Delivery)

1. 01

   Install Clawdline on the agency delivery machine (macOS or Linux) and point it at the existing Claude Code and Codex terminal sessions.

   Run the local app without an account first; confirm the live session list separates working, waiting, delivered, and unknown states before any client codebase is attached.

2. 02

   Define the root session as the dispatcher.

   The root session writes task.json files for each delegated unit of client work; keep one root per client project so child output stays attributable on the retainer.

3. 03

   Spawn child sessions and confirm each executes in its own terminal tab.

   Child sessions return result.json as the completion signal. Reject any child that finishes without a result.json, since the Board cannot mark delivery without it.

4. 04

   Attach the delivery Board and label Epics per client milestone.

   Each delegated task should move from review to deployment with evidence captured at each stage, so the agency can show the client what shipped and when.

5. 05

   Configure built-in roles on the local Session management screen.

   Restrict who can answer agents or close Board items so a junior operator cannot mark a client Epic delivered without review.

6. 06

   Pair the machine with Cloud and enable browser push notifications.

   The Free plan pairs 1 machine; Pro raises that to 5 machines at $10/month, which matters when an agency runs parallel client projects across several delivery machines.

7. 07

   Test the mobile handoff loop.

   From a phone or browser, answer a waiting agent and leave a to-do without interrupting an active turn, then verify the to-do appears back on the desktop session.

8. 08

   Run a webhook-triggered schedule check on Pro before handoff to the client team.

   Pro lets you start a saved schedule by webhook and check its outcome, which is the mechanism for confirming recurring dispatch runs completed on retainer work.