Skip to content

Coordinator loses all agent context after conversation compaction #653

Closed

Description

@simonjokanic03

Steps to reproduce

  1. Run a multi-phase task (analyse → implement → test) with 3+ agent spawns
  2. Context compaction triggers automatically ("Compacting conversation history...")
  3. Ask coordinator "what happened?" or "continue"

Expected

Coordinator should maintain awareness of completed agent work after compaction.

Actual

Coordinator responds: "No agent-made file changes or orchestration logs were found" — has no memory of any agents it spawned or their results.

Workaround

Coordinator writes session state to .squad/session-state.md after every agent completion. On compaction, re-reads this file to recover context.

Environment

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

Activity

  1. github-actions commented on Mar 28, 2026

    @github-actions
    Contributor

    📋 Assigned to Flight (Lead)

    Issue: #653 — Coordinator loses all agent context after conversation compaction

    Flight 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:
    Flight, work on issue #653

  2. github-actions commented on Mar 28, 2026

    @github-actions
    Contributor

    📋 Assigned to EECOM (Core Dev)

    Issue: #653 — Coordinator loses all agent context after conversation compaction

    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 #653

  3. github-actions commented on Mar 28, 2026

    @github-actions
    Contributor

    🏗️ Squad Triage — Flight (Lead)

    Issue: #653 — Coordinator loses all agent context after conversation compaction
    Assigned to: FIDO (Quality Owner)
    Reason: Issue relates to testing/quality work

    @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 #682 addresses this. Needs rebase (behind dev). Adds compaction recovery via session-state.md.

  5. self-assigned this
    on Mar 31, 2026
  6. diberry commented on Mar 31, 2026

    @diberry
    Contributor

    ✅ Status Update — Issue #653

    PR #682 addresses this issue:

    • Rebased against dev, pushed
    • All 21 squad members reviewed and approved
    • Adds compaction recovery via session-state.md

    Ready for merge.

  7. diberry commented on Mar 31, 2026

    @diberry
    Contributor

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

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

    @bradygaster
    Collaborator

    Closing — this is caused by Copilot CLI's automatic conversation compaction, which is outside Squad's control. Appreciate the detailed report! If the platform adds hooks for compaction events we'd love to revisit.

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

Metadata

Metadata

Assignees

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