🌐 日本語

Part 8: Session Management and Memory Persistence

NOTE

The lifecycle of a conversation and how memory is operated.
/compact and /clear are representative examples in Claude Code. Keeping conversations short and persisting decisions in files are not product-specific.
The theoretical basis is in Parts 1 and 2. This Part covers operations.

Why It Matters

LLM sessions are finite. As conversations grow longer, Context Rot progresses and Instruction Decay occurs. Proper session management is the most practical countermeasure for maintaining LLM quality.

→ Why: Which Structural Problems Does It Address?

IMPORTANT

• Context Rot: /compact prevents token accumulation through predictive compression
• Lost in the Middle: Compressing before 50% usage prevents U-shaped curve collapse
• Instruction Decay: /clear resets degradation by splitting sessions

Documents in This Part

Document	Content
Using /compact and /clear	When to compress and when to reset
/loop and Self-Driving Sessions	What an unattended loop amplifies, and the guards written into its specification
Why Memory Becomes a Problem	Information loss between sessions
What to Remember	Selecting information to persist
When and How to Recall	Memory retrieval strategy
Tool Comparison and Selection	Comparison of memory tools

---

Previous: Part 7: The Runtime Layer LLMs Don't See

Next: Part 9: Code-World Grounding — Code Intelligence