Long Claude coding chats can lose project details during handover
A beginner coder used Claude to set up and build a project for a full week in one continuous chat. The chat became so large that it was hard to load and manage.
A detailed JSON was created to move the work into a fresh chat, with an extra request for Claude to read the full old conversation rather than rely only on memory. The new chat still did not carry over.
It reached about 80% of the old setup, but some earlier features and context were missing. /compact was also tried, but the old chat remained hard to use, and the main unresolved question is whether an old can be used directly as context for a new one.
Key points
- One was used for about a week of coding work.
- The became too large to load and manage easily.
- A JSON handover was used to start a new chat, but it missed some details.
- /compact did not fully solve the problem with the old chat.
- The new chat carried over about 80% of the previous work, but some features and context were still missing.
Sources covering this story (5)
- r/ClaudeAILong Claude coding chats can lose project details during handover ↗
- r/ClaudeAIHow do you guys handle workspace recovery with Claude Code? ↗
- r/CodexHacksBuilt a free, open-source continuity layer for and with Codex and I want to share it. Observed 4k–13k tokens of repeated repo rediscovery avoided per prompt ↗
- r/ClaudeAIHow do you guys manage context and sync two AI models without maxing out the context window instantly? ↗
- r/ClaudeAIHow do you manage long-term AI-assisted coding without losing control? ↗