Repository navigation
Action: reduce queue lanes — one lane each for OpenCode and OpenChamber #2133
Description
Disable repo-queue-worker-shift-opencode-b and repo-queue-worker-shift-openchamber-b (Drew approved 2026-10-29). One lane each remains for opencode and openchamber; code keeps four lanes, nix keeps one.
Why: those queues are shallow (41 and 27 issues filed in the check-in #5 window vs code's 346) and the B lanes were the #2 and #12 token spenders in the fleet (228M and 122M input per ~15h). Reversible: re-enable if queue latency suffers. Expected saving ~570M input/day at current per-run costs, minus work migrating to the A lanes and dispatched sessions.
Done when: both jobs show enabled=false, the change is noted in the fleet log, and the next two token check-ins confirm no completion-rate collapse on those queues.
Activity
developing-today commentedon Oct 29, 2026
CODE-1031
dezren39 commentedon Oct 29, 2026
EXECUTED 2026-10-29 ~01:0x CDT (Drew approved the full Batch 3 set at 00:55): repo-queue-worker-shift-opencode-b and repo-queue-worker-shift-openchamber-b are both enabled=false, verified via scheduler status (no next run scheduled for either). One opencode-b shift already in flight at disable time will finish its current run and then stop. One lane each remains for opencode and openchamber; code keeps four lanes, nix one. Watch item: the next two daily token check-ins confirm no completion-rate collapse on those queues (per-lane economics section). Closing as done.