Read Once
From its catalog listing
On a repeated identical local read_file, tells the model to answer from the earlier result when READ_ONCE_HITS=1, the file bytes are unchanged, and that exact result is still in the latest model request. Observe-only otherwise. /read-once stats shows hits.
Good to know before installing
reads and SHA-256-hashes regular files under READ_ONCE_ROOT (1 MiB max), inspects the model request in memory for that result digest, and keeps ephemeral metadata only. No network, no telemetry, no disk cache, and no background watcher. It does not hash dotenv names, auth.json, or paths under vault, mcp-tokens, browser-profile, webapp, or pairing. Hits stay off unless READ_ONCE_HITS=1. A repeat of the same read can be Hermes's unchanged-stub rather than the file bytes.
From its catalog listing.
How to install
- Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install read-once - Said no? Turn it on later:
hermes plugins enable read-once - Restart Hermes so it loads the plugin.
Some plugins also need a sign-in or settings: see Full setup & settings. Memory plugins ask whether to become your memory provider instead. Steps follow the official plugins guide (opens in a new tab).
- Category
- Memory & notes
- Maintained by
- batmnnn (Community)
- Needs
- No API keys declared
- Adds hooks
post_tool_callpost_compactionon_session_endon_session_reseton_session_finalizeon_session_delete- Needs Hermes
- 0.23.0 or newer
- Version
- 0.2.0
- In the catalog
- 2026-11-11
Known issues (from its catalog listing)
- Tested on Hermes 0.23.0 only.
- A terminal backend cached inside Hermes and not visible as TERMINAL_ENV or the hermes_terminal_scope context var can still be treated as local.
Using the Hermes desktop app? See where plugins live

Full setup & settings ↗Source code ↗
More in memory & notes
New Hermes Agent updates every day on X. Follow @HermesWatcher