# Lightkeeper: Hermes Agent plugin

> An Obsidian-compatible map of how your codebase works (modules, flows, integrations, platform traps, decisions), kept outside the repo and kept honest by hooks: a primer on the first turn, pointers to the notes that…

Canonical: https://hermeswatcher.com/plugins/lightkeeper  
Tier: Community  
Official page (Nous Research): https://hermes-agent.nousresearch.com/docs/plugins/lightkeeper  
Last updated in catalog: 2026-10-23

An Obsidian-compatible map of how your codebase works (modules, flows, integrations, platform traps, decisions), kept outside the repo and kept honest by hooks: a primer on the first turn, pointers to the notes that own what you are asking about or editing, and a reminder through the verify gate when code moved but the map did not. Eight lightkeeper:* skills carry the procedures (init, seed, tidy, trace, release, knowledge-vault, vault-sync, vault-tidy); the vault CLI (find, check, sync, status, log, export) works from any shell. Not a memory provider.

## 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.

## How to install

1. Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.

```bash
hermes plugins install lightkeeper
```

2. Said no? Turn it on later:

```bash
hermes plugins enable lightkeeper
```

3. Restart Hermes so it loads the plugin.

Some plugins also need a sign-in or settings: see the official page. Memory plugins ask whether to become your memory provider instead. Steps follow the official plugins guide: https://hermes-agent.nousresearch.com/docs/user-guide/features/plugins

## Facts

- Category: Coding & developer tools
- Maintained by: Light5566 (Community)
- Needs: No API keys declared
- Works on: linux, macos
- Requires Hermes: `>=0.22.0`
- Version: 2.4.4
- In the catalog since: 2026-10-23

## Links

- [Full setup and settings (official page)](https://hermes-agent.nousresearch.com/docs/plugins/lightkeeper)
- [Source code](https://github.com/Light5566/claude-lightkeeper#hermes-agent)
- [All plugins](https://hermeswatcher.com/plugins.md)

---

HermesWatcher is an independent guide. It is not affiliated with or endorsed by Nous Research. The [official Hermes Agent documentation](https://hermes-agent.nousresearch.com/docs) and [repository](https://github.com/NousResearch/hermes-agent) from Nous Research are the authority; each page here lists the official sources it was written from. If this site and the official docs disagree, trust the official docs. Index for agents: https://hermeswatcher.com/llms.txt