codemap_session_reopen
Reopen a previously closed session to continue multi-day work. Creates new transaction log with original session ID, preserving continuity while tracking new changes.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
sessionId | string | ✅ Required | Session ID to reopen (e.g., '2026-04-05T02-53-34'). Get from codemap_session_list. |
Usage Examples
MCP Usage (for AI Agents like Claude)
json
{
"name": "codemap_session_reopen",
"arguments": {
"sessionId": "2026-04-05T02-53-34"
}
}Example Output
JSON Response
json
{
"success": true,
"message": "Session 2026-04-05T02-53-34 reopened successfully",
"sessionId": "2026-04-05T02-53-34",
"originalStartedAt": "2026-04-05T02:53:34.789Z",
"reopenedAt": "2026-04-08T14:30:00.123Z",
"originalDuration": "3 hours, 22 minutes",
"originalSummary": "Started implementing user dashboard - completed data layer",
"rootPath": "/path/to/project",
"stats": {
"files": 301,
"symbols": 3120,
"dependencies": 175
},
"parsers": [
{
"name": "@egentica/codemap-parser-typescript",
"version": "0.1.0",
"extensions": ".ts, .tsx, .js, .jsx"
}
],
"previousActivity": {
"filesCreated": 5,
"filesUpdated": 12,
"filesDeleted": 1,
"groupsModified": 3
},
"checklist": {
"items": [
{
"text": "Review .codemap/sessions/NEXT_SESSION.md",
"priority": "high"
}
]
}
}When to Use This Tool
-
Use
- Continue work on a multi-day feature or task
- Resume work after closing a session prematurely
- Maintain session continuity for related work
- Track cumulative changes across multiple work sessions
- Preserve session context and history
codemap_session_reopen when you need to:
Common Patterns
Multi-Day Feature Development
Perfect for features that take multiple days to implement.
Resume After Interruption
Maintains context across interruptions.
Review and Continue
Useful when you don't remember the exact session ID.
1. Day 1: Work, then codemap_close({ summary: "Progress" })
2. Save the sessionId from response
3. Day 2: codemap_session_reopen({ sessionId })
4. Continue work, close again
5. Repeat until feature completePerfect for features that take multiple days to implement.
Resume After Interruption
1. Working on task...
2. Emergency interruption - codemap_close({ summary: "WIP" })
3. Handle emergency
4. codemap_session_reopen({ sessionId })
5. Pick up exactly where you left offMaintains context across interruptions.
Review and Continue
1. codemap_session_list() to see past sessions
2. Find session to continue
3. codemap_session_read({ sessionId }) to review details
4. codemap_session_reopen({ sessionId }) to resume
5. Continue workUseful when you don't remember the exact session ID.
Pro Tips
- Same session ID, new tracking: Reopening preserves the original session ID but creates a fresh transaction log for new changes. This maintains continuity.
- Check previous activity: The response shows what was done in the original session (
previousActivity), helping you remember where you left off. - Can't reopen if session active: Must close current session before reopening another. This prevents session collision.
- Cumulative history: When you close a reopened session, the changes are additive - new files are combined with original session's file list.
- Use list to find sessions: If you don't know the session ID, use
codemap_session_listto browse recent sessions and their summaries. - Original summary preserved: The
originalSummaryfield shows what the session was about, helping confirm you're reopening the right one.
Best Practices
- Use meaningful summaries when closing - makes finding sessions easier when reopening
- Always check
previousActivityto refresh your memory of what was done - Close sessions between reopen cycles to maintain clean history
- Use reopen for related work only - don't reopen unrelated old sessions
- Review the session with
codemap_session_readbefore reopening if it's been a while
Common Mistakes
❌ Mistake: Trying to reopen while another session is active
✅ Instead: Close current session first:
❌ Mistake: Reopening sessions without checking what they contained
✅ Instead: Use
❌ Mistake: Reopening very old sessions for unrelated work
✅ Instead: Start fresh sessions for new work, only reopen for continuing specific features
❌ Mistake: Not saving session IDs when closing
✅ Instead: Save the
❌ Mistake: Assuming reopened sessions track from original start time
✅ Instead: New work duration starts from reopen time, original duration shown separately
❌ Mistake: Reopening sessions on wrong project
✅ Instead: Sessions are project-specific - ensure you're in correct project before reopening
✅ Instead: Close current session first:
codemap_close() then codemap_session_reopen({ sessionId })❌ Mistake: Reopening sessions without checking what they contained
✅ Instead: Use
codemap_session_read({ sessionId }) to review before reopening❌ Mistake: Reopening very old sessions for unrelated work
✅ Instead: Start fresh sessions for new work, only reopen for continuing specific features
❌ Mistake: Not saving session IDs when closing
✅ Instead: Save the
sessionId from close response for easy reopening later❌ Mistake: Assuming reopened sessions track from original start time
✅ Instead: New work duration starts from reopen time, original duration shown separately
❌ Mistake: Reopening sessions on wrong project
✅ Instead: Sessions are project-specific - ensure you're in correct project before reopening