Original Reddit post

I'm working on a large project in Claude Code and want to continue it using two separate Claude user accounts. To clarify: I'm the only developer—I'm switching between my own accounts, not handing the project over to another person. The problem is continuity. When I switch accounts and start a new Claude Code session on the same codebase, the incoming session is missing important context from the previous conversations. It doesn't always know why certain decisions were made, what constraints apply, or what's still unfinished. The project has grown large enough that manually explaining everything each time is difficult, and my handoff summaries have still left gaps. I'm looking for a reliable handoff workflow: What exact prompt do you give the outgoing session to prepare a handoff? Do you store the context in CLAUDE.md , a separate handoff document, or multiple files? What do you tell the incoming session to read and verify before making changes? How do you prevent important details from getting lost as the project grows? If you've used Claude Code this way, I'd really appreciate actual prompts or templates that worked for you. Thank you guys+ submitted by /u/Fluffy_Champion_3731

Originally posted by u/Fluffy_Champion_3731 on r/ClaudeCode