Triage incoming issues
Triage needs the graph engine. Without it, q:intake issues wait untouched.
-
In
~/.cambium/config.json:{"engine": "graph","phases": { "dispatch": { "cap": 1 } }}capis how many triage workers may run at once.0turns triage off. -
Restart, since
engineis read only at start:Terminal window oakgreen restart cambium -
File work with the label
q:intake. Issues from mycelium already carry it.
Triage one issue now
Section titled “Triage one issue now”cambium run dispatch --issue 42 --repo owner/nameRuns a triage worker in the foreground, whatever the cap, and applies its verdict.
Make agents file issues the same way
Section titled “Make agents file issues the same way”oakgreen setup, run from a clone, writes docs/agents/triage-labels.md and a pointer to it in CLAUDE.md or AGENTS.md. Agent skills that file issues read it and use q:intake. If the guide exists but does not name q:intake, oakgreen doctor says so; replace it.
Tune deferral
Section titled “Tune deferral”Key under phases.dispatch |
Default | Controls |
|---|---|---|
deferHours |
6 | wait before re-checking a deferred issue |
maxDefers |
8 | deferrals before it goes to q:human |
maxAttempts |
3 | failed triage attempts before q:human |
wallClockMinutes |
15 | time limit per triage worker |
Verdicts and where each one sends an issue: cambium graphs. Why triage defers instead of asking a person: Humans in the loop.