Repository navigation
OpenChamber dispatch v1.1: admission control, hand-backs, stall nudges, harvesting, Workhorse-first routing #1187
Description
What
v1.1 of the OpenChamber dispatch system (design:
files/openchamber-dispatch-babysitter-design-2026-10-26.md): turn
the report-only babysitter into the working dispatcher + babysitter.
Scope
- Dispatcher: claims queue tasks whose packet carries
executor: openchamber(larger code work: effort/m+l, session-shaped
per triage), admits against (a) location capacity and (b) the POOL
MAP measurement gate for the routed pool (fresh quota read; ≥85% of
window = no new heavy work). Creates the session in a per-task
worktree on branchqueue/<task-id>-<issue>-<slug>and records the
binding (session id, location, pool/route, started-at) on the task. - Hand-back: no slot or no headroom → park the task with reason
classexecutor-saturatedand note it on the issue. Saturation is
reported, never a silent backlog; a Claude lane can still claim the
task if urgent. - Babysitter actions: stall nudge (one message into a session idle
20 min while claiming work: checkpoint/continue/state blocker; max
2, then escalate to the monitor tracker); wall handling (quota stop =
park blocked with the wall named, never a PAYG fallback); harvesting
(session done → verify against GitHub → complete/park/block the task
with labels synced and an agent-note on the issue). - Routing policy as config: Fast / Workhorse (default) / Frontier
tiers per the design; escalation to Frontier requires recorded
evidence (failed Workhorse attempt or design-shaped triage); the
split pattern (Frontier plan → Workhorse/Fast implementation) is a
first-class dispatch shape. Routing ledger entries land in the
babysitter report.
Acceptance criteria
- A task marked
executor: openchamberflows queue → session →
PR → verified terminal queue state with no Claude lane involved. - With the location at capacity, the next candidate is handed back
(parked,executor-saturated, issue noted) within one round. - A deliberately stalled session receives exactly one nudge, and a
second stall escalates instead of nudging forever. - Every Frontier session in a week of reports has a recorded
escalation reason; Workhorse-first is the observed default. - No dispatched task evaporates: every binding ends in a terminal
state or a named hand-back (monitor Duty 1 stays clean).
Depends on: babysitter v1 (report-only) and the session-API + quota
attribution pilots. Filed by Muse (operator) 2026-10-26.
Metadata
Metadata
Assignees
Labels
Infrastructure, deployment, and operationsLarge: multi-day or open-ended; expect staged check-insNew feature or capability requestFully doable remotely: design, config, code, cloudImportant and time-sensitiveQueue task is parked (waiting on CI, time, or an event)Filed by the new-issue-creator jobDeliberately paused with a recorded resume conditionQueue packet kind: verify, reproduce, and route this item
Activity
developing-today commentedon Oct 27, 2026
CODE-323
112 remaining items
dezren39 commentedon Nov 3, 2026
🤖 Agent note · triaged (ruling applied; no natural occurrence yet — re-parked on the standing check)
State verified fresh:
Natural-occurrence check — not exercised yet, with the evidence limit stated honestly:
gh search issues 'executor-saturated'returns only the dispatch design/tracking issues, no occurrence record).~/workspace/goals/keep-the-four-repos-healthy/carries onlydesigns/; nofiles/*dispatch*or babysitter report files), so criterion 3 has no observable event either.Next natural checkpoint: the next dispatch round that hits location capacity (it will park a task with reason class
executor-saturatedand note the issue) or the next babysitter report that records a stall nudge. Whichever appears first is the evidence that closes the matching criterion; the issue closes when both standing checks have an occurrence (or when a later ruling drops them).Labels: removed
user/escalated/status/blocked/queue/blocked(the decision has been given; nothing is blocked on Drew) and setqueue/parked+status/parkedto reflect "waiting on a natural occurrence".dezren39 commentedon Nov 3, 2026
agent-note:v1
state: triaged (coverage pass)
Coverage pass 2026-11-03: reviewed in the fleet-wide per-issue pass (drift / overlap / already-handled / stale / blockers / ordering). Verdict: still live; queued in repo-health-code-pilot as triage at priority 50 (priority/high). If this is already handled at current main, the triage closes it with evidence; if it needs splitting, the triage files the split.
Found via: coverage pass 2026-11-03
dezren39 commentedon Nov 4, 2026
🤖 Agent note · triaged
gh search issues 'executor-saturated'returns only design/tracking issues — OpenChamber dispatch v1.1: admission control, hand-backs, stall nudges, harvesting, Workhorse-first routing #1187, Dispatcher v1 live: scheduled launches of OpenCode/OpenChamber sessions for queued issues #1337, epic(openchamber): session dispatch + babysitting — OpenChamber as the fleet's workhorse executor #1234, rollout(fleet): OpenCode-half pilot on the code queue + extension to opencode/openchamber/nix (OpenCode-half step 5) #1658 — no occurrence record), no stall-nudge occurrence is recorded, and the dispatcher dependency Dispatcher v1 live: scheduled launches of OpenCode/OpenChamber sessions for queued issues #1337 ("Dispatcher v1 live") is still OPEN, so the machinery that would produce natural occurrences is not fully rolled out. Criterion 1 (harvesting) remains verified from the earlier lanes. Verdict: issue OpenChamber dispatch v1.1: admission control, hand-backs, stall nudges, harvesting, Workhorse-first routing #1187 is correctly parked on the standing check; no fix path to scope and nothing to split — this coverage task duplicates task 7472's follow-up and completes as triaged with no new follow-up task (a new task would just re-park identically).executor-saturatedwith an issue note, or a babysitter report recording a stall nudge + escalation), or when a later ruling drops them. Next natural checkpoint: Dispatcher v1 live: scheduled launches of OpenCode/OpenChamber sessions for queued issues #1337 landing.