Skip to content

Compaction killed the session #2500

Open
Open

Description

@laeubi

Describe the bug

While a task running, I see this in the logs:

● Compaction completed
│ A new checkpoint has been added to your session.
└ Use /session checkpoints 3 to view the compaction summary.

◐ The user hasn't sent a new message yet - the system just loaded the context summary. Let me wait for the user's actual question/request.
...
Session restored. Here's the current state:

And then it just stopped and asking

What would you like to do next?

And I need to repeat my request!

Affected version

No response

Steps to reproduce the behavior

No response

Expected behavior

No response

Additional context

No response

Activity

  1. added theissue type on Apr 3, 2026
  2. added
    area:context-memoryContext window, memory, compaction, checkpoints, and instruction loading
    on Apr 6, 2026
  3. added
    area:sessionsSession management, resume, history, session picker, and session state
    on Apr 6, 2026
  4. laeubi commented on Apr 18, 2026

    @laeubi
    Author

    This now happens again with the latest version

    ● Read app.js
      │ src/main/resources/web/method/js/app.js
      └ L1403:1510 (107 lines read)
    
    ● Compacting conversation history...
    
    ● Good. Now let me also store the key findings for future reference:
    
    ● Memory stored ...
      └ …
    
    ● Compaction completed 
      │ A new checkpoint has been added to your session.
      └ Use /session checkpoints 3 to view the compaction summary.
    
    ◐ The user's last message was about doing a deep check for the Config>Modules section. Let me read the current state of the code and understand what needs to be done. Let me look at the plan and the current state of the codebase.
    
      Let me read the plan.md and the current app.js to understand where we are.
    

    stupid enough this happened right before the session was about to be completed so copilot is doing another round of thinking and checks just to finally come to the conclusion:

    ● All the Modules fixes from the previous session are already in place. The changes are:
    

    so it seems to think it is a complete new session now.

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

    area:context-memoryContext window, memory, compaction, checkpoints, and instruction loadingarea:sessionsSession management, resume, history, session picker, and session state

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions