Skip to content

read_agent returns "Failed" after ~2-3 minutes of agent completion #652

Closed

Description

@simonjokanic03

Steps to reproduce

  1. Spawn 3 agents in parallel (background mode)
  2. Wait for all to complete (~2-3 min)
  3. Call read_agent on any completed agent
  4. → Fails with no error message

Expected

Agent results should be readable for the duration of the session.

Actual

Results expire silently after ~2-3 minutes. No error message, just "Failed".

Workaround

Write agent results to persistent files (e.g. .squad/orchestration-log/) immediately after agent completion, before calling read_agent.

Environment

  • Squad v0.9.1
  • Copilot CLI on macOS
  • Models: gpt-5.4 (agents), claude-haiku-4.5 (scribe)

Activity

  1. added
    squadSquad triage inbox — Lead will assign to a member
    bugSomething isn't working
    on Mar 28, 2026
  2. github-actions commented on Mar 28, 2026

    @github-actions
    Contributor

    📋 Assigned to EECOM (Core Dev)

    Issue: #652 — read_agent returns "Failed" after ~2-3 minutes of agent completion

    EECOM will pick this up in the next Copilot session.

    For Copilot coding agent: If enabled, this issue will be worked automatically.
    Otherwise, start a Copilot session and say:
    EECOM, work on issue #652

  3. github-actions commented on Mar 28, 2026

    @github-actions
    Contributor

    🏗️ Squad Triage — Flight (Lead)

    Issue: #652 — read_agent returns "Failed" after ~2-3 minutes of agent completion
    Assigned to: Flight (Lead)
    Reason: No specific domain match — assigned to Lead for further analysis

    @copilot evaluation: No strong capability match — routed to squad member.

    Team roster:

    • Flight (Lead) → label: squad:flight
    • Procedures (Prompt Engineer) → label: squad:procedures
    • EECOM (Core Dev) → label: squad:eecom
    • FIDO (Quality Owner) → label: squad:fido
    • PAO (DevRel) → label: squad:pao
    • CAPCOM (SDK Expert) → label: squad:capcom
    • CONTROL (TypeScript Engineer) → label: squad:control
    • Surgeon (Release Manager) → label: squad:surgeon
    • Booster (CI/CD Engineer) → label: squad:booster
    • GNC (Node.js Runtime) → label: squad:gnc
    • Network (Distribution) → label: squad:network
    • RETRO (Security) → label: squad:retro
    • INCO (CLI UX & Visual Design) → label: squad:inco
    • GUIDO (VS Code Extension) → label: squad:guido
    • Telemetry (Aspire & Observability) → label: squad:telemetry
    • VOX (REPL & Interactive Shell) → label: squad:vox
    • DSKY (TUI Engineer) → label: squad:dsky
    • Sims (E2E Test Engineer) → label: squad:sims
    • Handbook (SDK Usability) → label: squad:handbook
    • Ralph (Work Monitor) → label: squad:ralph
    • @copilot (Coding Agent) → label: squad:copilot

    To reassign, remove the current squad:* label and add the correct one.

  4. diberry commented on Mar 31, 2026

    @diberry
    Contributor

    🔄 Ralph status: PR #684 addresses this. Needs rebase (behind dev). Coordinator prompt change — persist read_agent results immediately.

  5. diberry commented on Mar 31, 2026

    @diberry
    Contributor

    ✅ Status Update — Issue #652

    PR #684 addresses this issue:

    • Rebased against dev, pushed
    • All 21 squad members reviewed and approved
    • Persists agent results immediately after read_agent to prevent data loss

    Ready for merge.

  6. diberry commented on Mar 31, 2026

    @diberry
    Contributor

    🔄 Ralph status update: PR #684 has team review, CI green. Labeled \squad:pr-reviewed. Awaiting Dina review.

  7. added 5 commits that reference this issue on Apr 5, 2026
    b1c2210
    27cc10d
    3f8b3ab
    e89cbbc
    900b4ee
  8. bradygaster commented on Apr 8, 2026

    @bradygaster
    Collaborator

    Closing this one — the read_agent timeout is a Copilot CLI platform behavior that Squad doesn't have control over. Thanks for reporting it though, it helped us understand the boundary. If the platform behavior changes in the future we can revisit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinggo:needs-researchNeeds investigationsquadSquad triage inbox — Lead will assign to a member

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions