Lightkeeper

Good to know before installing

Each hook runs python3 on the plugin's own scripts as a synchronous subprocess with a 10 s timeout (on every user message, after every write_file and patch, at the verify step and at session end), and those scripts run read-only git commands (rev-parse, remote get-url, worktree list, ls-tree, status, log) in the session's checkout and in the vault folder; the session primer and prompt hints put text from the vault's notes into the model's context; the hooks read the vault registry ~/.claude/vaults and the vault folders it lists, and write only inside the vault (_meta/index.json), a small per-session state file in the system temporary directory ($TMPDIR), and the plugin's own data directory; the init, seed, sync, tidy, trace and release procedures run the vault CLI through the terminal and commit to the vault's own git repository, and vault init appends the vault to ~/.claude/vaults and, only when you pass its opt-in flags, copies a vault launcher to ~/.local/bin (--install-cli), installs report-only post-merge and pre-push hooks in your code checkouts (--git-hook), or adds a post-commit hook that pushes every vault commit to the remote you name (--backup-remote); vault export write

From the plugin's catalog listing.