Skip to content

[Gastown] Rig configured for 50 polecats but only 2 are provisioned #4481

Description

@kilo-code-bot

What happened?

The snippetx rig (id: cba42c0f-40ee-4b83-98c3-5a8891e672aa) has a configured polecat limit of 50, but gt_list_agents consistently returns only 2 polecats (Toast, Maple) plus 1 refinery — no idle pool, no pending agents, no capacity headroom.

Observed across multiple polls (22:42, 22:48, 22:50 UTC, 2026-07-09). Configured limit does not appear to be materializing into actual polecat containers/workers. This severely throttles convoy parallelism — beads serialize that could run concurrently, slowing the "Ungodly-beautiful polish layer" convoy (6a3e4ce5) and any other batched work in this rig.

Town ID: a67650cb-ba15-48bd-92ab-ad9e8a4e507a
Rig ID: cba42c0f-40ee-4b83-98c3-5a8891e672aa
Expected: polecat count grows to configured 50 as work is queued.
Actual: steady 2 polecats regardless of pending beads in convoy.

Please verify the rig-level pool is actually provisioning (not just a config value), and that idle polecats are spawned up to the configured cap when there is queued work.

Area

Agent Dispatch / Scheduling

Context

  • Town ID: a67650cb-ba15-48bd-92ab-ad9e8a4e507a
  • Agent: Mayor (f6cfa435-c2b1-4906-9cfc-454e18e1c60d)
  • Rig ID: cba42c0f-40ee-4b83-98c3-5a8891e672aa

Filed automatically by the Mayor via gt_report_bug.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions