claude-code - 💡(How to fix) Fix Session/thread context lost mid-workflow, auto-memory saved us but reveals gaps in long-running project resilience

Environment

• Claude Code on Windows 11 (Opus 4.7, 1M context)
• Project: multi-day workflow building a Reddit + Pinterest intelligence pipeline (~10 hour active session across several days)

What happened I was deep in a session orchestrating a complex pipeline build (BERTopic clustering, Pinterest API OAuth, video render for platform submission, multiple Python scripts). The chat thread became inaccessible, I couldn't scroll back to my prior context, prior tool outputs, the running todo list, or which sub-task ("stack 8" / "stack 9") was actively in flight.

I had to start a fresh session and reconstruct state by asking the agent to read auto-memory files and stat artifacts on disk.

What worked (please keep doing this) The auto-memory system is a lifesaver. A persistent note at ~/.claude/projects/<project>/memory/<topic>.md had captured the full session state, every sub-item, every blocker, every file path. Recovery took about 2 minutes once the new session started. Without it I'd have lost hours of orientation.

What hurt

1. No visible warning that the prior thread's context would become inaccessible. I just hit a wall.
2. No in-app "restore session" or "resume from latest checkpoint" affordance.
3. Auto-memory captured project state, but transient state (running processes, active branch, exact next-action) is not in memory by design.
4. Felt panic before realizing memory had saved me, there's no UI cue pointing users at the recovery path.

Suggestions

• Show a clear notice when a session is about to be archived/compacted, with a one-click "save key context to memory now" option.
• Add a "resume session" / "show recent sessions" command surfacing the last N sessions with one-click reopen.
• When a session can't be reopened, surface a "what to do next" tip that points at auto-memory recovery (read MEMORY.md, ask the agent to reconstruct from disk).
• Consider opt-in auto-backup of the memory folder itself (it currently isn't git-tracked or synced anywhere by default).

Happy to share more detail privately if useful. Thanks for shipping Claude Code, when it works (which is most of the time), it's transformative for solo operators like me.