[Feature Request] Native persistent session architecture with indefinite context preservation

Persistent-Session Architecture: a-user-driven prototype

I've been-running two-Claude-Code-sessions in-parallel for-over-52-hours, combined with-a-persistent-memory-system (MEMORY.md files synced to-GitHub).
This effectively creates a-dual-memory-architecture:

• Sessions = short-term-working-memory (days)
• Memory-files = long-term-knowledge-store (permanent)
• --resume = bridge between-the-two

I believe a-native Persistent-Session feature, where context is-preserved indefinitely without-manual-memory-management, which would-be the-next-major-UX-leap for-Claude-Code.

The-current --resume is-a-great-step, but sessions still degrade over-time
through-context-compression.
What-if sessions never-truly-ended?

……………………………………………………………
Submitted by Gles

Environment Info

• Platform: win32
• Terminal: windows-terminal
• Version: 2.1.47
• Feedback ID: 1c01aaf6-5ecb-4515-a84a-964c0663360c