gnosys 5.15.1 → 5.15.3

package/README.md

@@ -71,8 +71,8 @@ This package installs two binaries:
 | `gnosys_read` | Read a specific memory. |
 | `gnosys_search` | Search memories by keyword across all stores. |
 | `gnosys_list` | List memories across all stores, optionally filtered by category, tag, or store layer. |
-| `gnosys_add` | Add a new memory. |
-| `gnosys_add_structured` | Add a memory with structured input (no LLM needed). |
+| `gnosys_add_structured` | **Preferred for LLM agents.** Add a memory with structured fields you supply (title, category, tags, content) — makes no server-side LLM call. |
+| `gnosys_add` | Add a memory from raw text; the server's LLM structures it. For non-agent callers (scripts, cron) — agents should use `gnosys_add_structured`. |
 | `gnosys_tags` | List all tags in the registry, grouped by category. |
 | `gnosys_tags_add` | Add a new tag to the registry. |
 | `gnosys_reinforce` | Signal whether a memory was useful. |

package/dist/index.js

@@ -624,7 +624,7 @@ regTool("gnosys_list", "List memories across all stores, optionally filtered by
     }
 });
 // ─── Tool: gnosys_add ────────────────────────────────────────────────────
-regTool("gnosys_add", "Add a new memory. Accepts raw text — an LLM structures it into an atomic memory. Writes to the project store by default. Use store='personal' for cross-project knowledge, or store='global' to explicitly write to shared org knowledge.", {
+regTool("gnosys_add", "Add a new memory from raw text — the server's LLM structures it into an atomic memory. For non-agent callers (scripts, cron); if you are an LLM agent, use gnosys_add_structured instead to avoid a redundant server-side LLM call. Writes to the project store by default. Use store='personal' for cross-project knowledge, or store='global' to explicitly write to shared org knowledge.", {
     input: z
         .string()
         .describe("Raw text input. Can be a decision, concept, fact, observation, or any knowledge."),
@@ -738,7 +738,7 @@ regTool("gnosys_add", "Add a new memory. Accepts raw text — an LLM structures
     }
 });
 // ─── Tool: gnosys_add_structured ─────────────────────────────────────────
-regTool("gnosys_add_structured", "Add a memory with structured input (no LLM needed). Writes to the project store by default. Use store='global' to explicitly write to shared org knowledge.", {
+regTool("gnosys_add_structured", "Preferred for LLM agents: add a memory with structured fields you supply (title, category, tags, content) — makes no server-side LLM call. Writes to the project store by default. Use store='global' to explicitly write to shared org knowledge.", {
     title: z.string().describe("Memory title"),
     category: z.string().describe("Category directory name"),
     tags: z

package/dist/lib/embeddings.js

@@ -35,8 +35,10 @@ export class GnosysEmbeddings {
         const cacheDir = process.env.GNOSYS_CACHE_DIR ||
             path.join(process.env.HOME || process.env.USERPROFILE || "/tmp", ".cache", "gnosys");
         await fs.mkdir(cacheDir, { recursive: true });
-        // HF_HOME is the canonical env var in @huggingface/transformers v3+;
-        // keep TRANSFORMERS_CACHE set too for any tooling that still reads it.
+        // NOTE: @huggingface/transformers does NOT honor HF_HOME/TRANSFORMERS_CACHE
+        // for its Node file cache (that's the Python huggingface_hub convention).
+        // It caches under its own `env.cacheDir`, which we set below after import.
+        // We still export the env vars for any adjacent tooling that reads them.
         process.env.HF_HOME = cacheDir;
         process.env.TRANSFORMERS_CACHE = cacheDir;
         // Dynamic import — keeps @huggingface/transformers out of the main bundle.
@@ -45,13 +47,22 @@ export class GnosysEmbeddings {
         // Use `any` here so `tsc` succeeds even when the optional dep is not installed
         // (CI network-share-simulation job, fresh checkouts, etc.). The real type
         // is only needed at runtime when the package is present.
-        let pipeline;
+        // `any`: the optional dep may be absent at type-check time (see note above).
+        let transformers;
         try {
-            ({ pipeline } = await import("@huggingface/transformers"));
+            transformers = await import("@huggingface/transformers");
         }
         catch {
             throw new Error("Local embeddings require @huggingface/transformers. Install it with: npm install @huggingface/transformers");
         }
+        // `env.cacheDir` is the actual knob transformers.js uses for its on-disk
+        // model cache. Without it the model lands in the package's own
+        // node_modules/.cache (wiped on reinstall) and GNOSYS_CACHE_DIR is silently
+        // ignored — it does NOT honor HF_HOME/TRANSFORMERS_CACHE. Access by property
+        // (not destructuring) so a mocked module without `env` doesn't throw.
+        if (transformers.env)
+            transformers.env.cacheDir = cacheDir;
+        const pipeline = transformers.pipeline;
         this.pipeline = (await pipeline("feature-extraction", MODEL_NAME, {
             dtype: "q8",
         }));

package/dist/lib/rulesGen.js

@@ -35,7 +35,8 @@ This project uses **Gnosys** for persistent memory via MCP. Gnosys uses a centra
 
 ### Write automatically
 
-- When user says "remember", "memorize", "save this", "note this down", "don't forget" — call \`gnosys_add\`
+- **Always write with \`gnosys_add_structured\`** — you are an LLM, so structure the memory yourself (title, category, tags, content, relevance) and pass the explicit fields. Do NOT use the freeform \`gnosys_add\`: it makes the Gnosys server run a *second, redundant* LLM call to structure your text and adds an external provider-key dependency that can fail silently. \`gnosys_add_structured\` makes no server-side model call. (Freeform \`gnosys_add\` exists only for non-agent callers — cron jobs, scripts — that cannot structure text themselves.)
+- When user says "remember", "memorize", "save this", "note this down", "don't forget" — call \`gnosys_add_structured\`
 - When user states a decision or preference (even casually) — commit to \`decisions\` category
 - When user provides a spec or plan — commit BEFORE starting work
 - After significant implementation — commit findings and gotchas
@@ -47,7 +48,7 @@ This project uses **Gnosys** for persistent memory via MCP. Gnosys uses a centra
 |--------|------|
 | Find memories | \`gnosys_discover\` (metadata) → \`gnosys_read\` (content) |
 | Search | \`gnosys_hybrid_search\` (best), \`gnosys_federated_search\` (cross-project), \`gnosys_search\` (keyword), \`gnosys_ask\` (Q&A) |
-| Write | \`gnosys_add\` (freeform), \`gnosys_add_structured\` (explicit fields) |
+| Write | \`gnosys_add_structured\` (explicit fields — **always use this as an agent**; no server-side LLM call). \`gnosys_add\` (freeform) is for non-agent callers only. |
 | Update | \`gnosys_update\`, \`gnosys_reinforce\` (useful/not_relevant/outdated) |
 | Browse | \`gnosys_list\`, \`gnosys_lens\` (filtered), \`gnosys_tags\`, \`gnosys_graph\` |
 | Maintain | \`gnosys_maintain\`, \`gnosys_stale\`, \`gnosys_history\`, \`gnosys_dashboard\` |
@@ -63,7 +64,11 @@ This project uses **Gnosys** for persistent memory via MCP. Gnosys uses a centra
 
 ### Categories
 
-\`architecture\` · \`decisions\` · \`requirements\` · \`concepts\` · \`roadmap\` · \`landscape\` · \`open-questions\``;
+\`architecture\` · \`decisions\` · \`requirements\` · \`concepts\` · \`roadmap\` · \`landscape\` · \`open-questions\`
+
+### Keeping these instructions current
+
+This block is generated by Gnosys and can drift from the installed version. After upgrading Gnosys (or if guidance here looks stale), run \`gnosys sync\` to regenerate this section in every detected IDE rules file (CLAUDE.md, .cursor/rules, .codex). Your user preferences and project conventions are re-injected at the same time.`;
 }
 // ─── Content generation ─────────────────────────────────────────────────
 /**

package/dist/lib/syncCommand.js

@@ -30,7 +30,14 @@ export async function runSyncCommand(opts) {
             process.exitCode = 1;
             return;
         }
-        const resolvedTarget = target || identity.agentRulesTarget || "all";
+        // Default to "all": refresh every IDE rules file actually present in the
+        // project (detectAllTargets only touches existing files, never creating
+        // configs for unused IDEs). A project accumulates multiple IDEs over its
+        // life — bare `gnosys sync` must keep all of them current, not just the one
+        // recorded in agentRulesTarget at first setup. This matches the upgrade-time
+        // "sync registered projects" path, which already uses "all". Use
+        // `--target <ide>` to refresh a single file.
+        const resolvedTarget = target || "all";
         const results = await syncToTarget(centralDb, projectDir, resolvedTarget, identity.projectId);
         if (results.length === 0) {
             console.error("No targets found. Create a CLAUDE.md, .cursor/, or .codex/ directory first.");

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gnosys",
-  "version": "5.15.1",
+  "version": "5.15.3",
   "description": "Gnosys — Persistent Memory for AI Agents. Sandbox-first runtime, central SQLite brain, federated search, Dream Mode, Web Knowledge Base, Obsidian export.",
   "type": "module",
   "main": "dist/index.js",