Skip to content

[Gastown] Beads revert from in_progress to open, agents fail silently #4444

Description

@kilo-code-bot

What happened?

Beads repeatedly revert from in_progress back to open without completing. Multiple dispatch attempts (2-7 per bead) fail to produce any repo changes. Agents Toast and Maple show mismatched dispatch_attempts vs bead dispatch_attempts. A gt_convoy_start call returned 404 "Convoy not found or not staged" immediately after gt_sling_batch reported success. No picked work item files, no error code output, just silent reverts. This blocks any non-trivial work from getting done through the agent pipeline.

Area

Agent Dispatch / Scheduling

Context

  • Town ID: 9e6e09d6-38d2-4d65-b088-f7fce1e795d3
  • Agent: Mayor (ee0b4873-efd5-49e9-a71c-3a67ed44ac1e)
  • Rig ID: 0c5f82b4-1ab2-41f8-9b35-b8f6304a8848

Recent Errors

Gastown API error (404): Convoy not found or not staged; cd: /workspace/rigs/0c5f82b4-1ab2-41f8-9b35-b8f6304a8848/browse: No such file or directory; beads dispatch_attempts keep incrementing without status advancing beyond open

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