What happened?
Polecat agents (Toast and Maple) in rig 2e9c840e-c2f8-4e97-9065-3963cd5587b2 consistently fail triage request resolution with: "Permission error: gt_triage_resolve requires triage agent role but current role is polecat." This has triggered 4+ duplicate escalation beads (0629ea33, 65a00961, 27a9ee8a, 7e1dcf48). The rig has no .kilo/agent/*.md config files in its browse directory, and the polecat agent definition does not include triage permissions. Expected behavior: either polecats should handle triage or prevent escalated triage-request beads from being routed to agents without the required role. SFW—no secrets or credentials involved.
Area
Agent Dispatch / Scheduling
Context
- Town ID: 2cda427a-6017-44cf-a059-48c96a1425f6
- Agent: Mayor (0ed7df0c-48f5-48c2-8b3e-e36076c4d23b)
- Rig ID: 2e9c840e-c2f8-4e97-9065-3963cd5587b2
Filed automatically by the Mayor via gt_report_bug.
What happened?
Polecat agents (Toast and Maple) in rig 2e9c840e-c2f8-4e97-9065-3963cd5587b2 consistently fail triage request resolution with: "Permission error: gt_triage_resolve requires triage agent role but current role is polecat." This has triggered 4+ duplicate escalation beads (0629ea33, 65a00961, 27a9ee8a, 7e1dcf48). The rig has no .kilo/agent/*.md config files in its browse directory, and the polecat agent definition does not include triage permissions. Expected behavior: either polecats should handle triage or prevent escalated triage-request beads from being routed to agents without the required role. SFW—no secrets or credentials involved.
Area
Agent Dispatch / Scheduling
Context
Filed automatically by the Mayor via
gt_report_bug.