codemap_session_read
Read detailed summary for a specific session by ID. Returns full session details including all files changed, groups modified, annotations added, and complete transaction history.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
sessionId | string | ✅ Required | Session ID to read (e.g., '2026-03-30T21-08-29'). Get from codemap_session_list. |
Usage Examples
MCP Usage (for AI Agents like Claude)
json
{
"name": "codemap_session_read",
"arguments": {
"sessionId": "2026-04-08T14-23-45"
}
}Example Output
JSON Response
json
{
"success": true,
"session": {
"sessionId": "2026-04-08T14-23-45",
"startedAt": "2026-04-08T14:23:45.123Z",
"closedAt": "2026-04-08T16:38:12.456Z",
"duration": "2 hours, 15 minutes",
"summary": "Implemented user authentication system with JWT tokens",
"filesCreated": [
"src/auth/jwt.ts",
"src/middleware/auth.ts",
"tests/auth.test.ts"
],
"filesUpdated": [
"src/api/routes.ts",
"src/config/app.ts",
"package.json",
"tsconfig.json",
"src/types/auth.ts"
],
"filesDeleted": [
"src/auth/old-auth.ts"
],
"filesRenamed": [],
"groupsModified": [
"auth-system",
"api-layer"
],
"notationsAdded": [
"auth-system: Added JWT validation middleware with expiry handling",
"api-layer: Integrated auth middleware into route handlers"
],
"annotationsAdded": []
}
}When to Use This Tool
-
Use
- Review what happened in a specific session
- Check which files were changed before reopening
- Audit session activity
- Generate reports on development history
- Verify session exists before reopening
codemap_session_read when you need to:
Pro Tips
- Always read before reopen: Check session details before reopening to confirm it's the right one
- Complete file lists: Unlike
listwhich shows summaries,readshows every file changed - Shows groups and annotations: See which groups were modified and what annotations were added
- Use with list: List to browse, read to get details on specific sessions
- Session ID required: Must provide exact session ID from
codemap_session_list
Best Practices
- Read session details before reopening to confirm it's the right one
- Use to audit what happened in past sessions
- Combine with list for comprehensive session browsing
- Check file counts to understand session scope
Common Mistakes
❌ Mistake: Guessing session IDs
✅ Instead: Get session IDs from
❌ Mistake: Not checking if session exists before reading
✅ Instead: Handle
❌ Mistake: Using read when list would suffice
✅ Instead: Use
✅ Instead: Get session IDs from
codemap_session_list first❌ Mistake: Not checking if session exists before reading
✅ Instead: Handle
SESSION_NOT_FOUND error gracefully❌ Mistake: Using read when list would suffice
✅ Instead: Use
list for browsing, read only when you need full details