Practical use.
Session Vault helps when a local capture exists but the original chat is unavailable. The important distinction is between evidence that was captured on this machine and context that existed only in a remote conversation.
Session Vault.
Session Vault keeps local recovery evidence available after crashes, closes, outages, deleted threads, or tool bugs.
What it carries.
- Surviving conversation evidence
- Local session recovery history
- Pointers to deeper history when needed
- No mandatory cloud account
How it fits ShardStitch.
This feature preserves local recovery records so a deleted, rate-limited, or abandoned session does not erase the useful state already present on disk.
What survives a lost session.
Session Vault is useful when the original chat is closed, deleted, rate-limited, or no longer trustworthy. It keeps local recovery evidence available for a later scan, including the project location, captured state, and pointers needed to rebuild a continuation packet.
It is not a cloud transcript archive and it does not promise to restore a provider’s private conversation. The goal is to preserve enough local evidence that work can continue from the repository instead of from memory alone.
Recover what was actually captured.
After a closed, deleted, or stalled session, identify the matching local project and session record, then compare its timestamps and captured messages with current repository changes.
- Select the project and session deliberately; similar project names can point to different checkouts.
- Use the record to recover decisions and sequence, but use git status and files to establish what changed.
- Carry forward only the parts needed for the next action and call out gaps where the original session was not captured.
Worked example.
If two local projects share a similar name, compare the saved session path with the repository root and branch before using its transcript. Then separate the chat sequence from the current diff: the record can explain why an approach was tried, while the files show what remains. If the record stops before the last edit, mark that gap and inspect the working tree directly.
Limits and verification.
A local vault cannot recreate conversation content that was never captured, restore a provider account, or guarantee recovery after disk loss. Keep a separate backup for important project data and verify the recovered narrative against the repository.