Skip to content

[BUG] Session data not persisting across recent compactions #14820

New issue
New issue
Closed as not planned
Closed as not planned
[BUG] Session data not persisting across recent compactions#14820
Labels
area:coreautocloseIssue will be closed automaticallybugSomething isn't workingmemoryplatform:macosIssue specifically occurs on macOS

Description

@mintmcqueen
mintmcqueen
opened on Dec 20, 2025

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

If shortly after compaction -- even after Claude comes to a stopping point -- user exits and restarts a new session, Claude Code fails to persist session data. In other words, the /resume command fails to store recent data.

What Should Happen?

Close the session, restart -- and find most recent stopping point as resumable session.

Error Messages/Logs

N/A

Steps to Reproduce

N/A

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.0.72

Claude Code Version

2.0.74

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

Activity

  1. mintmcqueen
    added
    bugSomething isn't working
    on Dec 20, 2025
  2. github-actions
    added
    platform:macosIssue specifically occurs on macOS
    area:core
    memory
    on Dec 20, 2025

  3. github-actions commented on Dec 20, 2025

    @github-actions
    github-actionsBot
    on Dec 20, 2025 – with GitHub Actions

    Found 3 possible duplicate issues:

    1. [Bug] Resume flag reverts to pre-compaction state after manual compaction #14462
    2. Cannot resume session when context exceeds limit - no way to compact before loading #14472
    3. [Bug] Session compaction loses context priority and critical blockers #13678

    This issue will be automatically closed as a duplicate in 3 days.

    • If your issue is a duplicate, please close it and 👍 the existing issue instead
    • To prevent auto-closure, add a comment or 👎 this comment

    🤖 Generated with Claude Code

  4. github-actions commented on Jan 19, 2026

    @github-actions
    github-actionsBot
    on Jan 19, 2026 – with GitHub Actions

    This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

  5. github-actions
    added
    autocloseIssue will be closed automatically
    on Jan 19, 2026

  6. github-actions commented on Feb 14, 2026

    @github-actions
    github-actionsBot
    on Feb 14, 2026 – with GitHub Actions

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

  7. github-actions
    closed this as not plannedon Feb 14, 2026

  8. github-actions commented on Feb 23, 2026

    @github-actions
    github-actionsBot
    on Feb 23, 2026 – with 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.

  9. github-actions
    locked as resolved and limited conversation to collaborators on Feb 23, 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

    area:coreautocloseIssue will be closed automaticallybugSomething isn't workingmemoryplatform:macosIssue specifically occurs on macOS

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions