SillyMemory 0.4.0 (experimental)

SillyMemory 0.4.0 — experimental pre-release

Long-term memory for SillyTavern. Powered by LambdaDB.

Prepared release boundary: 2026-10-13. Confirm publication through the
GitHub Release.
Dated notes alone do not promote main or publish a release; those actions require
maintainer authorization. Supported host: SillyTavern 1.19.0, commit
06bde939fb1e9c4c8d8641d810f0a916b5bce127; other versions remain unverified.

User-visible changes

• Preserve at least five recent eligible messages in native order and roles,
  keeping an adjacent input/reply pair together. Normal input retains five;
  a completed reply can retain six. Archive displaced completed pairs together
  as separate message chunks, not a delayed five-message write queue.
• Search the two latest eligible messages in one role-labelled request. Bayesian
  vector/English-text fusion uses managed Jev reranking, vector k=100, at most
  100 candidates and 50 returned chunks. The initial memory budget is 4,096 tokens,
  capped at one quarter of the host context. An explicit saved budget is respected.
• Assemble touching/overlapping chunks from the same source without repeating
  provenance headers. Available host-message timestamps accompany excerpts and
  are explicitly distinct from dates mentioned in the story. No LLM preprocessing
  or additional retrieval request is added.
• Keep native replies, model/API formats and streaming. Natural guidance asks for
  clarification of ambiguous intent and acknowledges missing/conflicting evidence.
  There is no forced JSON response or accumulated clarification state.
• Save a verified key for this native account and exact endpoint/project in a
  dedicated browser record. Reload verifies it before restoring the previous
  memory-enabled state. Forget key removes it and disables memory. Other code on
  the same page can access browser storage; this is not an isolated secret vault.
• Use story collections and isolated chat branches by default, including explicit
  named checkpoints and inherited committed history. The old opt-in/conversion
  path is removed; there is no existing-user data migration contract.
• Keep preparation failures visible even after background synchronization. A
  failed generation preserves the submitted input and directs retry to Regenerate.

Installation and operation

After authorized promotion, install https://github.com/lambdadb/SillyMemory
from Extensions → Install extension, leaving the branch field empty to follow
main. Existing branch-based installations use Manage extensions → SillyMemory
→ Update, then reload. No npm install, build, server plugin, proxy setting or
host restart is required. LambdaDB must accept the browser origin via direct CORS.

A LambdaDB project key with document, collection and branch permissions is required.
Use Save and connect, run the synthetic connection test, prepare chat memory,
then enable memory for a saved character chat. Managed embeddings and reranking
still incur service costs; no separate embedding-provider key is needed.
Disable memory to use ordinary native history. See the README,
saved credentials and checkpoints.

Evidence and limits

See installation readiness and
bounded native-reply validation. The latter uses
real managed LambdaDB and Sol, including streaming and reconnection; it is a narrow
English UX acceptance run, not an official benchmark score or quality guarantee.
Transient search 503s required explicit regeneration retries; their backend cause
is unknown. A failed preparation stops generation rather than silently continuing.

Final Chat Completion delivery is verified against prepared memory/recent turns;
text-completion delivery remains visibly unverified. Long ambiguous conversations
can outgrow the recent window. Queries above 8 KiB fail explicitly. Small host
contexts may truncate even recent turns; keep sufficient context and output space.
No multi-device concurrent-writer, arbitrary-provider or multilingual quality
support is established. Rollback changes code, not remote/local data; see
release procedures.

Publication verification

Published as an experimental pre-release on 2026-10-13. Main and annotated tag
v0.4.0 both identify efd5df8d5cdecdc95714c3b1f51314c60ed7ae6e. The promotion preserves the
reviewed develop head as the merge commit's second parent; its tree is unchanged.

• Main CI and tag CI passed on Node.js 20.12.0 and 24.
• Actual SillyTavern 1.19.0/Chromium default Git URL installation of public main
  passed 14 assertions, including exact commit/version and preference/ownership
  preservation after reload, with zero page errors or provider calls. Temporary
  profiles were removed. This is installation acceptance, not a new answer-quality run.
• Original report, screenshot, measured producer and publication receipts are
  retained locally in artifacts/archive/release-040-publication-v1/evidence.tar.gz;
  SHA-256 f235a8a4f7e5456891e7fd2c13db128b3f4e923e97be0e6b751d3be944baf5bf. Member bytes were read back and verified. This local-only archive
  is not downloadable from a fresh clone or this Release.