superlocalmemory 4.1.21 → 4.1.22

package/.claude-plugin/marketplace.json

@@ -9,7 +9,7 @@
       "author": {
         "name": "Qualixar"
       },
-      "description": "Local-first agent memory + reversible context compression and KV cache, as an MCP server. 38-tool code profile with graph intelligence.",
+      "description": "Local-first agent memory + reversible context compression and KV cache, as an MCP server. Serves the 56-tool full profile by default; set SLM_MCP_PROFILE=code for the 38-tool code profile.",
       "homepage": "https://github.com/qualixar/superlocalmemory",
       "keywords": [
         "memory",
@@ -21,7 +21,7 @@
       "license": "AGPL-3.0-or-later",
       "name": "superlocalmemory",
       "source": "./plugin",
-      "version": "4.1.21"
+      "version": "4.1.22"
     },
     {
       "author": {
@@ -39,7 +39,7 @@
       "license": "AGPL-3.0-or-later",
       "name": "superlocalmemory-codex",
       "source": "./codex-plugin",
-      "version": "4.1.21"
+      "version": "4.1.22"
     }
   ]
 }

package/CHANGELOG.md

@@ -5,6 +5,117 @@ All notable changes to SuperLocalMemory will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [4.1.22] — Faster recall from the first second, memories that stay findable, deletes you can trust
+
+### Added
+
+- **Filter by exact tags.** `recall`, `search`, `list` and `slm recall/list`
+  take a tag filter, over MCP, HTTP and the daemon proxy. A tag filter searches
+  inside the tagged memories and says why a result is empty.
+- **Switch the embedding model without losing recall.** `slm embedder`
+  re-indexes in the background, keeps the previous vectors, gives way to
+  recall while it works, resumes after a crash and can roll back.
+- **Model recommendations for this computer.** A model catalogue with current
+  defaults and each local model's result in SLM's extraction test; the setup
+  wizard offers your installed Ollama models, best first, and `slm models` and
+  the dashboard suggest installed and recommended models.
+- **Every recall says whether its answer was checked**: supported,
+  unsupported or unjudged, and why.
+- **`slm db integrity` and `slm db repair`** show store health in five parts
+  and fix leftover rows, erased words, unfinished deletes and memories that
+  lost their searchable fact, with receipts and undo. A repair never brings
+  back anything that was erased, deleted or withheld.
+- **`slm corrections overtaken`** lists corrections SLM had only proposed
+  itself that a delete, replace or edit overtook; `restore-overtaken` puts one
+  back.
+- Older memories in an upgraded store are classified by kind once, on this
+  device, in the background.
+- SuperLocalMemory installs as a Cursor-format plugin for Grok Bot, with a
+  low-RAM profile for shared bot hosts and two skills for bots sharing one
+  computer.
+
+### Changed
+
+- **Recall is about 2.6 times faster, with the same answers.** On a copy of a
+  real store, typical recall went from 849 ms to 321 ms (slowest 5%: 1.2 s to
+  0.49 s), and on 124 held-out questions from 923 ms to 340 ms (slowest 5%:
+  2.0 s to 0.77 s). Every speed change returns the same top ten memories as
+  before on all 184 test questions.
+- **Fast from the first second after a start, and while you save.** The store
+  is read into memory once at start, graph rankings and stored vectors are
+  prepared in separate background processes, background work yields to a
+  running recall at fine grain, requests no longer open the database to check
+  the login setting, and several slow store queries now use indexes. On a
+  22,000-memory store with the answer check on, a recall every second and a
+  save every half second: recalls slower than 3 s went from 13 of 318 to 7 of
+  297, with none in the first minute after a start (3 before), and saves slower
+  than 1.5 s from 7 of 56 to 1 of 87.
+- **Background enrichment keeps up.** Saved memories finish enrichment while
+  you keep recalling, instead of waiting for a quiet moment that never came:
+  about six times as many per minute under steady recall.
+- **A stated rule answers a yes/no permission question.** "May the agent
+  publish without approval?" is answered by a memory that says "Never publish
+  until the owner approves", with the same answer-check threshold as before;
+  the answer says it came from a rule. A rule about one named thing does not
+  answer a general question.
+- A memory that says it corrects an earlier one keeps that suggestion when the
+  model's check is unsure.
+- Local models copy the extraction prompt's example into your memories no
+  more, and invent fewer dates and numbers (llama3.2: sources with a fact the
+  source did not support went from 36 to 22 of 102; gemma3:4b from 1 to 0;
+  qwen2.5:7b 6 before, 7 now).
+- A fresh install (and CI) starts in Mode A.
+- `slm --json` and MCP tool responses are no longer pretty-printed.
+
+### Fixed
+
+- **A note that looked like an older one no longer loses its searchable fact.**
+  Enrichment deleted a new memory's only fact when it resembled another
+  memory's, so notes that differed only in a number or a declared kind could
+  not be found a moment after saving. `slm db repair` gives existing ones back.
+- **A question that mentions a time like "recently" still finds an older
+  memory it matches**, instead of returning nothing.
+- **A memory you save stays findable while SLM's own guess that it updates an
+  older one waits for review.** Approving the guess retires the older memory;
+  rejecting it keeps both. In one real store this made 406 saved memories
+  findable again; how often the right memory comes first is unchanged.
+- **Saves are not refused when the computer briefly stalls**, and a save
+  acknowledged just before the service was killed is enriched as soon as it
+  restarts.
+- **Deleting and erasing.** Erasing a memory removes its words everywhere
+  (keyword index, journal, event previews, entity summaries, logs, soft-forget
+  copies, vectors kept for a model switch). Erasing a person also erases the
+  memories they corrected, and erasing a whole profile no longer stops partway.
+  A delete refused at the last moment no longer leaves a memory unfindable.
+  Deleting a profile moves its memories to default, still findable, linked and
+  correctable.
+- A save sees the people and things it just added, so it does not create them
+  twice; a cancelled save leaves no trace in recall's lookups.
+- A background computation that times out, or whose service was stopped, no
+  longer keeps running.
+- Two recalls at the same moment are both reranked.
+- Measurements like 2004.6 ms are kept as measurements, never turned into
+  dates.
+- Bounded Loops runs with a node that never ran (an approval or a join) are no
+  longer rejected, and a gate verdict must be a real true or false.
+- The first memory call after a fresh start waits for SLM to finish starting;
+  a tool call no longer waits 60 s when two starts race; stopping a daemon
+  stuck in start-up no longer hangs.
+- Windows: SLM notices a stopped daemon at once, and Codex and Claude Code
+  hooks run SLM's own command.
+- Linux hosts with no GPU install CPU-only torch.
+- The remote listener closes a connection that floods data before its first
+  request; which cached answers get re-checked can no longer be predicted from
+  outside this install.
+- Plugin listings state the tool counts they really serve; the Hermes plugin
+  reaches the new `slm models`, `slm corrections` and `slm embedder` commands.
+
+### Known issues
+
+- On very large stores under heavy saving, a few recalls can still take longer
+  than 3 s while the store is busy committing a large write.
+
+
 ## [4.1.21] — Recall that knows your project, and memories that stay findable
 
 ### Added

package/README.md

@@ -70,9 +70,9 @@ Real output from a fresh Mode A install, trimmed. Scores rank; they are not prob
 
 Five minutes: install, setup, recall, cache and compression.
 
-### The dashboard, on real 4.1.21
+### The dashboard
 
-Captured from a 4.1.21 install in Mode A, with Laya running on the Mac and a store of fictional project memories. Nothing is mocked: each verdict, score and timing is what SLM returned.
+Captured from a real install in Mode A, with Laya running on the Mac and a store of fictional project memories. Nothing is mocked: each verdict, score and timing is what SLM returned.
 
 | Memories that answer the question | Memories that do not: "I don't have that" |
 |---|---|
@@ -110,15 +110,58 @@ SLM is part of Qualixar's AI Reliability Engineering work: agent memory that is
 
 | Surface | What you get | Docs |
 |---|---|---|
-| Editor plugins | Claude Code, Codex, VS Code / Copilot, Antigravity, Hermes. Each ships 12 skills, 4 sub-agents and session hooks | [IDE setup](docs/ide-setup.md), [Hermes](docs/hermes.md) |
+| Editor plugins | Claude Code, Codex, VS Code / Copilot, Antigravity, Hermes. Each ships 14 skills, 4 sub-agents and session hooks | [IDE setup](docs/ide-setup.md), [Hermes](docs/hermes.md) |
 | `slm connect <ide>` | Writes the MCP config for 12 IDEs, including Cursor, Windsurf, Zed, JetBrains, Gemini CLI and Claude Desktop | [IDE setup](docs/ide-setup.md) |
 | MCP | stdio (`slm mcp`) or HTTP at `http://127.0.0.1:8765/mcp/`; profiles from 8 to 103 tools | [MCP tools](docs/mcp-tools.md) |
 | Framework adapters | LangGraph, LangChain, LlamaIndex, CrewAI, AutoGen, Semantic Kernel, Microsoft Agent Framework, Google ADK, OpenAI Agents | [Framework adapters](docs/framework-adapters.md) |
 | Python SDK and HTTP API | `MemoryEngine` in your code; the local REST API | [API reference](docs/api-reference.md) |
 | Auto-capture hooks | `slm hooks install` for Claude Code, `--agent codex` for Codex | [Auto-memory](docs/auto-memory.md) |
+| Cursor-format plugin (Grok Bot, Cursor) | A marketplace-distributed plugin — different from `slm connect cursor` above — that runs on a shared, memory-tight computer with no hooks or dashboard | See below |
 
 Claude Code memory in two commands: `claude plugin marketplace add qualixar/superlocalmemory`, then `claude plugin install superlocalmemory@qualixar`.
 
+### Grok Bot (and other Cursor-format plugin hosts)
+
+Grok Bot runs plugins in Cursor's format: a `.cursor-plugin/plugin.json` manifest, not the
+`.claude-plugin/` one Claude Code reads. SuperLocalMemory ships both from one source, so the
+plugin works on Grok Bot's shared, memory-constrained computer without any manual MCP setup.
+
+**Install:** add the `qualixar` marketplace (`.cursor-plugin/marketplace.json` at this repo's
+root) in Grok Bot's Plugins screen, then add `superlocalmemory`. No API key, no sign-in step —
+the server runs locally on the Grok Bot computer, so nothing goes to a memory SaaS.
+*(The MCP server starts as `uvx --from superlocalmemory==<version> slm mcp`: a pinned,
+on-PATH command, with `UV_TORCH_BACKEND=cpu` so a GPU-less Linux box never pulls PyTorch's CUDA
+wheel stack. The first start resolves the package once; the first recall downloads the local
+embedding model once.)*
+
+**Try it:** tell any bot *"Remember that our Q4 theme is agent reliability."* Then open a
+different bot and ask *"What's our Q4 theme?"*
+
+**What's shared and what isn't:** every write is attributed to `SLM_AGENT_ID=cursor_plugin` —
+that is attribution, not an access boundary. If your bots share one `SLM_DATA_DIR` (the default
+on one Grok Bot computer), they share one memory store: anything stored without an explicit
+`scope` is visible to any bot that can reach that store, the same way two terminal sessions on
+one laptop would see each other's files. Mark a fact `scope=global` only when every bot on that
+computer should see it; a bot that genuinely needs private memory needs its own `SLM_DATA_DIR`.
+See the `slm-bot-memory` skill (ships with this plugin) for the full model, including what
+should never be stored on a computer shared with other bots (secrets, keys, other people's
+personal data).
+
+**Tools:** this plugin sets `SLM_MCP_PROFILE=core` — 18 tools (`remember`, `recall`, `search`,
+session lifecycle, compression/cache, corrections) — deliberately smaller than the 56-tool
+default profile every other host gets, so a shared computer is not listing tool descriptions
+for tiers it will not use.
+
+**Resources — the lite bot-host profile:** this plugin also sets `SLM_RERANKER_ENABLED=false`,
+`SLM_RERANKER_IDLE_TIMEOUT=120` and `SLM_MAX_EMBEDDING_WORKERS=1` by default, because the box is
+"shared by every bot on it" with as little as 1.8-3.5 GiB free. Measured on macOS, warm, after
+one remember and one recall: about 390 MB resident with the reranker on (daemon + reranker
+worker + embedding worker) vs. about 190 MB with it off — recall still runs every other channel
+(BM25, semantic, entity graph, temporal, spreading activation, Hopfield) and fuses them, just
+without the cross-encoder re-ordering pass. Set `SLM_RERANKER_ENABLED=true` in the plugin's env
+block to trade that RAM back for ranking precision, or run `slm serve stop` when a bot is done
+with it.
+
 ## What developers use it for
 
 - **Persistent memory for Claude Code, Codex and Cursor.** Decisions, conventions, fixes and project context carry across sessions and across tools; confirmed rules and decisions load at session start.
@@ -133,7 +176,7 @@ Claude Code memory in two commands: `claude plugin marketplace add qualixar/supe
 
 ## Architecture
 
-![SuperLocalMemory 4.1.21 architecture: modes, eight-layer pipeline, governance, Scale Engine, SLM-Mesh, bounded loops](docs/assets/slm-4.1.21-architecture.svg)
+![SuperLocalMemory architecture: modes, eight-layer pipeline, governance, Scale Engine, SLM-Mesh, bounded loops](docs/assets/slm-4.1.21-architecture.svg)
 
 *SQLite + sqlite-vec are canonical; CozoDB and LanceDB are parity-gated projections; SLM-Mesh coordinates trusted peers rather than replicating a distributed database; connectors are opt-in.* [Architecture docs](docs/ARCHITECTURE.md).
 
@@ -148,12 +191,13 @@ Claude Code memory in two commands: `claude plugin marketplace add qualixar/supe
 | Standing rules | Confirmed rules (up to 10) and decisions (up to 5) load into every new agent session | [Memory kinds](docs/memory-kinds.md#standing-rules-at-session-start) |
 | Replace and correct | `--replaces <id>` retires an old fact, kept and undoable. Edits go through reviewed corrections with rollback | [Corrections](docs/reviewed-corrections.md) |
 | Time travel | `--as-of`, `--known-as-of`, `--valid-at`, and `--window 7d` or a date range | [Recall](docs/recall.md#time-travel) |
-| Recall filters | `--project`, `--saved-by`, `--about`, `--kind`; applied before the answer check | [Recall](docs/recall.md#narrowing-a-recall) |
-| Project-aware recall | New in 4.1.21: memories from your current project rank first, hiding nothing. `--project` narrows and says when nothing matched | [Recall](docs/recall.md) |
-| Summaries and saved views | New in 4.1.21: `slm summary session`, `day` or `project`, each citing its memory ids; `slm view create "Work log" "what did I ship" --window 7d`, then `slm view run` | [Summaries](docs/recall.md#summaries), [Views](docs/recall.md#saved-views) |
+| Recall filters | `--project`, `--saved-by`, `--about`, `--kind`, and exact tags with `--tag` (repeat it; `--tags-match all` or `any`); applied before the answer check, and an empty result says why | [Recall](docs/recall.md#narrowing-a-recall) |
+| Project-aware recall | Memories from your current project rank first, hiding nothing. `--project` narrows and says when nothing matched | [Recall](docs/recall.md) |
+| Summaries and saved views | `slm summary session`, `day` or `project`, each citing its memory ids; `slm view create "Work log" "what did I ship" --window 7d`, then `slm view run` | [Summaries](docs/recall.md#summaries), [Views](docs/recall.md#saved-views) |
 | Knowledge graph | Entities, aliases, scenes and timelines; Entity Explorer in the dashboard | [Architecture](docs/ARCHITECTURE.md) |
 | Code graph | Index a repo, then ask for blast radius, callers, review context and code search by meaning | [MCP tools](docs/mcp-tools.md) |
-| Modes and providers | A: no model calls. B: a model on this machine (Ollama by default, or another local OpenAI-compatible server). C: your own endpoint or a cloud provider. Multilingual embedders work | [Configuration](docs/configuration.md) |
+| Modes and providers | A: no model calls. B: a model on this machine (Ollama by default, or another local OpenAI-compatible server). C: your own endpoint or a cloud provider. Multilingual embedders work. `slm models` recommends models that fit this computer | [Configuration](docs/configuration.md) |
+| Switch the embedding model | `slm embedder switch MODEL` re-indexes every memory in the background while recall keeps working, then changes over in one step; `status`, `cancel` and `rollback` | [CLI reference](docs/cli-reference.md#embedding-models-and-store-health) |
 
 Recalled text is untrusted evidence: before it reaches a prompt, secrets are redacted, forged boundary markers neutralised and provenance attached, a defence against prompt injection through memory.
 
@@ -221,6 +265,7 @@ All of it fails open. [Optimize](docs/optimize-overview.md), [Proxy setup](docs/
 - **[Dashboard](docs/DASHBOARD-COVERAGE.md):** `slm dashboard`, 16 panes including Answer Check, Brain, Knowledge Graph, Governance, Optimize and Mesh Peers.
 - **Durable writes:** each save moves raw → queryable → enriching → complete with a receipt; a failed step keeps the raw evidence and retries. Saves under heavy load are queued, never refused.
 - **[Operations](docs/troubleshooting.md):** `slm doctor`, `status`, `health`, `restart`, `ops`; stuck operations are listed and resolved.
+- **Store health:** `slm db integrity` reports the store's health; `slm db repair` previews fixes for leftover rows, erased words, unfinished deletes and memories that lost their searchable fact, applies them with `--apply`, and undoes a run with `--undo`. It never brings back anything erased, deleted or withheld. [CLI reference](docs/cli-reference.md#embedding-models-and-store-health)
 
 ## MCP memory server: tool profiles
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "superlocalmemory",
-  "version": "4.1.21",
+  "version": "4.1.22",
   "description": "Local-first agent memory with MCP and an agent-native CLI. Documented clients include Claude Code, Cursor, and Windsurf.",
   "keywords": [
     "ai-memory",
@@ -78,8 +78,10 @@
     "scripts/preuninstall.js",
     ".claude-plugin/",
     "plugin/",
+    "plugin-src/skills/slm-bot-memory/SKILL.md",
     "plugin-src/skills/slm-cache/SKILL.md",
     "plugin-src/skills/slm-compress/SKILL.md",
+    "plugin-src/skills/slm-getting-started-bot/SKILL.md",
     "plugin-src/skills/slm-governance/SKILL.md",
     "plugin-src/skills/slm-graph/SKILL.md",
     "plugin-src/skills/slm-loop/SKILL.md",

package/plugin/.claude-plugin/plugin.json

@@ -3,7 +3,7 @@
     "name": "Qualixar",
     "url": "https://github.com/qualixar/superlocalmemory"
   },
-  "description": "Local-first agent memory + reversible context compression and KV cache, as an MCP server. 38-tool code profile with graph intelligence.",
+  "description": "Local-first agent memory + reversible context compression and KV cache, as an MCP server. Serves the 56-tool full profile by default; set SLM_MCP_PROFILE=code for the 38-tool code profile.",
   "displayName": "SuperLocalMemory",
   "keywords": [
     "memory",
@@ -15,5 +15,5 @@
   "mcpServers": "./.mcp.json",
   "name": "superlocalmemory",
   "repository": "https://github.com/qualixar/superlocalmemory",
-  "version": "4.1.21"
+  "version": "4.1.22"
 }

package/plugin/.cursor-plugin/plugin.json

@@ -0,0 +1,24 @@
+{
+  "author": {
+    "name": "Qualixar"
+  },
+  "description": "Local-first long-term memory for your agents and bots: remember, recall and session context stored on your own computer, with reversible compression and a cache for large tool outputs.",
+  "homepage": "https://github.com/qualixar/superlocalmemory",
+  "hooks": {
+    "hooks": {}
+  },
+  "keywords": [
+    "memory",
+    "long-term-memory",
+    "local-first",
+    "mcp",
+    "agents"
+  ],
+  "license": "AGPL-3.0-or-later",
+  "logo": "assets/logo.svg",
+  "mcpServers": "./mcp.cursor.json",
+  "name": "superlocalmemory",
+  "repository": "https://github.com/qualixar/superlocalmemory",
+  "skills": "./cursor-skills/",
+  "version": "4.1.22"
+}

package/plugin/CLAUDE.md

@@ -1,4 +1,4 @@
-<!-- BEGIN SuperLocalMemory v4.1.21 -->
+<!-- BEGIN SuperLocalMemory v4.1.22 -->
 
 ## SuperLocalMemory (SLM) — Agent Rules
 
@@ -40,6 +40,6 @@ slm-recall · slm-remember · slm-session · slm-status · slm-cache · slm-comp
 ### Subagents
 slm-memory-advisor (memory decisions, session hygiene, scope/profile guidance) · slm-optimize-advisor (context compression + KV cache) · slm-governance-advisor (scope/roles/compliance/GDPR)
 
-<!-- END SuperLocalMemory v4.1.21 -->
+<!-- END SuperLocalMemory v4.1.22 -->
 
-SuperLocalMemory v4.1.21 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v4.1.22 · Qualixar · AGPL-3.0-or-later

package/plugin/agents/slm-governance-advisor.md

@@ -77,4 +77,4 @@ slm-scope · slm-governance · slm-profile · slm-remember · slm-recall
 # What NOT to do
 Never session_init twice; never forget without dry-run preview; never store secrets; never bypass role checks; never claim an erasure succeeded without verifying via recall.
 
-SuperLocalMemory v4.1.21 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v4.1.22 · Qualixar · AGPL-3.0-or-later

package/plugin/agents/slm-loop-runner.md

@@ -68,4 +68,4 @@ assessment. The gate is the authority.
 
 ---
 
-SuperLocalMemory v4.1.21 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v4.1.22 · Qualixar · AGPL-3.0-or-later

package/plugin/agents/slm-memory-advisor.md

@@ -47,4 +47,4 @@ slm-recall · slm-remember · slm-session · slm-scope · slm-profile · slm-gov
 # What NOT to do
 Never session_init twice; never forget dry_run=False without reporting preview; never dump a whole file into remember; never invent a memory; never claim "saved" without success:true / clean CLI exit; never bypass scope or governance restrictions.
 
-SuperLocalMemory v4.1.21 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v4.1.22 · Qualixar · AGPL-3.0-or-later

package/plugin/agents/slm-optimize-advisor.md

@@ -41,4 +41,4 @@ slm-compress · slm-cache · slm-status · slm-profile
 # What NOT to do
 Never compress code-for-edit/JSON-to-parse/<500 chars; never store secrets/ccr_ids; never let optimize failure block/alter the task; never claim a specific savings %; never carry ccr_ids across profile switches.
 
-SuperLocalMemory v4.1.21 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v4.1.22 · Qualixar · AGPL-3.0-or-later

package/plugin/assets/logo.svg

@@ -0,0 +1,36 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 128 128" role="img" aria-labelledby="title desc">
+  <title id="title">SuperLocalMemory mark</title>
+  <desc id="desc">A local memory core represented by connected evidence nodes in a cyan and violet ring.</desc>
+  <defs>
+    <linearGradient id="slm-ring" x1="18" y1="18" x2="110" y2="110" gradientUnits="userSpaceOnUse">
+      <stop stop-color="#22d3ee"/>
+      <stop offset=".52" stop-color="#60a5fa"/>
+      <stop offset="1" stop-color="#a78bfa"/>
+    </linearGradient>
+    <linearGradient id="slm-core" x1="39" y1="37" x2="91" y2="91" gradientUnits="userSpaceOnUse">
+      <stop stop-color="#d9fbff"/>
+      <stop offset="1" stop-color="#c4b5fd"/>
+    </linearGradient>
+  </defs>
+  <circle cx="64" cy="64" r="58" fill="#07111f" stroke="url(#slm-ring)" stroke-width="4"/>
+  <path d="M33 51c4-15 16-25 31-25 20 0 35 16 35 36 0 17-12 31-28 35" fill="none" stroke="url(#slm-ring)" stroke-linecap="round" stroke-width="4"/>
+  <path d="M35 78c6 15 22 24 38 20 9-2 16-8 20-16" fill="none" stroke="url(#slm-ring)" stroke-linecap="round" stroke-width="4" opacity=".82"/>
+  <g fill="none" stroke="url(#slm-ring)" stroke-linecap="round" stroke-linejoin="round" stroke-width="3.5">
+    <path d="M43 55 58 45l14 10 13-8"/>
+    <path d="M43 55v18l15 9 14-9 13 8"/>
+    <path d="M58 45v37"/>
+    <path d="M72 55v18"/>
+  </g>
+  <g fill="url(#slm-core)" stroke="#07111f" stroke-width="2">
+    <circle cx="43" cy="55" r="6"/>
+    <circle cx="58" cy="45" r="6"/>
+    <circle cx="72" cy="55" r="6"/>
+    <circle cx="85" cy="47" r="6"/>
+    <circle cx="43" cy="73" r="6"/>
+    <circle cx="58" cy="82" r="6"/>
+    <circle cx="72" cy="73" r="6"/>
+    <circle cx="85" cy="81" r="6"/>
+  </g>
+  <circle cx="64" cy="64" r="8" fill="url(#slm-ring)"/>
+  <circle cx="64" cy="64" r="3" fill="#f8fafc"/>
+</svg>

package/plugin/cursor-skills/slm-bot-memory/SKILL.md

@@ -0,0 +1,139 @@
+---
+name: slm-bot-memory
+description: Cross-bot memory on a shared computer (Grok Bot, Cursor plugin, any host where several agents share one machine). Explains agent_id attribution vs. profile/scope access, how to namespace by agent_id + profile + scope, and what must never be written to memory. Read this before the first remember/recall on a new Grok-Bot-style host.
+when_to_use: |
+  - First session on a Grok Bot computer or any shared-bot host
+  - "Will my other bots see this memory?"
+  - "How do I keep this bot's notes separate from that one?"
+  - Deciding whether to store something that looks like a secret or personal data
+  - Setting up a second bot on a computer that already has SLM configured
+allowed-tools: remember, recall, search, session_init, switch_profile
+---
+
+# slm-bot-memory — Cross-Bot Memory on a Shared Host
+
+SuperLocalMemory ships as an MCP server. On a single-user laptop, one bot is
+the only thing talking to it. On a **shared-bot host** — Grok Bot's "one
+computer, shared by all your Bots" model, several Cursor windows, or any
+setup where more than one agent process points at the same install — several
+agents can reach the same memory store at once. This skill is about that
+case: what is actually isolated, what is not, and what must never be written
+regardless.
+
+---
+
+## Three things that sound like isolation and are not the same
+
+| Setting | What it controls | Does it hide memories from another bot? |
+|---|---|---|
+| `SLM_AGENT_ID` | **Attribution** — who gets credit for a memory in logs and summaries | **No.** It is metadata, never an authenticated principal (verified in `mcp/agent_context.py`'s own docstring). Any bot that can query the same store can read a memory written under a different `agent_id`. |
+| `SLM_DATA_DIR` (profile root) | **Which database file** the daemon opens | **Yes.** Two bots pointed at different `SLM_DATA_DIR` values have fully separate, independent memory stores — nothing is shared unless you explicitly configure sharing. |
+| `scope` (`personal` / `shared` / `global`, see `slm-scope`) | **Visibility inside one store**, between profiles that share that store | Only the way you set it. `personal` (the default) stays within the writing profile; `shared`/`global` are explicit, user-initiated opt-ins. |
+
+The practical rule: **`SLM_AGENT_ID` tells you who wrote something; `SLM_DATA_DIR`
+and `scope` decide who can read it.** If two bots on the same Grok Bot computer
+use the same `SLM_DATA_DIR` (the common case — it is a shared filesystem, and
+nothing in Grok Bot's plugin model points different bots at different data
+directories by default), they see each other's `personal`-scope memories too,
+the same way two terminal sessions on one laptop would. Giving two bots
+different `SLM_AGENT_ID` values does not change that — it only changes whose
+name shows up on the memory.
+
+If you need one bot's memories genuinely unreachable from another, that bot
+needs its **own `SLM_DATA_DIR`** (or its own profile within a store that has
+governance/roles configured — see `slm-governance`), not just its own
+`SLM_AGENT_ID`.
+
+---
+
+## Namespacing that actually works
+
+Use all three dimensions together, each for what it is good at:
+
+1. **`agent_id`** (`SLM_AGENT_ID` env, or the `agent_id` parameter on
+   `remember`/`recall` directly) — so a human or another agent reading
+   `get_memory_summary` or the stored facts later can tell which bot said
+   what. Set it to something stable and specific: `grok_bot_support`,
+   `grok_bot_release_notes`, not a generic `bot`.
+2. **`profile_id`** / `SLM_DATA_DIR` — the real isolation boundary. One
+   store per bot that genuinely needs privacy from the others.
+3. **`scope`** (see `slm-scope`) — inside a store two or more bots
+   legitimately share, keep writes `personal` by default and only promote to
+   `shared`/`global` when a fact is meant for every bot on that store.
+
+```
+remember(
+  content="Deploy window for the support bot is Tue/Thu 14:00-16:00 UTC",
+  tags="ops,schedule",
+  agent_id="grok_bot_support",
+  session_id="<sid>",
+)
+```
+
+```
+recall(
+  query="deploy window",
+  agent_id="grok_bot_support",
+  session_id="<sid>",
+)
+```
+
+Recall is not filtered by `agent_id` automatically — it is attribution on the
+written record, not a query filter. If you need "only what this bot wrote",
+say so in the query text or check the `saved_by`/attribution field on the
+results, the same way you would read any shared log.
+
+---
+
+## What never goes into memory, on any host
+
+This is not Grok-Bot-specific — it is the baseline for every SLM host — but
+it matters more here because a shared computer means a shared blast radius if
+it is violated:
+
+- **Secrets, API keys, tokens, passwords, certificates.** Never pass them to
+  `remember`, even "just this once" or "temporarily." If a fact needs to
+  reference that a credential exists, store the *fact of its existence and
+  where to rotate it*, never the value.
+- **Personal data about identifiable people** that was not already something
+  the user explicitly asked to be remembered about themselves (names,
+  emails, addresses, health, financial details of third parties).
+- **Anything from Grok Bot's shared filesystem you did not write yourself**
+  and were not asked to remember. "Files are visible to every Bot" on that
+  computer (Grok Bot's own docs) — a file being readable is not the same as
+  having permission to copy its contents into long-term memory that other
+  bots and later sessions will see.
+- **Command-line credentials.** Grok Bot's own docs note these are shared
+  across bots on the computer; SLM must not become a second, more durable
+  copy of them.
+
+If you are unsure whether something is a secret, treat it as one and ask the
+user before storing anything derived from it.
+
+---
+
+## Checklist for a new bot on an existing shared host
+
+1. Confirm `SLM_DATA_DIR` — is this bot meant to share the existing store, or
+   does it need its own? (`slm status` or `session_init` shows the active
+   store's identity.)
+2. Set a specific `SLM_AGENT_ID` for this bot before the first `remember`.
+3. Read `slm-scope` before writing anything with `scope="shared"` or
+   `scope="global"` — those are machine-wide, not just cross-bot.
+4. Read the "never goes into memory" list above once, out loud if you are
+   unsure, before the first write on this host.
+
+---
+
+## Related skills
+
+- `slm-getting-started-bot` — first-session setup for a headless bot host
+- `slm-scope` — the personal/shared/global visibility model this skill
+  namespaces on top of
+- `slm-profile` — switching the active workspace/tool-tier within one store
+- `slm-governance` — role-based access when a store has multiple human/bot
+  members and real access control, not just convention
+
+---
+
+*SuperLocalMemory v4.1.22 · Qualixar · AGPL-3.0-or-later*