SuperLocalMemory 4.1.23 — Your web apps and bots use the same memory, and it stays on your computer

Added

• Web access. ChatGPT, Claude on the web, Claude Code on the web, Muse,
  Composio and any MCP client that supports remote connections with OAuth can
  use the memory on your computer. Turn it on from the dashboard's new
  Connected apps page, sign in with GitHub, and choose per app whether it
  may only read, also save, and use session tools. Your computer keeps one
  outbound link to SLM's connection gateway; there is no port to open and no
  tunnel or Cloudflare account to set up. The memory database never leaves the
  computer, and SLM works fully without Web access. Each connection has a free
  daily allowance of tool calls.
• Web access renews its own credentials while your computer is online. If the
  computer stays offline long enough for access to lapse, the Connected apps
  page warns before it ends and says what to do after. Once the computer has
  been silent for 45 seconds, for example asleep, a web app is told at once that
  it is unavailable. A relayed recall answers inside the relay's time budget,
  and remote answers are compact JSON with host details redacted.
• Connected apps lists every app that can reach your memory and removes
  any of them with immediate effect. Memory and local configuration are kept.
• Instructions for web agents. docs/web-agents/ has a full and a short
  instruction block and an Agent Skill folder that tell a connected app when to
  recall, when to say it has no answer, what to save (with kind, tags and an
  idempotency key) and what to do when your computer is asleep or the daily
  allowance is used up. The dashboard copies the short block for you.
• slm-web-access skill in every editor plugin, so a local agent can help
  you set up Web access and diagnose a connection.
• slm db repair brings the two vector indexes back in line with the
  memories. It rewrites sqlite-vec rows that no longer match their memory's
  embedding and removes LanceDB rows for memories that are gone, withheld or
  soft-deleted; slm db integrity reports both counts.
• SLM checks your memory store after an upgrade, and Health offers Repair
  now. A few minutes after the first start of a new version, the store is
  checked in the background; the check only reads. The dashboard's Health page
  lists what it found in plain words, the sidebar marks Health while something
  can be repaired, and Repair now saves a full backup copy first, runs the
  same repair as slm db repair, and checks again. If the backup copy cannot
  be made, nothing is changed.
• Every editor plugin ships in the npm package: Codex, VS Code / Copilot,
  Hermes and Antigravity alongside Claude Code, with all skills, agents and
  rules. slm codex install now installs every skill and all four sub-agents.
  Editor and agent plugins gives each host's install
  commands.
• Model advice carries SLM's own measured results, and a model measured on
  a small sample is ranked conservatively.

Changed

• The editor plugins' skills, agents and rules were checked against the
  current tools and corrected where they had drifted.

Fixed

• 4.1.22 could corrupt memory.db or lose saves (GitHub #153). The start-up
  cache read opened and closed memory.db inside the daemon. SQLite's locks
  belong to the process, so that close dropped them: another process (a hook,
  slm mcp, slm doctor) could then delete the WAL under the running daemon,
  which logged "database disk image is malformed" or "disk I/O error" and could
  write stale pages back into the store. The read now runs in a child process.
  Thanks to @MelleKoning for the detailed report and an independent fix (#154).
  If you run 4.1.22, upgrade. If slm doctor then reports a malformed
  database, list restore points with slm db restore-points and go back to the
  newest one with slm db restore <id>; then run slm db integrity. Upgrading
  is the supported path: migrations are forward-only, so going back to an older
  release needs a backup taken before it.
• On SQLite older than 3.42 (for example Ubuntu 22.04), every start and every
  erasure logged "keyword index secure delete not enabled: SQL logic error".
  That SQLite cannot remove deleted words from the keyword index at once;
  SLM now says so once at info level, and slm db repair removes them.
• The "Lance semantic projection diverged from SQLite" warning at every start
  is gone: LanceDB search now covers every tier the canonical search ranks.
• Semantic search on LanceDB now finds cold and archived memories too.
• A rebuilt vector projection leaves out withheld and soft-deleted memories.
• An erasure also blanks the preview of the erased memory in auto-observe
  activity events, and slm db repair blanks previews that earlier erasures
  left in activity events.
• A web app's save or recall is never filed under the session of an agent
  running on your computer.
• A second suggestion about the same memory no longer logs a warning on every
  save.
• A memory saved with the same words as another memory is no longer counted as
  repair work that the repair could never do.
• Maintenance never creates an empty database at a path where no store exists.
• The Hermes guide named a release download that was never published; it now
  installs the plugin from the repository. The VS Code guide named a connect
  command that does not exist; it is slm connect vscode-copilot --here.
• The laptop link no longer fails at start when two parts read its credential
  at the same time.
• The remember tool is declared additive, so clients do not treat saving as a
  destructive action.

Security

• The remote connector's HTTP clients never follow a redirect, and tests pin
  that the API key cannot be sent to another host.
• Web access grants are narrowed to the scopes you consented to, for one MCP
  resource; client registration keeps no diagnostic records.