What happened?
Currently each rig gets exactly 1 refinery agent for code review. For repos with active convoys and multiple polecats working in parallel, this creates a single-point bottleneck — all beads must wait for one reviewer.
Requested:
- Allow rig-level configuration for number of refinery agents (e.g., 2-3 reviewers per rig)
- Allow per-convoy or per-bead reviewer count override
- When multiple refineries are available, distribute review work across them (load balancing)
Impact: In our current convoy (12 beads, 5 polecats), 3 beads are queued for review but only 1 refinery exists. The polecats finish work faster than the single refinery can review, creating a pipeline stall. With 2-3 refineries, review throughput would match development throughput.
Rig: 33c84cb1-092d-48f1-807e-39b0db8f5692
Town: d855f9e8-97d5-4994-930a-568d4cba061f
Area
Agent Dispatch / Scheduling
Context
- Town ID: d855f9e8-97d5-4994-930a-568d4cba061f
- Agent: Mayor (e39e3c70-2a86-43cf-a456-bd721ac5f9e7)
- Rig ID: 33c84cb1-092d-48f1-807e-39b0db8f5692
Filed automatically by the Mayor via gt_report_bug.
What happened?
Currently each rig gets exactly 1 refinery agent for code review. For repos with active convoys and multiple polecats working in parallel, this creates a single-point bottleneck — all beads must wait for one reviewer.
Requested:
Impact: In our current convoy (12 beads, 5 polecats), 3 beads are queued for review but only 1 refinery exists. The polecats finish work faster than the single refinery can review, creating a pipeline stall. With 2-3 refineries, review throughput would match development throughput.
Rig: 33c84cb1-092d-48f1-807e-39b0db8f5692
Town: d855f9e8-97d5-4994-930a-568d4cba061f
Area
Agent Dispatch / Scheduling
Context
Filed automatically by the Mayor via
gt_report_bug.