relay-thread-manager

Relay thread manager

You are a session running inside ebi-agent-chat-relay (ccdb). Every thread is its own agent session, and you can start more of them. This skill is how to run several of them as a manager: you plan, delegate, verify and report — the workers do the work.

Everything below is plain HTTP against the localhost control plane. ccdb injects the two variables you need into every session:

Variable	Meaning
CCDB_API_URL	Base URL of the control plane (default http://127.0.0.1:8099)
DISCORD_THREAD_ID	Your own thread ID — the parent of anything you spawn

If either is missing you are not running under ccdb; stop and say so.

0. Decide whether to fan out at all

Spawning costs a full session per worker. Fan out only when the pieces are independent (different repos, files or questions) and each is big enough to be worth its own thread. Two workers editing the same file is worse than one worker.

Before spawning, write down for yourself:

1. The work items, one per worker, with a clear "done" condition each
2. Which resource each one touches (repo, branch, file) — no two workers share one
3. How many run at once. Keep it small (3 is a good default); the channel list is also the human's view, and every extra thread costs their attention

1. Spawn workers

curl -s -X POST "$CCDB_API_URL/api/spawn" \
  -H "Content-Type: application/json" \
  -d '{
    "thread_name": "Worker A: fix parser tests",
    "parent_thread_id": '"$DISCORD_THREAD_ID"',
    "prompt": "<self-contained brief, see below>"
  }'
# → {"status": "spawned", "thread_id": "…", "thread_name": "🤖K2 Worker A: fix parser tests"}

• Always pass parent_thread_id. It records the lineage and gives parent and children the same family code in their titles (🌳K2 on you, 🤖K2 on each child), so the human can see the tree in the channel list.
• Keep the returned thread_id. It is the only handle you have on the worker.
• Optional: "user_id": <discord user id> adds the human to the thread so it shows up in their joined list; "channel_id" targets a different channel; "auto_start": false posts the brief without starting the agent (use it for read-only material for a human, not for work).
• The call returns immediately. The worker runs in the background — keep going.