codemap_backup_list
List available backups for persistent storage files. Shows daily and turn-based backups.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
type | stringgroups | annotations | labels | ❌ Optional | Filter by type: groups|annotations|labels (omit for all) |
backupType | stringdaily | turn | ❌ Optional | Filter by backup type: daily|turn (omit for all) |
Usage Examples
MCP Usage (for AI Agents like Claude)
json
{
"name": "codemap_backup_list",
"arguments": {}
}Example Output
JSON Response
json
{
"daily": [
{
"type": "groups",
"timestamp": "2026-04-07",
"size": 2847,
"path": ".codemap/backups/daily/groups-2026-04-07.json"
},
{
"type": "labels",
"timestamp": "2026-04-07",
"size": 1245,
"path": ".codemap/backups/daily/labels-2026-04-07.json"
}
],
"turn": [
{
"type": "groups",
"timestamp": "2026-04-07T14-23-45",
"size": 2850,
"path": ".codemap/backups/turn/groups-turn-0001.json"
}
]
}When to Use This Tool
-
Use
- Check available restore points before recovery
- Verify backup retention policies are working
- Find specific backup timestamps
- Audit backup coverage across storage types
- Determine oldest/newest backups for cleanup
codemap_backup_list when you need to:
Common Patterns
Pre-Restore Audit
Backup Health Check
Cleanup Planning
1. List backups with type filter
2. Review available timestamps
3. Choose appropriate restore point
4. Use timestamp in restore commandBackup Health Check
1. List all backups
2. Verify each type has backups
3. Check daily vs turn-based balance
4. Identify gaps in coverageCleanup Planning
1. List backups by type
2. Sort by timestamp
3. Identify old backups for removalPro Tips
- Daily backups: One per day, retained for 7 days
- Turn backups: Created on each modification, retained last 10
- Use type filter: Faster when you only need specific storage type
- Check before restore: Always list first to verify backup exists
- Timestamp format: Daily uses YYYY-MM-DD, turn uses full ISO timestamp
Best Practices
- List backups before restore operations
- Use type filter when working with specific storage
- Monitor backup counts regularly
- Verify daily backups exist for each day
- Check turn backups for recent changes
- Document restore points for important changes
Common Mistakes
❌ Mistake: Restoring without checking available backups first
✅ Instead: Always list backups to verify restore point exists
❌ Mistake: Not filtering by type when you know what you need
✅ Instead: Use type parameter to reduce noise and improve speed
❌ Mistake: Assuming backups exist for all types
✅ Instead: List and verify coverage for each storage type
❌ Mistake: Ignoring empty backup results
✅ Instead: Investigate why backups are missing if unexpected
❌ Mistake: Not understanding daily vs turn-based retention
✅ Instead: Know that daily=7 days, turn=last 10 modifications
❌ Mistake: Using backup list as primary monitoring tool
✅ Instead: Check periodically but don't rely solely on manual checks
✅ Instead: Always list backups to verify restore point exists
❌ Mistake: Not filtering by type when you know what you need
✅ Instead: Use type parameter to reduce noise and improve speed
❌ Mistake: Assuming backups exist for all types
✅ Instead: List and verify coverage for each storage type
❌ Mistake: Ignoring empty backup results
✅ Instead: Investigate why backups are missing if unexpected
❌ Mistake: Not understanding daily vs turn-based retention
✅ Instead: Know that daily=7 days, turn=last 10 modifications
❌ Mistake: Using backup list as primary monitoring tool
✅ Instead: Check periodically but don't rely solely on manual checks