@gamaze/hicortex 0.19.6 → 0.20.1

package/dist/telemetry.js

@@ -7,11 +7,11 @@
  *   v        — package version
  *   pv       — payload schema version
  *   mode     — server or client
- *   agent    — cc, pi, oc, or mixed (detected from session sources); OMITTED
- *              when the agent type is genuinely unknown (pre-flight abort — no
- *              transcripts read yet). The admin summary buckets a missing agent
- *              as "?", distinct from any real type, so an aborting Hermes/OC
- *              client is never miscounted as "cc".
+ *   agent    — cc, hermes, pi, oc, opencode, or mixed (detected from session
+ *              sources); OMITTED when the agent type is genuinely unknown
+ *              (pre-flight abort — no transcripts read yet). The admin summary
+ *              buckets a missing agent as "?", distinct from any real type, so
+ *              an aborting Hermes/OC client is never miscounted as "cc".
  *   mem      — total memory count
  *   lessons  — total lesson count
  *   lessonsGenerated — lessons created THIS run (server mode only; the per-run

package/dist/uninstall.js

@@ -234,6 +234,40 @@ async function runUninstall() {
     if ((0, claude_md_js_1.removeLessonsBlock)(CLAUDE_MD)) {
         console.log("  ✓ Removed Hicortex Learnings block from CLAUDE.md");
     }
+    // 6. Remove the Pi extension (#348). Guarded on the "hicortex" marker the
+    //    installer always ships — "hicortex.ts" is a plausible user filename,
+    //    and uninstall never deletes a file we did not write. Fail-soft when
+    //    absent (no Pi on the machine) or unreadable.
+    const piExtension = (0, node_path_1.join)((0, node_os_1.homedir)(), ".pi", "agent", "extensions", "hicortex.ts");
+    if ((0, node_fs_1.existsSync)(piExtension)) {
+        try {
+            if ((0, node_fs_1.readFileSync)(piExtension, "utf-8").toLowerCase().includes("hicortex")) {
+                (0, node_fs_1.unlinkSync)(piExtension);
+                console.log("  ✓ Removed Pi extension (~/.pi/agent/extensions/hicortex.ts)");
+            }
+            else {
+                console.log("  ⚠ Skipping ~/.pi/agent/extensions/hicortex.ts — not a Hicortex file, left untouched");
+            }
+        }
+        catch { /* unreadable — leave it */ }
+    }
+    // 7. Remove the opencode plugin (#347). Same marker guard — the plugins
+    //    directory is shared (third-party files live there too), and uninstall
+    //    never deletes a file we did not write. Fail-soft when absent (no
+    //    opencode on the machine) or unreadable.
+    const openCodePlugin = (0, node_path_1.join)((0, node_os_1.homedir)(), ".config", "opencode", "plugins", "hicortex.ts");
+    if ((0, node_fs_1.existsSync)(openCodePlugin)) {
+        try {
+            if ((0, node_fs_1.readFileSync)(openCodePlugin, "utf-8").toLowerCase().includes("hicortex")) {
+                (0, node_fs_1.unlinkSync)(openCodePlugin);
+                console.log("  ✓ Removed opencode plugin (~/.config/opencode/plugins/hicortex.ts)");
+            }
+            else {
+                console.log("  ⚠ Skipping ~/.config/opencode/plugins/hicortex.ts — not a Hicortex file, left untouched");
+            }
+        }
+        catch { /* unreadable — leave it */ }
+    }
     console.log(`\n✓ Uninstalled. Database preserved at ${HICORTEX_HOME}/hicortex.db`);
     console.log("  To remove all data: rm -rf ~/.hicortex");
 }

package/hermes-plugin/hicortex/README.md

@@ -78,7 +78,7 @@ hermes memory setup   # select "hicortex", enter the server URL/token when promp
 
 Run it once per profile if you use Hermes profiles. Hermes allows **one** external memory provider at a time, so disable Honcho (or any other) first, then restart the gateway.
 
-Config fields (`hicortex_url`, `default_project`, `recall_limit`, `privacy_filter`, `agent_name`) can also be written to `$HERMES_HOME/plugins/hicortex/config.json` directly. `agent_name` pins the per-agent context id for this profile (leave blank to auto-derive — see [Per-agent standing context](#per-agent-standing-context-013)). The auth token is a **secret** — set it via env, not the JSON file:
+Setup asks exactly two questions: the **server URL** and the **auth token**. Everything else has a correct default and is configured — if ever needed — directly in `$HERMES_HOME/plugins/hicortex/config.json`: `default_project` (blank = memories unattributed), `recall_limit` (default 5; sizes the tools and the legacy `/search` fallback only — the pushed recall index is sized by SERVER config `recallMaxItems`), `agent_name` (blank auto-derives from the running profile; pin it only for fleet re-installs — see [Per-agent standing context](#per-agent-standing-context-013)), and `mission_domains` (blank = off; an optional recall boost keyed to the server's domain vocabulary). The auth token is a **secret** — set it via env, not the JSON file:
 
 ```bash
 export HICORTEX_AUTH_TOKEN=hctx-<your-token>   # or your custom token
@@ -86,7 +86,7 @@ export HICORTEX_AUTH_TOKEN=hctx-<your-token>   # or your custom token
 
 Env overrides: `HICORTEX_URL`, `HICORTEX_AUTH_TOKEN`.
 
-> **`privacy_filter` is DEPRECATED** (plugin 0.7.2 / server 0.16.2). The server no longer filters on privacy — the `privacy` column is vestigial (stored, never filtered). The setting is still accepted for backward compatibility but is now a harmless no-op; setting it emits a one-time-per-process warning in the gateway log. For work/personal isolation, run a **separate Hicortex server** per scope rather than relying on in-server privacy filtering.
+> **`privacy_filter` is REMOVED from setup** (plugin 0.7.4; deprecated since 0.7.2 / server 0.16.2). The server no longer filters on privacy — the `privacy` column is vestigial (stored, never filtered) — so the setting was a no-op the setup flow still prompted for. New setups never see the question; existing config.json files that still carry the key are tolerated (one-time warning in the gateway log; safe to delete the line). For work/personal isolation, run a **separate Hicortex server** per scope rather than relying on in-server privacy filtering.
 
 ## Topology
 

package/hermes-plugin/hicortex/config.py

@@ -36,65 +36,25 @@ CONFIG_SCHEMA: list[dict[str, Any]] = [
         "key": "hicortex_auth_token",
         "label": "Auth token",
         "description": (
-            "Bearer token for the server. Omit (leave blank) when targeting "
-            "localhost — the server bypasses auth there. Default token: "
-            "hctx-default-token."
+            "Bearer token for the server. Leave blank when targeting "
+            "localhost — the server bypasses auth there. To find a remote "
+            "server's token, run `hicortex status` on the server machine "
+            "(or check ~/.hicortex/config.json there)."
         ),
         "secret": True,
         "env_var": "HICORTEX_AUTH_TOKEN",
     },
-    {
-        "key": "default_project",
-        "label": "Default project",
-        "description": "Optional project name to scope recall and capture.",
-        "required": False,
-    },
-    {
-        "key": "recall_limit",
-        "label": "Recall limit",
-        "description": (
-            "Max memories returned per recall (default 5). Applies to the "
-            "tools and the legacy pre-0.14 /search prefetch fallback only — "
-            "the pushed recall index is sized by SERVER config (recallMaxItems)."
-        ),
-        "default": "5",
-        "required": False,
-    },
-    {
-        "key": "privacy_filter",
-        "label": "Privacy filter (DEPRECATED)",
-        "description": (
-            "DEPRECATED since plugin 0.7.2 / server 0.16.2. The server no "
-            "longer filters on privacy — the column is vestigial. This setting "
-            "is now a harmless no-op: it is still accepted for backward "
-            "compat but ignored. For work/personal isolation, run a separate "
-            "Hicortex server per scope. (Historically: comma-separated privacy "
-            "levels to include, e.g. WORK,PERSONAL.)"
-        ),
-        "default": "WORK,PERSONAL",
-        "required": False,
-    },
-    {
-        "key": "agent_name",
-        "label": "Agent name (per-agent context)",
-        "description": (
-            "Identity sent as ?agent= when fetching the standing context layer, "
-            "so this profile gets its own context (0.13). Leave blank to "
-            "auto-derive from the running profile (HERMES_PROFILE / HERMES_HOME)."
-        ),
-        "required": False,
-    },
-    {
-        "key": "mission_domains",
-        "label": "Mission domains",
-        "description": (
-            "Comma-separated knowledge domains this agent works in (e.g. Health, "
-            "or Finance,Work). Recall boosts memories tagged into these domains "
-            "(soft — never excludes others). Pick from the domains in your "
-            "Hicortex config; leave blank for a general-purpose agent."
-        ),
-        "required": False,
-    },
+    # 0.7.6: setup asks ONLY url + token. default_project joined the
+    # config-only knobs (0.7.5 removed recall_limit / agent_name /
+    # mission_domains) after live-install feedback: "no human will understand
+    # what it is" — a memory-attribution bucket is not a setup question.
+    # Config-only knobs (set directly in config.json, all have correct
+    # defaults): default_project (blank = unattributed), recall_limit (5;
+    # tools + legacy fallback only — the pushed index is SERVER-sized via
+    # recallMaxItems), agent_name (blank auto-derives from the running
+    # profile), mission_domains (blank = off).
+    # privacy_filter was removed outright in 0.7.4 (dead since server 0.16.2;
+    # tolerated at load with a one-time warning if an old file carries it).
     # NOTE: recall-only plugin — no capture config. Capture is handled by the
     # nightly server-side reader of each agent's session store.
 ]
@@ -130,7 +90,8 @@ def load_config() -> Dict[str, Any]:
     # Defaults
     cfg.setdefault("hicortex_url", "http://localhost:8787")
     cfg.setdefault("recall_limit", 5)
-    cfg.setdefault("privacy_filter", "WORK,PERSONAL")
+    # No privacy_filter default — the setting is dead (see schema note) and
+    # must not be injected into new configs.
 
     # 0.16.2 deprecation: privacy_filter is a no-op now (server ignores privacy
     # entirely). Warn once per process if the profile explicitly sets it.

package/hermes-plugin/hicortex/plugin.yaml

@@ -1,6 +1,6 @@
 name: hicortex
-version: 0.7.3
-description: "Self-learning memory for Hermes agents — every session is distilled into lessons overnight, and your agent wakes up wiser. Pushes a compact per-turn recall index (lazy-loaded with hicortex_get), injects fresh lessons plus a per-agent standing context block, and exposes the full 9-tool memory surface (search, get, recent, ingest, lessons, index, graph, update, delete) via a shared Hicortex server. Stdlib-only."
+version: 0.7.8
+description: "Self-learning memory for Hermes agents — every session is distilled into lessons overnight, and your agent wakes up wiser. Pushes a compact per-turn recall index (lazy-loaded with hicortex_get), injects fresh lessons plus a per-agent standing context block, and exposes the full 9-tool memory surface (search, get, recent, ingest, lessons, index, graph, update, delete) via a shared Hicortex server. Stdlib-only. AFTER INSTALL: run `hermes memory setup`, select hicortex, enter the server URL + token (see the token env var description for where to find it)."
 pip_dependencies: []
 hooks: []
 requires_env:

package/hermes-plugin/hicortex/provider.py

@@ -224,7 +224,10 @@ class HicortexProvider(MemoryProvider):
             self._recall_limit = int(cfg.get("recall_limit", 5))
         except (TypeError, ValueError):
             self._recall_limit = 5
-        self._privacy = cfg.get("privacy_filter", "WORK,PERSONAL")
+        # privacy_filter removed (0.7.4): the server ignores privacy entirely;
+        # the dead setting is no longer read. _privacy stays at its inert
+        # default for the (equally ignored) wire parameter.
+        self._privacy = "WORK,PERSONAL"
         # #203 scope: declared knowledge domains for this role-bound agent
         # (e.g. a health-focused agent → Health). Soft affinity boost on
         # recall; never excludes.