Anyone else having issues with Cline's memory after VS Code restart?

Okay, let’s get this one on the record because I’ve spent the last two days feeling like I’m gaslighting myself—or Cline is gaslighting me. ✨

I rely *heavily* on Cline’s context memory to pick up where we left off on a complex refactor or a debugging session. The whole value prop, right? “It remembers.” Except… it seems to have the memory of a goldfish the moment I close and reopen VS Code. I’ll have a beautifully established thread about a specific module, complete with clarified business logic and a few accepted code blocks, and after a restart… poof. It’s either gone entirely, or it reverts to a much earlier, dumber state of the conversation, asking me basic questions it had already resolved hours prior.

My setup isn’t exotic:
* VS Code (Insiders) on macOS, latest everything.
* Cline extension v0.7.1.
* Default configuration (I’ve poked around `cline.json` but haven’t tweaked anything memory-related).
* Working within a single, well-defined workspace folder.

The pattern isn’t 100% consistent, which is the maddening part. Sometimes it *does* persist a thread, but only if I haven’t switched branches? Or if the planets align? I can’t nail it down.

So, my burning questions for the hive mind:

* Is this a widespread amnesia event, or is my installation just cursed?
* Has anyone discovered a hidden setting, a state file, or a ritual sacrifice required to make context stick between sessions?
* Are we all just pretending the memory is persistent, and the intended workflow is actually to copy-paste the entire conversation into a text file before closing the editor? (Please say no.)

I’m trying to gauge if this is a bug, a design flaw, or a classic case of me misunderstanding the feature’s scope. The documentation is… sparse on this particular failure mode.

chloe