diff --git a/plugin-catalog/hyatlas.yaml b/plugin-catalog/hyatlas.yaml
index 2e21b1a29a..abf6b1bcc5 100644
--- a/plugin-catalog/hyatlas.yaml
+++ b/plugin-catalog/hyatlas.yaml
@@ -8,7 +8,7 @@ screenshots:
   - https://raw.githubusercontent.com/tuancookiez-hub/HyAtlas-Memory/f61727a84971dcf3b5bdd2a9a2a12e74b47695ba/docs/images/desktop-overview.png
   - https://raw.githubusercontent.com/tuancookiez-hub/HyAtlas-Memory/f61727a84971dcf3b5bdd2a9a2a12e74b47695ba/docs/images/desktop-graph.png
 title: HyAtlas Memory
-description: "HyAtlas v4 — self-hosted 7-layer memory provider backed by a pure-Go single-binary server you run yourself (chromem-go vectors, in-process BGE-small embeddings, hybrid vector + keyword search, bitemporal knowledge graph with source citations). Embeddings, the vector index and stored memories stay local. Ships agent tools (hyatlas_status/search/recent/add), a `hermes hyatlas` CLI, a Desktop pane with a starmap graph view, and a web dashboard. Disclosure — requires the separate hyatlas-go server, installed by the user. The plugin never downloads or bundles it, and it talks only to the configured server (default 127.0.0.1:19528). Embeddings and stored memories stay local. Extraction is opt-in: the server has no default LLM endpoint and makes no LLM call until HYATLAS_LLM_BASE, HYATLAS_LLM_MODEL and HYATLAS_LLM_KEY are all set. The repo installer pre-fills a free Nous Portal endpoint that Enter accepts, but nothing is sent until you also enter a key. Once configured, each turn's user and assistant text goes to that endpoint (not tool output or context summaries; capped at 12,000 characters). In the default ultra mode the server also sends batches of up to 50 stored facts to it every 6 hours and supersedes (hides but keeps) the facts the model marks merged or stale, recording a reason for each drop. It also records relations corroborated across turns in the local knowledge graph (HYATLAS_CONSOLIDATE_GRAPH=off disables that). HYATLAS_MODE=lite makes no LLM call. Server endpoints that rewrite stored data are off unless the server runs with HYATLAS_ADMIN=on. The spawned server gets an allowlisted environment (OS essentials plus HYATLAS_*), not the agent's keys. auto_start is off by default. On Windows, if a hyatlas-go.ps1 launcher is configured, `hermes hyatlas start/stop` runs it; the repo's sample launcher reads your Nous token from Hermes auth.json and points extraction at the Nous Portal. No telemetry."
+description: "HyAtlas v4 — self-hosted 7-layer memory provider backed by a pure-Go single-binary server you run yourself (chromem-go vectors, in-process BGE-small embeddings, hybrid vector + keyword search, bitemporal knowledge graph with source citations). Embeddings, the vector index and stored memories stay local. Ships agent tools (hyatlas_status/search/recent/add), a `hermes hyatlas` CLI, a Desktop pane with a starmap graph view, and a web dashboard. Disclosure — requires the separate hyatlas-go server, installed by the user. The plugin never downloads or bundles it, and it talks only to the configured server (default 127.0.0.1:19528). Embeddings and stored memories stay local. Extraction is opt-in: the server has no default LLM endpoint and makes no LLM call until HYATLAS_LLM_BASE, HYATLAS_LLM_MODEL and HYATLAS_LLM_KEY are all set. The repo installer pre-fills a free Nous Portal endpoint that Enter accepts, but nothing is sent until you also enter a key. Once configured, each turn's user and assistant text goes to that endpoint (not tool output or context summaries; capped at 12,000 characters). In the default ultra mode the server also sends batches of up to 50 stored facts to it every 6 hours and supersedes (hides but keeps) the facts the model marks merged or stale, recording a reason for each drop. It also records relations corroborated across turns in the local knowledge graph (HYATLAS_CONSOLIDATE_GRAPH=off disables that). HYATLAS_MODE=lite makes no LLM call. Server endpoints that rewrite stored data are off unless the server runs with HYATLAS_ADMIN=on. The spawned server gets an allowlisted environment (OS essentials plus HYATLAS_*), not the agent's keys. auto_start is off by default; a server started by auto_start or `hermes hyatlas start` keeps running after Hermes exits until `hermes hyatlas stop`. On Windows, if a hyatlas-go.ps1 launcher is configured, `hermes hyatlas start/stop` runs it; the repo's sample launcher reads your Nous token from Hermes auth.json and points extraction at the Nous Portal. No telemetry."
 maintainer: tuancookiez-hub
 tier: community
 category: memory