superlocalmemory 4.2.5 → 4.2.6

package/codex-plugin/_GENERATED.md

@@ -2,7 +2,7 @@
 
 Built by `scripts/build-codex-plugin.mjs` from the single source in `plugin-src/`. Version stamped from `plugin-src/manifest.json`.
 
-Version: **4.2.5**
+Version: **4.2.6**
 
 ## Derived — do not edit by hand
 
@@ -20,6 +20,7 @@ Version: **4.2.5**
 - `agents/slm-loop-runner.md`
 - `agents/slm-memory-advisor.md`
 - `agents/slm-optimize-advisor.md`
+- `assets/icon.svg`
 - `commands/slm-loop.md`
 - `skills/slm-bot-memory/SKILL.md`
 - `skills/slm-cache/SKILL.md`

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

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

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

@@ -79,4 +79,4 @@ assessment. The gate is the authority.
 
 ---
 
-SuperLocalMemory v4.2.5 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v4.2.6 · Qualixar · AGPL-3.0-or-later

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

@@ -51,4 +51,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 switch the active profile unasked; 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.2.5 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v4.2.6 · Qualixar · AGPL-3.0-or-later

package/codex-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 hand a ccr_id to another agent.
 
-SuperLocalMemory v4.2.5 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v4.2.6 · Qualixar · AGPL-3.0-or-later

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

@@ -178,4 +178,4 @@ store every local bot on that computer can reach.
 
 ---
 
-*SuperLocalMemory v4.2.5 · Qualixar · AGPL-3.0-or-later*
+*SuperLocalMemory v4.2.6 · Qualixar · AGPL-3.0-or-later*

package/codex-plugin/skills/slm-cache/SKILL.md

@@ -144,4 +144,4 @@ These subcommands control daemon-level cache settings and bulk removal. They do
 
 ---
 
-SuperLocalMemory v4.2.5 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v4.2.6 · Qualixar · AGPL-3.0-or-later

package/codex-plugin/skills/slm-compress/SKILL.md

@@ -147,4 +147,4 @@ Content over 1 MB (1 000 000 bytes UTF-8) is processed but `reversible` is force
 
 ---
 
-SuperLocalMemory v4.2.5 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v4.2.6 · Qualixar · AGPL-3.0-or-later

package/codex-plugin/skills/slm-getting-started-bot/SKILL.md

@@ -194,4 +194,4 @@ quality on a shared box.
 
 ---
 
-*SuperLocalMemory v4.2.5 · Qualixar · AGPL-3.0-or-later*
+*SuperLocalMemory v4.2.6 · Qualixar · AGPL-3.0-or-later*

package/codex-plugin/skills/slm-governance/SKILL.md

@@ -20,7 +20,9 @@ SuperLocalMemory can run with named users and roles per workspace (company
 mode), keeps a compliance audit trail, applies a retention lifecycle, and ships
 GDPR export and erasure commands. This skill documents how an agent must behave
 in a governed workspace and what the governance tools really do. The MCP audit
-and retention tools are in the `power` tool set (see `slm-profile`).
+and retention tools are in the `power` tool set, not the default: if they are
+missing, tell the user to run `slm tools set power` and restart this app (see
+`slm-profile`). The `slm gdpr` and `slm team` commands work either way.
 
 ---
 
@@ -274,4 +276,4 @@ Before running any destructive or state-changing operation (`forget`,
 
 ---
 
-*SuperLocalMemory v4.2.5 · Qualixar · AGPL-3.0-or-later*
+*SuperLocalMemory v4.2.6 · Qualixar · AGPL-3.0-or-later*

package/codex-plugin/skills/slm-graph/SKILL.md

@@ -20,7 +20,7 @@ allowed-tools: build_code_graph, query_graph, get_blast_radius, semantic_search_
 
 # slm-graph — Code Intelligence Skill
 
-Index any repo as a code knowledge graph and answer structural questions about it: callers, callees, impact radius, semantic search, and review context. These tools are only registered in the `code` MCP tool set (or with `SLM_MCP_ALL_TOOLS=1`); see "Tool set requirement" below.
+Index any repo as a code knowledge graph and answer structural questions about it: callers, callees, impact radius, semantic search, and review context. These tools are not in the default tool set: they need `slm tools set code` (or `whole`); see "Tool set requirement" below.
 
 **Prerequisite rule:** every tool except `build_code_graph` self-guards — if the graph is not built it returns `{"success": false, "error": "Code graph not built. Run build_code_graph first."}`. Always index first.
 
@@ -289,17 +289,11 @@ If `build_code_graph` returns `files_parsed: 0`, no supported source files were
 The six tools above are registered only when the MCP server runs the `code` tool
 set, or with `SLM_MCP_ALL_TOOLS=1` / `SLM_MCP_PROFILE=whole`, or when
 `SLM_MCP_TOOLS` names them. They are **not** in `core`, `full`, `power` or the
-no-profile default that the Claude Code and Codex plugins use, so with those
-settings the tools simply do not exist and a call fails as an unknown tool. The
-tool set is read when the server starts: set it in the host's MCP config and
-restart the host.
-
-```json
-"env": {
-  "SLM_MCP_PROFILE": "code",
-  "SLM_AGENT_ID": "codex"
-}
-```
+default every app gets, so there the tools do not exist and a call fails as an
+unknown tool. If the user asks for graph work and the tools are missing, tell
+them: "Code-graph tools are off by default. Run `slm tools set code` (graph
+without mesh) or `slm tools set whole` (every tool), then restart this app."
+Let them choose; it changes the tools every connected app sees.
 
 `switch_profile` does not change the tool set; it changes the active memory
 profile. See `slm-profile`. The `code` set leaves out the mesh and several
@@ -324,4 +318,4 @@ All are host-only: a remote caller cannot use them.
 
 ---
 
-SuperLocalMemory v4.2.5 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v4.2.6 · Qualixar · AGPL-3.0-or-later

package/codex-plugin/skills/slm-loop/SKILL.md

@@ -171,4 +171,4 @@ Guides: `docs/skill-evolution.md`, `docs/bounded-loops-bridge.md`.
 
 ---
 
-SuperLocalMemory v4.2.5 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v4.2.6 · Qualixar · AGPL-3.0-or-later

package/codex-plugin/skills/slm-media/SKILL.md

@@ -337,4 +337,4 @@ minutes (previous vectors are kept) and let them decide.
 
 ---
 
-*SuperLocalMemory v4.2.5 · Qualixar · AGPL-3.0-or-later*
+*SuperLocalMemory v4.2.6 · Qualixar · AGPL-3.0-or-later*

package/codex-plugin/skills/slm-mesh/SKILL.md

@@ -386,4 +386,4 @@ mesh availability.
 
 ---
 
-*SuperLocalMemory v4.2.5 · Qualixar · AGPL-3.0-or-later*
+*SuperLocalMemory v4.2.6 · Qualixar · AGPL-3.0-or-later*

package/codex-plugin/skills/slm-profile/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: slm-profile
-description: Memory profiles (separate namespaces inside one SuperLocalMemory store) and MCP tool sets (which tools your host sees). Use switch_profile or slm profile switch to change the active memory profile, the profile_id argument to read or write another profile for one call, and SLM_MCP_PROFILE to choose a tool set. Required when working across multiple projects, clients, or tenants.
+description: Memory profiles (separate namespaces inside one SuperLocalMemory store) and MCP tool sets (which tools your host sees). Use switch_profile or slm profile switch to change the active memory profile, the profile_id argument to read or write another profile for one call, and `slm tools set <name>` to choose the tool set every connected app sees. Required when working across multiple projects, clients, or tenants.
 when_to_use: |
   - "Switch to my work profile"
   - "What profile am I currently in?"
@@ -97,14 +97,15 @@ named differently (for example `superlocalmemory-personal` and
 
 | Profile | Tools | What it is |
 |---------|-------|------------|
-| `core` | 19 tools — remember, recall, search, fetch, expand, list_recent, update_memory, forget, session, optimize, corrections, summaries, switch_profile | Smallest set; the Grok Bot / Cursor plugin uses it |
+| `core` | 19 tools — remember, recall, search, fetch, expand, list_recent, update_memory, forget, session, optimize, corrections, summaries, switch_profile | Smallest set |
 | `code` | 39 tools — core + portable Brain evidence, report_outcome/report_feedback, 6 code-graph tools, memory kinds, bounded loops | For coding agents that need the graph; no mesh, no `get_status` |
-| `full` | 58 tools — everyday memory, delete_memory, get_status, observe, saved views, learning tools, skills, optimize, kinds, loops, mesh | Same set as the no-profile default |
+| `full` | 58 tools — everyday memory, delete_memory, get_status, observe, saved views, learning tools, skills, optimize, kinds, loops, mesh | The default for every app |
 | `power` | 70 tools — full + audit_trail, retention, compaction, consistency_check, behavioral and diagnostic tools | Governance and admin work |
 | `mesh` | 9 tools — mesh coordination only | Lightweight cross-session signalling |
 
-A host that sets no profile gets the 58-tool `full` set (this is what the Claude
-Code and Codex plugins do; the Antigravity plugin sets `power`). While pictures
+Every app gets the 58-tool `full` set unless the user chose another: no plugin
+or extension SuperLocalMemory ships sets one. It fits hosts that cap the total
+number of MCP tools at about 100. While pictures
 and documents are on (`slm media status`), `full` lists 62 tools and `power` 74:
 the five picture tools `remember_media`, `get_media`, `remember_document`,
 `media_status` and `media_upload_link` are added to both, and never to `core`,
@@ -117,19 +118,19 @@ such as `core_memory` and `settle_session_outcomes` exist only with
 `SLM_MCP_ALL_TOOLS=1`, `whole` or an explicit `SLM_MCP_TOOLS` list. Tools whose
 function is to manage the SLM computer are never available to a remote caller.
 
-The tool set is read when the MCP server starts. To change it, set it in the
-host's MCP config and restart the host; asking the server at runtime does not
-work:
+The tool set is read when the MCP server starts. To change it for every app at
+once, the user runs one command and then restarts their apps (or reconnects
+them in Dashboard → Connected apps); asking the server at runtime does not work:
 
-```json
-"env": {
-  "SLM_MCP_PROFILE": "code",
-  "SLM_AGENT_ID": "codex"
-}
+```bash
+slm tools                 # the current set and how many tools each set has
+slm tools set power       # core, code, full, power, mesh or whole
+slm tools set default     # back to full
 ```
 
-`slm connect <ide> --profile <name>` writes that variable into a supported
-host's config. Setting `SLM_MCP_PROFILE` to a name that does not exist stops
+An app whose own MCP config sets `SLM_MCP_PROFILE` keeps that value: it wins
+over the saved choice, for that app only (`slm connect <ide> --profile <name>`
+writes it). Setting `SLM_MCP_PROFILE` to a name that does not exist stops
 `slm mcp` with a message listing the valid names. Older count-suffixed names
 such as `code20`, `full38` and `power50` still resolve, with a startup warning.
 On an install that already has memories, do not set `SLM_DATA_DIR` in the MCP
@@ -142,8 +143,10 @@ set. It is not in `mesh`.
 
 ## If a tool is missing
 
-Check the tool set first (`slm status` does not show it; look at the host's MCP
-config for `SLM_MCP_PROFILE`). Mesh tools need `full`, `power`, `mesh` or the
+Check the tool set first: `slm tools` shows it (an app's own `SLM_MCP_PROFILE`,
+if set, overrides it for that app). Tell the user which set has the tool and
+the command, for example "run `slm tools set power` and restart this app", and
+let them decide; widening the set adds tools to every connected app. Mesh tools need `full`, `power`, `mesh` or the
 default. Picture and PDF tools need `full`, `power` or `whole` and the feature
 turned on (`slm media enable`). Code-graph tools need `code` or `SLM_MCP_ALL_TOOLS=1`. Audit and
 retention tools need `power`. `report_outcome` and `report_feedback` need
@@ -161,4 +164,4 @@ anything but `core` or `mesh`.
 
 ---
 
-*SuperLocalMemory v4.2.5 · Qualixar · AGPL-3.0-or-later*
+*SuperLocalMemory v4.2.6 · Qualixar · AGPL-3.0-or-later*

package/codex-plugin/skills/slm-recall/SKILL.md

@@ -515,4 +515,4 @@ See `slm-profile`.
 
 ---
 
-*SuperLocalMemory v4.2.5 · Qualixar · AGPL-3.0-or-later*
+*SuperLocalMemory v4.2.6 · Qualixar · AGPL-3.0-or-later*

package/codex-plugin/skills/slm-remember/SKILL.md

@@ -372,4 +372,4 @@ sessions on this machine, so use it only when the user asks to move. See
 
 ---
 
-*SuperLocalMemory v4.2.5 · Qualixar · AGPL-3.0-or-later*
+*SuperLocalMemory v4.2.6 · Qualixar · AGPL-3.0-or-later*

package/codex-plugin/skills/slm-scope/SKILL.md

@@ -180,4 +180,4 @@ to review the impact. See `slm-remember` for the full deletion discipline.
 
 ---
 
-*SuperLocalMemory v4.2.5 · Qualixar · AGPL-3.0-or-later*
+*SuperLocalMemory v4.2.6 · Qualixar · AGPL-3.0-or-later*

package/codex-plugin/skills/slm-session/SKILL.md

@@ -288,4 +288,4 @@ answered. To also surface shared or global facts, call `recall` with
 
 ---
 
-*SuperLocalMemory v4.2.5 · Qualixar · AGPL-3.0-or-later*
+*SuperLocalMemory v4.2.6 · Qualixar · AGPL-3.0-or-later*

package/codex-plugin/skills/slm-status/SKILL.md

@@ -228,4 +228,4 @@ the memory-engine upgrade is pending.
 
 ---
 
-SuperLocalMemory v4.2.5 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v4.2.6 · Qualixar · AGPL-3.0-or-later

package/copilot-plugin/.github/agents/slm-governance-advisor.agent.md

@@ -9,7 +9,7 @@ description: >
 tools: recall, search, remember, update_memory, list_recent, Read, Bash
 model: inherit
 target: vscode
-version: "4.2.5"
+version: "4.2.6"
 ---
 
 # Role
@@ -83,4 +83,4 @@ slm-scope · slm-governance · slm-profile · slm-remember · slm-recall · slm-
 # What NOT to do
 Never session_init twice; never forget without dry-run preview; never run `slm gdpr erase --yes` unasked; never store secrets; never bypass role checks; never claim an erasure succeeded without verifying via recall.
 
-SuperLocalMemory v4.2.5 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v4.2.6 · Qualixar · AGPL-3.0-or-later

package/copilot-plugin/.github/agents/slm-loop-runner.agent.md

@@ -11,7 +11,7 @@ description: >
 tools: Bash, recall, remember, Read, slm_loop_run, slm_loop_history, slm_loop_show
 model: inherit
 target: vscode
-version: "4.2.5"
+version: "4.2.6"
 ---
 
 # Role
@@ -81,4 +81,4 @@ assessment. The gate is the authority.
 
 ---
 
-SuperLocalMemory v4.2.5 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v4.2.6 · Qualixar · AGPL-3.0-or-later

package/copilot-plugin/.github/agents/slm-memory-advisor.agent.md

@@ -8,7 +8,7 @@ description: >
 tools: session_init, recall, search, remember, update_memory, forget, list_recent, Read
 model: inherit
 target: vscode
-version: "4.2.5"
+version: "4.2.6"
 ---
 
 # Role
@@ -53,4 +53,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 switch the active profile unasked; 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.2.5 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v4.2.6 · Qualixar · AGPL-3.0-or-later

package/copilot-plugin/.github/agents/slm-optimize-advisor.agent.md

@@ -9,7 +9,7 @@ description: >
 tools: slm_compress, slm_retrieve, slm_cache_set, slm_cache_get, slm_optimize_stats, Read, Bash
 model: inherit
 target: vscode
-version: "4.2.5"
+version: "4.2.6"
 ---
 
 # Role
@@ -43,4 +43,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 hand a ccr_id to another agent.
 
-SuperLocalMemory v4.2.5 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v4.2.6 · Qualixar · AGPL-3.0-or-later

package/copilot-plugin/.github/copilot-instructions.md

@@ -1,7 +1,7 @@
 <!-- SLM-START -->
-<!-- SuperLocalMemory v4.2.5 — managed block. Edit outside these markers; this section is regenerated. -->
+<!-- SuperLocalMemory v4.2.6 — managed block. Edit outside these markers; this section is regenerated. -->
 
-<!-- BEGIN SuperLocalMemory v4.2.5 -->
+<!-- BEGIN SuperLocalMemory v4.2.6 -->
 
 ## SuperLocalMemory (SLM) — Agent Rules
 
@@ -54,8 +54,8 @@ 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) · slm-loop-runner (bounded, gate-verified loops)
 
-<!-- END SuperLocalMemory v4.2.5 -->
+<!-- END SuperLocalMemory v4.2.6 -->
 
-SuperLocalMemory v4.2.5 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v4.2.6 · Qualixar · AGPL-3.0-or-later
 
 <!-- SLM-END -->

package/copilot-plugin/.github/prompts/slm-bot-memory.prompt.md

@@ -1,7 +1,7 @@
 ---
 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.
-version: "4.2.5"
+version: "4.2.6"
 agent: agent
 tools:
   - remember
@@ -177,4 +177,4 @@ store every local bot on that computer can reach.
 
 ---
 
-*SuperLocalMemory v4.2.5 · Qualixar · AGPL-3.0-or-later*
+*SuperLocalMemory v4.2.6 · Qualixar · AGPL-3.0-or-later*

package/copilot-plugin/.github/prompts/slm-cache.prompt.md

@@ -1,7 +1,7 @@
 ---
 name: slm-cache
 description: KV cache for repeated reads — call slm_cache_get(key) first; on a miss do the expensive operation then slm_cache_set(key, value, ttl_seconds) to store it; on a hit use the returned value directly; always fail-open (hit:false on any error, never raises); saves tokens when the same file, query result, or tool output is read more than once in a session.
-version: "4.2.5"
+version: "4.2.6"
 agent: agent
 tools:
   - slm_cache_set
@@ -148,4 +148,4 @@ These subcommands control daemon-level cache settings and bulk removal. They do
 
 ---
 
-SuperLocalMemory v4.2.5 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v4.2.6 · Qualixar · AGPL-3.0-or-later

package/copilot-plugin/.github/prompts/slm-compress.prompt.md

@@ -1,7 +1,7 @@
 ---
 name: slm-compress
 description: Compress large text, tool output, or transcripts to reduce context-window usage while keeping the full 1M window intact — call slm_compress(content, mode, reversible, ttl_seconds) to shrink content; if the result is lossy a ccr_id is returned so you can call slm_retrieve(ccr_id) later to recover the exact original; always fail-open (ok:false → continue with the original).
-version: "4.2.5"
+version: "4.2.6"
 agent: agent
 tools:
   - slm_compress
@@ -151,4 +151,4 @@ Content over 1 MB (1 000 000 bytes UTF-8) is processed but `reversible` is force
 
 ---
 
-SuperLocalMemory v4.2.5 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v4.2.6 · Qualixar · AGPL-3.0-or-later

package/copilot-plugin/.github/prompts/slm-getting-started-bot.prompt.md

@@ -1,7 +1,7 @@
 ---
 name: slm-getting-started-bot
 description: First-session orientation for SuperLocalMemory on a headless bot host (Grok Bot, or any Cursor-format plugin install with no hooks, no dashboard, and no interactive setup wizard). What is different here vs. Claude Code/Codex, which 19 tools are actually available, and the first three calls to make.
-version: "4.2.5"
+version: "4.2.6"
 agent: agent
 tools:
   - session_init
@@ -193,4 +193,4 @@ quality on a shared box.
 
 ---
 
-*SuperLocalMemory v4.2.5 · Qualixar · AGPL-3.0-or-later*
+*SuperLocalMemory v4.2.6 · Qualixar · AGPL-3.0-or-later*

package/copilot-plugin/.github/prompts/slm-governance.prompt.md

@@ -1,7 +1,7 @@
 ---
 name: slm-governance
 description: Governed-workspace behavior for SuperLocalMemory. Covers roles (admin/member/viewer) and company mode, who administers a company-mode workspace (a signed-in admin, or `slm team` on the SLM computer), `slm token show` in strict mode, what remote web apps can never see or change, retention and lifecycle settings, the audit trail, GDPR export and erasure, and how agents must behave when operating under workspace governance. The audit and retention tools need the power MCP profile. Agents must never bypass governance controls.
-version: "4.2.5"
+version: "4.2.6"
 agent: agent
 tools:
   - audit_trail
@@ -22,7 +22,9 @@ SuperLocalMemory can run with named users and roles per workspace (company
 mode), keeps a compliance audit trail, applies a retention lifecycle, and ships
 GDPR export and erasure commands. This skill documents how an agent must behave
 in a governed workspace and what the governance tools really do. The MCP audit
-and retention tools are in the `power` tool set (see `slm-profile`).
+and retention tools are in the `power` tool set, not the default: if they are
+missing, tell the user to run `slm tools set power` and restart this app (see
+`slm-profile`). The `slm gdpr` and `slm team` commands work either way.
 
 ---
 
@@ -276,4 +278,4 @@ Before running any destructive or state-changing operation (`forget`,
 
 ---
 
-*SuperLocalMemory v4.2.5 · Qualixar · AGPL-3.0-or-later*
+*SuperLocalMemory v4.2.6 · Qualixar · AGPL-3.0-or-later*

package/copilot-plugin/.github/prompts/slm-graph.prompt.md

@@ -1,7 +1,7 @@
 ---
 name: slm-graph
 description: >
-version: "4.2.5"
+version: "4.2.6"
 agent: agent
 tools:
   - build_code_graph
@@ -15,7 +15,7 @@ tools:
 
 # slm-graph — Code Intelligence Skill
 
-Index any repo as a code knowledge graph and answer structural questions about it: callers, callees, impact radius, semantic search, and review context. These tools are only registered in the `code` MCP tool set (or with `SLM_MCP_ALL_TOOLS=1`); see "Tool set requirement" below.
+Index any repo as a code knowledge graph and answer structural questions about it: callers, callees, impact radius, semantic search, and review context. These tools are not in the default tool set: they need `slm tools set code` (or `whole`); see "Tool set requirement" below.
 
 **Prerequisite rule:** every tool except `build_code_graph` self-guards — if the graph is not built it returns `{"success": false, "error": "Code graph not built. Run build_code_graph first."}`. Always index first.
 
@@ -284,17 +284,11 @@ If `build_code_graph` returns `files_parsed: 0`, no supported source files were
 The six tools above are registered only when the MCP server runs the `code` tool
 set, or with `SLM_MCP_ALL_TOOLS=1` / `SLM_MCP_PROFILE=whole`, or when
 `SLM_MCP_TOOLS` names them. They are **not** in `core`, `full`, `power` or the
-no-profile default that the Claude Code and Codex plugins use, so with those
-settings the tools simply do not exist and a call fails as an unknown tool. The
-tool set is read when the server starts: set it in the host's MCP config and
-restart the host.
-
-```json
-"env": {
-  "SLM_MCP_PROFILE": "code",
-  "SLM_AGENT_ID": "claude_code"
-}
-```
+default every app gets, so there the tools do not exist and a call fails as an
+unknown tool. If the user asks for graph work and the tools are missing, tell
+them: "Code-graph tools are off by default. Run `slm tools set code` (graph
+without mesh) or `slm tools set whole` (every tool), then restart this app."
+Let them choose; it changes the tools every connected app sees.
 
 `switch_profile` does not change the tool set; it changes the active memory
 profile. See `slm-profile`. The `code` set leaves out the mesh and several
@@ -319,4 +313,4 @@ All are host-only: a remote caller cannot use them.
 
 ---
 
-SuperLocalMemory v4.2.5 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v4.2.6 · Qualixar · AGPL-3.0-or-later

package/copilot-plugin/.github/prompts/slm-loop.prompt.md

@@ -1,7 +1,7 @@
 ---
 name: slm-loop
 description: Gate-verified bounded loops with SuperLocalMemory as the durable ledger. Use when a task has a checkable acceptance condition and you must iterate until an INDEPENDENT gate passes — never stopping because the agent believes it is done. `slm_loop_run` (MCP) waits, under hard bounds, for an independently executed check registered by the operator to pass; `slm loop demo` shows the control flow keyless; `slm loop history` and `slm loop show <run_id>` (or `slm_loop_history` / `slm_loop_show`) inspect past runs, whose every lap is stored as queryable SLM memory (tag `loop:<name>`). Terminal statuses are DONE / HALT / PAUSE / KILLED / ERROR — report them exactly, never converting HALT/PAUSE/ERROR into success.
-version: "4.2.5"
+version: "4.2.6"
 agent: agent
 tools:
   - slm_loop_run
@@ -183,4 +183,4 @@ Guides: `docs/skill-evolution.md`, `docs/bounded-loops-bridge.md`.
 
 ---
 
-SuperLocalMemory v4.2.5 · Qualixar · AGPL-3.0-or-later
+SuperLocalMemory v4.2.6 · Qualixar · AGPL-3.0-or-later

package/copilot-plugin/.github/prompts/slm-media.prompt.md

@@ -1,7 +1,7 @@
 ---
 name: slm-media
 description: Save pictures and PDFs in SuperLocalMemory and find them again by describing them. Covers when to save a picture or document, remember_media, remember_document, get_media, media_status and media_upload_link, how recall returns pictures and PDF pages, the limits, what stays private, turning the feature on with `slm media` (16 GB of memory needed), connecting folders with `slm sources`, and how web apps add files through one-time upload links. Off by default.
-version: "4.2.5"
+version: "4.2.6"
 agent: agent
 tools:
   - remember_media
@@ -338,4 +338,4 @@ minutes (previous vectors are kept) and let them decide.
 
 ---
 
-*SuperLocalMemory v4.2.5 · Qualixar · AGPL-3.0-or-later*
+*SuperLocalMemory v4.2.6 · Qualixar · AGPL-3.0-or-later*

package/copilot-plugin/.github/prompts/slm-mesh.prompt.md

@@ -1,7 +1,7 @@
 ---
 name: slm-mesh
 description: Cross-session peer coordination via the SLM mesh network. Lets multiple AI agent sessions on the same machine, and web apps the owner has allowed (ChatGPT, Claude on the web, Grok Bot, Muse, Composio), discover each other, send messages, wait for replies with mesh_wait, share lightweight state, and lock files to avoid conflicts. Covers the at-least-once delivery rule for web apps (pass ack_ids back as ack) and the two permissions a web app needs. Available in the default tool set and in the full, power and mesh MCP profiles. Only `slm mesh status` and `slm mesh peers` exist on the command line; the other tools are MCP-only.
-version: "4.2.5"
+version: "4.2.6"
 agent: agent
 tools:
   - mesh_summary
@@ -387,4 +387,4 @@ mesh availability.
 
 ---
 
-*SuperLocalMemory v4.2.5 · Qualixar · AGPL-3.0-or-later*
+*SuperLocalMemory v4.2.6 · Qualixar · AGPL-3.0-or-later*

package/copilot-plugin/.github/prompts/slm-profile.prompt.md

@@ -1,7 +1,7 @@
 ---
 name: slm-profile
-description: Memory profiles (separate namespaces inside one SuperLocalMemory store) and MCP tool sets (which tools your host sees). Use switch_profile or slm profile switch to change the active memory profile, the profile_id argument to read or write another profile for one call, and SLM_MCP_PROFILE to choose a tool set. Required when working across multiple projects, clients, or tenants.
-version: "4.2.5"
+description: Memory profiles (separate namespaces inside one SuperLocalMemory store) and MCP tool sets (which tools your host sees). Use switch_profile or slm profile switch to change the active memory profile, the profile_id argument to read or write another profile for one call, and `slm tools set <name>` to choose the tool set every connected app sees. Required when working across multiple projects, clients, or tenants.
+version: "4.2.6"
 agent: agent
 tools:
   - switch_profile
@@ -93,14 +93,15 @@ named differently (for example `superlocalmemory-personal` and
 
 | Profile | Tools | What it is |
 |---------|-------|------------|
-| `core` | 19 tools — remember, recall, search, fetch, expand, list_recent, update_memory, forget, session, optimize, corrections, summaries, switch_profile | Smallest set; the Grok Bot / Cursor plugin uses it |
+| `core` | 19 tools — remember, recall, search, fetch, expand, list_recent, update_memory, forget, session, optimize, corrections, summaries, switch_profile | Smallest set |
 | `code` | 39 tools — core + portable Brain evidence, report_outcome/report_feedback, 6 code-graph tools, memory kinds, bounded loops | For coding agents that need the graph; no mesh, no `get_status` |
-| `full` | 58 tools — everyday memory, delete_memory, get_status, observe, saved views, learning tools, skills, optimize, kinds, loops, mesh | Same set as the no-profile default |
+| `full` | 58 tools — everyday memory, delete_memory, get_status, observe, saved views, learning tools, skills, optimize, kinds, loops, mesh | The default for every app |
 | `power` | 70 tools — full + audit_trail, retention, compaction, consistency_check, behavioral and diagnostic tools | Governance and admin work |
 | `mesh` | 9 tools — mesh coordination only | Lightweight cross-session signalling |
 
-A host that sets no profile gets the 58-tool `full` set (this is what the Claude
-Code and Codex plugins do; the Antigravity plugin sets `power`). While pictures
+Every app gets the 58-tool `full` set unless the user chose another: no plugin
+or extension SuperLocalMemory ships sets one. It fits hosts that cap the total
+number of MCP tools at about 100. While pictures
 and documents are on (`slm media status`), `full` lists 62 tools and `power` 74:
 the five picture tools `remember_media`, `get_media`, `remember_document`,
 `media_status` and `media_upload_link` are added to both, and never to `core`,
@@ -113,19 +114,19 @@ such as `core_memory` and `settle_session_outcomes` exist only with
 `SLM_MCP_ALL_TOOLS=1`, `whole` or an explicit `SLM_MCP_TOOLS` list. Tools whose
 function is to manage the SLM computer are never available to a remote caller.
 
-The tool set is read when the MCP server starts. To change it, set it in the
-host's MCP config and restart the host; asking the server at runtime does not
-work:
+The tool set is read when the MCP server starts. To change it for every app at
+once, the user runs one command and then restarts their apps (or reconnects
+them in Dashboard → Connected apps); asking the server at runtime does not work:
 
-```json
-"env": {
-  "SLM_MCP_PROFILE": "code",
-  "SLM_AGENT_ID": "claude_code"
-}
+```bash
+slm tools                 # the current set and how many tools each set has
+slm tools set power       # core, code, full, power, mesh or whole
+slm tools set default     # back to full
 ```
 
-`slm connect <ide> --profile <name>` writes that variable into a supported
-host's config. Setting `SLM_MCP_PROFILE` to a name that does not exist stops
+An app whose own MCP config sets `SLM_MCP_PROFILE` keeps that value: it wins
+over the saved choice, for that app only (`slm connect <ide> --profile <name>`
+writes it). Setting `SLM_MCP_PROFILE` to a name that does not exist stops
 `slm mcp` with a message listing the valid names. Older count-suffixed names
 such as `code20`, `full38` and `power50` still resolve, with a startup warning.
 On an install that already has memories, do not set `SLM_DATA_DIR` in the MCP
@@ -138,8 +139,10 @@ set. It is not in `mesh`.
 
 ## If a tool is missing
 
-Check the tool set first (`slm status` does not show it; look at the host's MCP
-config for `SLM_MCP_PROFILE`). Mesh tools need `full`, `power`, `mesh` or the
+Check the tool set first: `slm tools` shows it (an app's own `SLM_MCP_PROFILE`,
+if set, overrides it for that app). Tell the user which set has the tool and
+the command, for example "run `slm tools set power` and restart this app", and
+let them decide; widening the set adds tools to every connected app. Mesh tools need `full`, `power`, `mesh` or the
 default. Picture and PDF tools need `full`, `power` or `whole` and the feature
 turned on (`slm media enable`). Code-graph tools need `code` or `SLM_MCP_ALL_TOOLS=1`. Audit and
 retention tools need `power`. `report_outcome` and `report_feedback` need
@@ -157,4 +160,4 @@ anything but `core` or `mesh`.
 
 ---
 
-*SuperLocalMemory v4.2.5 · Qualixar · AGPL-3.0-or-later*
+*SuperLocalMemory v4.2.6 · Qualixar · AGPL-3.0-or-later*