AgentFixboard
WorkaroundLast checked Hermes Agent#state#setup

Memory provider holographic is not installed after an update

A session starts with Memory provider 'holographic' is not installed, so external memory is off for this session. Its automatic install failed less than an hour ago: run hermes plugins install holographic. hermes memory status shows Provider: (none — built-in only).

From GitHub

NousResearch/hermes-agent

Issue

Difficulty
Easy
Time
~5 min
Steps
2
Fixed in
—
Last checked

No upstream fix: these steps work around it. Source: issue closed completed; recovery is the maintainer comment. Last checked 2026-10-17.

Symptom

A session starts with Memory provider 'holographic' is not installed, so external memory is off for this session. Its automatic install failed less than an hour ago: run hermes plugins install holographic. hermes memory status shows Provider: (none — built-in only).

Evidence what you'll see

  • The report says the plugin files were present at v0.6.1, commit 46b6f908, and memory_store.db still had 49 facts and 21 entities. The session had no fact_store tool.
  • A later comment records DependencyConflict and pilk==0.2.4 has no publish time while enabling the plugin. File memory in MEMORY.md and USER.md still loaded.

Why it happens

The automatic install of the catalog provider failed. The plugin maintainer says that failure can leave memory.provider empty and list holographic under plugins.disabled, while memory_store.db stays on disk. The reporter ties the move out of core to an update from 0.21.6. The v0.22.0 notes say Holographic moves to the plugin catalog on update or first start.

Affected versions

Hermes 0.21.6, Python 3.11.9. The report's operating system line is Windows 11 专业工作站版 Insider Preview 26220.9606.

Fix steps

0 of 2 done

Your check marks stay in this browser only.

How to check it worked

  • hermes memory status lists the holographic provider instead of Provider: (none — built-in only). A recovered session in the thread logged Memory provider 'holographic' registered.

If it still fails

  • The plugin maintainer says memory_store.db is left untouched by the failed install. The facts are still in that file.
  • The maintainer names commit abbc2ba35c (release age is checked when Hermes locks, not on users' machines) as the lock change, and says hermes plugins install holographic should succeed on an update that contains it. GitHub's compare of that commit to tag v0.22.0 is behind by 619 and ahead by 0, so the tag contains the commit. The v0.22.0 notes do not name it.
  • Pull request 137018, which would replace this warning with hermes plugins enable holographic, was closed on 16 Oct 2026 without merging. The linked issue does not include a merged rewrite of the warning.

Sources and credit

Summarized in our own words from these public reports. Credit goes to their authors.

Provided as is, without warranty. Try changes in a non-production environment and back up first. Security-related steps: verify against the official docs. Terms · Request removal or attribution change

Hit an error we don't cover? Submit it