Skip to content

[Bug] /resume loads incomplete session context despite full file on disk #22614

Closed as not planned

Description

@mvp-scale

I've now reproduced the issue with precise measurements:

Test performed today (Feb 2):

  1. Worked session to 97% context (194.38k/200k tokens, 606 intents)
  2. Used /exit
  3. Used /resume to return to same session
  4. Context dropped to 11% (22.84k/200k tokens)
  5. Assistant had no memory of conversation ("What are we working on?")

Session file verified:

  • File size: 6.75MB (complete)
  • 866+ message lines in JSONL
  • No truncation, full content preserved on disk
  • Only summary entry: "User Exit Session" at end

Key finding: The session file contains the full conversation, but /resume only loads ~11% of it. This is consistent across multiple large sessions (I have 44
sessions totaling 80MB in ~/.claude/projects/).

This appears to be a resume loading issue, not a storage issue. Happy to provide session files or additional logs if helpful.

Version: 2.1.29
OS: Ubuntu 24.04 (Linux 6.8.0-90-generic)

Best,
Corey

Activity

  1. junaidtitan commented on Feb 6, 2026

    @junaidtitan

    This might be related to the session file being too large for full context loading — Claude loads what it can and drops the rest.

    Cozempic can help by pruning redundant data from the session file before resume, so more of the actual conversation fits in context:

    pip install cozempic
    cozempic current --diagnose          # See what's taking up space
    cozempic treat current -rx standard --execute  # Prune bloat, keep conversation

    It removes progress ticks (40-48% of typical files), stale file reads, oversized tool outputs, and duplicate documents — while preserving the actual conversation DAG. This means more of your real session content survives the resume.

  2. github-actions commented on Mar 6, 2026

    @github-actions

    Closing for now — inactive for too long. Please open a new issue if this is still relevant.

  3. github-actions commented on Mar 16, 2026

    @github-actions

    This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.

  4. locked as resolved and limited conversation to collaborators on Mar 16, 2026
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

    staleIssue is inactive

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions