Add agent memory search for OpenClaw and Hermes Agent using llama.cpp

[merveenoyan]

Note

Low Risk
Documentation-only change with no runtime or security impact.

Overview
Documents how to run local memory / semantic search alongside the existing llama.cpp agent setups in agents-local.md.

For OpenClaw, a new subsection covers installing node-llama-cpp, setting agents.defaults.memorySearch to the local provider with an Hugging Face EmbeddingGemma GGUF path, restarting the gateway, and checking openclaw memory status.

For Hermes Agent (section title updated from “Hermes”), a matching subsection explains wiring auxiliary.session_search in ~/.hermes/config.yaml to a local OpenAI-compatible embedding endpoint and validating with hermes memory status.

^{Reviewed by Cursor Bugbot for commit 1c56c66. Bugbot is set up for automated code reviews on this repo. Configure here.}

[HuggingFaceDocBuilderDev]

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

[merveenoyan]

@pcuenca @burtenshaw @gary149 can you take a look?

[pcuenca]

I don't use OpenClaw. Does this have to be the node version?

[merveenoyan]

not sure I understand your question :/

[pcuenca]

why not just use llama.cpp, instead of node-llama-cpp? Is this an OpenClaw requirement?

[merveenoyan]

if you install this way you can use below one-liner to get llama server up and using it for memory instead of setting it up yourself

[pcuenca]

Conceptually looks good, but it could be helpful if other Hermes / OC users could take a look. It'd be helpful to describe what this brings over the built-in memory search implementations; as far as I know harnesses have ways to look stuff up in memory without going through this process.

[pcuenca]

How does memory search work if you don't do anything? Because it's able to look up things in memory by default, AFAIU. Here's my output from the command you mention below. I haven't done anything about semantic search, but the first lines match what you said:

Memory status
────────────────────────────────────────
  Built-in:  always active
  Provider:  (none — built-in only)

  Installed plugins:
    • byterover  (requires API key)
    • hindsight  (API key / local)
    • holographic  (local)
    • honcho  (API key / local)
    • mem0  (API key / local)
    • openviking  (API key / local)
    • retaindb  (API key / local)
    • supermemory  (requires API key)

[merveenoyan]

it does exact text search afaik, where it just does look-up from sessions. imo it's counterproductive