[FEATURE]

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Title: Persistent memory gaps between sessions cause excessive token consumption and session timeouts

Body:

Hi Claude Code team,

First — I genuinely love this tool and the work you're doing. This feedback comes from a place of frustration born out of caring about the product, not wanting to tear it down.

Here's my problem: Claude does not reliably retain context between sessions for the same project. Each new session, I find myself re-explaining decisions, re-correcting the same mistakes, and re-establishing context that was hard-won in a previous session. Things that were developed, tested, and working correctly have to be explained again from scratch.

The real sting is the knock-on effect: all of that re-explanation consumes tokens. That pushes me toward session limits faster, which then triggers timeouts — and I lose more context. It becomes a compounding problem.

What frustrates me most is that I feel penalised for a limitation that isn't mine. I didn't forget the work we did together — Claude did. Yet I'm the one burning through my token allowance to compensate for it.

I understand there are technical reasons behind session isolation, and I appreciate that tools like CLAUDE.md and the auto-memory system exist as partial mitigations. But in practice, for active multi-session projects, these don't fully close the gap.

I'd love to see the team invest in more robust, reliable, and transparent persistent memory across sessions — especially scoped to a project. Users working on long-running projects deserve continuity without paying the token cost of reconstruction.

Thanks for listening — keep up the great work overall.

Proposed Solution

Some way Claude does not forget things that cost me valuable tokens to remind it.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

Other

Use Case Example

_No response_

Additional Context

_No response_