Repair and recover
TroubleshootingWhen something looks off, Lyt can usually put itself right — look first, then fix only what you inspected. Start with a diagnosis: ask your agent to identify registry and mesh drift, then apply the repair you have reviewed.
1. Diagnose
Start here: one check that looks over the whole setup and reports what it finds.
Using Lyt, check whether my setup is healthy and tell me what you find. Report anything that was skipped or could not be checked, not just the failures.
Almost entirely a read: it probes binaries, GitHub auth, registry, vault and index health. The one thing it changes is a legacy identity file, which it migrates to the current format on any run. Checks it cannot reach are reported as skipped rather than failed, so a clean result is not proof every check ran.
lyt doctorUse this first for environment checks, missing vault paths, registry issues, and health guidance.
2. Preview, then repair
Using Lyt, show me what repair would change in my pod. Use dry-run only; do not change files or registry state.
lyt repair --dry-runDry run is the default and does not write. Review the reported findings and their suggested remediation before applying a change. A vault that has findings is not broken — drift is a normal thing to tidy up.
Apply the intended repair
Using Lyt, show me the repair finding you propose to fix and its exact target id, then wait for me to approve it before you apply anything. Apply only that one finding, not all of them.
Apply runs immediately — Lyt does not ask again, so your approval is the gate. Scope it with --target to the finding you inspected; without a target it applies every finding at once, and it refuses outright above five.
lyt repair --apply --target <finding-id>Repairs are idempotent. Re-attaching an orphan vault additionally requires you to name the mesh it should belong to, so it cannot land somewhere you did not choose.
Reconcile content and indexes
This is for when a note exists on disk but search cannot find it — or the other way around.
Using Lyt, check my research notes vault for drift between the markdown on disk and the search index.
lyt vault reconcile research/notesReconcile is detect-only by default. Add --apply only after reviewing missing frontmatter and unindexed Figments. For a pure cache rebuild, use lyt reindex --vault research/notes.
Snapshot before risky work
A snapshot is your undo point — take one before anything you might regret.
Using Lyt, take a snapshot of my research notes vault and label it before-merge.
lyt vault snapshot research/notes --label before-mergeA snapshot is a local Git branch containing the full working tree. Restore it deliberately with lyt vault restore research/notes --from-snapshot <label>.
Freeze while you investigate
Freezing puts a vault on hold: Lyt stops writing to it and syncing it while you figure things out. Your editor and Git still can.
Using Lyt, freeze my research notes vault for 24 hours while I look into something.
lyt vault freeze research/notes --until 24hA frozen vault refuses mutations and sync until it is unfrozen or the bounded duration expires.