The ten-point recoverability check
- 01
You know the active Claude directory
You confirmed the native Windows location and any CLAUDE_CONFIG_DIR override.
- 02
You know the project instruction scopes
Relevant CLAUDE.md and .claude locations are identified.
- 03
Repositories have their own protection
Committed code is pushed and important uncommitted work has a deliberate backup.
- 04
Credentials stay excluded
Tokens, private keys and secret-bearing configuration are not copied casually.
- 05
A copy survives device loss
At least one protected destination is separate from the Windows disk.
- 06
Integrity failures are detectable
Missing or modified backup data fails before recovery publication.
- 07
Useful history is retained
An earlier point can predate accidental deletion or corruption.
- 08
Recovery uses a safe folder first
The first action does not overwrite live Claude Code state.
- 09
A recent point was reconstructed
Recovery was actually tested rather than inferred from a completed copy.
- 10
The scope is explicit
Native Windows, WSL, Claude Desktop, cloud sessions and original project files are not blurred together.
When to repeat the check
Repeat it after changing CLAUDE_CONFIG_DIR, moving projects, changing backup destinations, adding important memory or customisations, or after a material Claude Code format change. A once-correct plan can become stale.
How to interpret the result
- 8-10 checks: the plan is credible; keep testing after meaningful changes
- 5-7 checks: recoverability still has important gaps
- 0-4 checks: a local failure could remove important continuity
What Calmbu currently claims
Calmbu shows the current supported scope, safer exclusions, encrypted protection, recovery status, and safe-folder recovery. Claude Code is launch-supported on native Windows.
See the recovery model How Calmbu verifies its claimsCommon questions
How often should I test Claude Code recovery?
Test after setup, after storage or configuration changes, and periodically after material Claude Code updates.
Is a synced .claude folder enough?
Sync can help with device loss, but it does not by itself prove versioned, integrity-checked reconstruction. Deletion or corruption may also sync.
What is the most important check?
Reconstruct a recent point in a separate folder and inspect it. That exposes more gaps than a copy-completed message.
Official references used for Claude Code facts
Anthropic documentation establishes Claude Code behaviour. Calmbu-specific statements describe the current product contract and are not presented as Anthropic guidance.