Reattach to Session
The reattach workflow allows you to resume development on any existing Raindrop project exactly where you left off. Whether you stopped mid-development, switched to another project, or are returning days later, reattaching restores complete context and continues seamlessly.
How Reattachment Works
Reattachment is instant and automatic. Once you provide your session and timeline IDs, Claude Code immediately has access to:
- Your complete PRD and all requirements
- All architectural decisions and infrastructure setup
- Generated code and current implementation state
- Team member access and collaboration context
- Current development phase and next steps
Your involvement: Provide session IDs and continue from where the workflow guides you.
Starting Reattachment
Using Shorthand Command:
/reattach-raindrop-session [session_id] [timeline_id]
Using Direct MCP Call:
Claude, call the liquidmetal-staging:reattach_to_session MCP tool with session_id "your-session-id" and timeline_id "your-timeline-id".
Finding Your Session IDs:
You can instruct Claude Code to look in your .raindrop.config.local.json
file to find your session and timeline IDs.
What You Achieve with Reattachment
Complete Context Restoration
You get immediate access to your entire project history. Claude Code knows exactly what you were building, why specific decisions were made, and how all components fit together. No time wasted explaining or reconstructing context.
Seamless Continuation
You receive clear guidance on what to do next based on your current development phase. Whether you were in the middle of requirements gathering, code implementation, or deployment, the workflow continues exactly where you left off.
Preserved Team Access
All team members maintain their access and can continue collaborating. Invitations remain active and shared context is immediately available to everyone on the team.
Infrastructure State Awareness
You get visibility into your current deployment state, including what infrastructure is running, which endpoints are live, and what still needs to be completed.
Reattachment Scenarios
- Mid-Development Resume - Pick up development in the exact phase where you stopped
- Cross-Session Project Switching - Switch between multiple projects seamlessly
- Team Member Joining - New team members get instant access to complete project context
- Long-Term Project Return - Return to projects after weeks or months with complete context restoration
- Error Recovery - Resume from a stable point after addressing workflow issues
- Infrastructure Troubleshooting - Continue after resolving deployment or provisioning problems
Session States and Next Actions
When you reattach, you’ll see your current state and what happens next:
session_started
- Set up team members or begin requirements definitionteam_set
orprd_created
- Continue with architecture generation and manifest creationmanifest_created
- Proceed with database schema design or documentation retrievaldocumentation_retrieved
- Continue with complete code implementationcoding_started
- Move to testing and validationtests_written
- Proceed with deployment to live infrastructuredeployed
- Continue with endpoint testing and final verificationtested
- Application is complete and ready for users
Reattachment transforms development from linear, session-bound work into flexible, resumable project management where you can always pick up exactly where you left off with complete context and team coordination.