[BUG] Desktop app unable to resume session after moving misplaced memory files; CLI unaffected

Resolved 💬 3 comments Opened Apr 26, 2026 by aress2525 Closed May 30, 2026

Preflight Checklist

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

What's Wrong?

he desktop app's memory system became corrupted when stray files named "condescending-kare" (and similar) were present in the project root directory. After moving these files to the proper directory, the desktop app was unable to resume the previous session state.

The CLI, using the same project and memory system, had no issues and resumed normally.

Steps to reproduce:

Create stray memory-related files in project root (e.g., "condescending-kare")
Use the desktop app to work on the project
Move the stray files to the proper directory
Attempt to resume the session in the desktop app
Expected behavior:
Desktop app should resume the session normally, as the CLI does.

Actual behavior:
Desktop app fails to resume session state after files are moved.

Environment:

Claude Code version: [run claude -most recent]
Platform: [Windows, WSL]

What Should Happen?

Claude should be able to repair memory state. As Claude code in the CLI had no issues and was able to stitch together the memory files this should be a function the desktop app should be able to do as well.

Error Messages/Logs

Steps to Reproduce

work in project directory.. Then change the directory in root-- (thought i was pointing claude to where other files were located. apparently that caused files were located in part in the root directory and the project directory

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

tried sonnet in desktop app but failed to fix

Claude Code Version

Claude Code 2.1.39 claude-opus-4-7[1m], desktop app 1.4758.0.0

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗