Skip to content

epic(openchamber): session dispatch + babysitting — OpenChamber as the fleet's workhorse executor #1234

Open
6 of 10 issues completed

Description

@dezren39

Session dispatch + babysitting (OpenChamber program)

Purpose

Move the fleet's larger code work off Claude cron shifts — whose every turn re-buys a large context — onto OpenChamber-hosted OpenCode sessions running on plan pools, watched by ONE babysitter worker instead of one worker per issue. Design record: openchamber-dispatch-babysitter-design-2026-10-26.md (keep-the-four-repos-healthy goal workspace, files/).

Scope

  • Locations abstraction: a session executor is a location (kind: openchamber | opencode-server | openclaw | codex-aster) with an adapter + capacity, so more OpenChamber machines, an OpenClaw gateway, or a Codex .aster route plug in without changing the babysitter loop. First location: the laptop's OpenChamber.
  • Dispatcher with admission control: hands queue tasks marked executor: openchamber to sessions only when a slot is free and the routed pool passes the quota measurement gate; otherwise hands the task back (parked executor-saturated, noted on the issue) — never a silent backlog.
  • One babysitter: rounds over every bound session — progress verdicts, one stall nudge then escalation, quota walls as named parks, harvesting finished sessions into verified terminal queue states. Reports quota per pool and a routing ledger (pool used per session, escalations, burn per landed task).
  • Routing, Workhorse-first: Fast / Workhorse (default) / Frontier tiers per the POOL MAP; Frontier only on evidence or for the design half of a split (Frontier plans, Workhorse/Fast implements).
  • OpenClaw long-term path: babysitting-by-comment — the monitor's routine issue comment is the control channel; OpenClaw reports and obeys in-thread. Reached via pilot → mirror mode → handover (see the design record).

Execution mode

Online. Builds land as fleet job bodies, helper tooling, and Supabase/queue conventions under the fleet goal; session work happens on the laptop location.

Dependencies

Acceptance

  • The babysitter runs as one worker regardless of session count; every dispatched task ends in a verified terminal state or a named hand-back.
  • A week of babysitter reports shows per pool: sessions run, landed rate, Frontier escalations with reasons, quota burn per landed task.
  • OpenClaw comment-loop pilot produces a go/no-go for mirror mode with the comment format pinned if go.

Filed by Muse (operator) 2026-10-26 under Drew's direction (design + issues filed the same evening; this epic groups them for the roadmap and PM dashboard).

Activity

  1. added
    priority/highImportant and time-sensitive
    area/infraInfrastructure, deployment, and operations
    epicMeta-issue grouping multiple items (org Project Type=Epic)
    on Oct 27, 2026
  2. developing-today commented on Oct 27, 2026

    @developing-today
    Contributor
  3. added
    effort/lLarge: multi-day or open-ended; expect staged check-ins
    meta/enrichedIntake review done: acceptance criteria, links, and normalized labels added
    on Oct 27, 2026
  4. 9 remaining items

  5. added
    source/creatorFiled by the new-issue-creator job
    task/triageQueue packet kind: verify, reproduce, and route this item
    on Nov 3, 2026
  6. developing-today commented on Nov 3, 2026

    @developing-today
    Contributor

    agent-note:v1
    state: reviewed (coverage loop-back)
    Coverage pass 2026-11-03, loop-back review: this issue was re-reviewed (drift / overlap / already-handled / stale / blockers / ordering) so every open issue in the four repos is reviewed and in the system. Verdict: still live; in the system as task 7221 (triage, queued, priority 50) in repo-health-code-pilot. Labels audited and synced. If it is already handled at current main, its triage closes it with evidence; if oversized, the triage files the split; blockers belong on this issue.
    Found via: coverage loop-back 2026-11-03

  7. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · picked up

  8. added
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 3, 2026
  9. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · triaged — CONFIRMED live umbrella; active delivery remains owned by the decomposed child issues

  10. added
    status/triagedTriaged and routed (see agent note)
    and removed
    task/triageQueue packet kind: verify, reproduce, and route this item
    queue/claimedQueue worker lifecycle state
    work/assignedQueue worker lifecycle state
    on Nov 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area/infraInfrastructure, deployment, and operationseffort/lLarge: multi-day or open-ended; expect staged check-insepicMeta-issue grouping multiple items (org Project Type=Epic)meta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedmode/onlineFully doable remotely: design, config, code, cloudpriority/highImportant and time-sensitivesource/creatorFiled by the new-issue-creator jobstatus/triagedTriaged and routed (see agent note)

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions