Skip to content

SillyMemory 0.7.1 (experimental)

Pre-release
Pre-release

Choose a tag to compare

@swkim86 swkim86 released this 23 Oct 06:42
· 5 commits to main since this release
f038205

Experimental release for SillyTavern 1.19.0 with Chromium.

Changes

  • Frozen memory snapshots preserve the complete native JSONL transcript while indexing only the older-history partition used by ordinary synchronization. Recent messages stay in the transcript and are archived normally when later dialogue displaces them on a resumed writable path.
  • Documentation and development tools focus on current behavior and final benchmark results. Retired experiment implementations and cohort-only fixtures have been removed; original evidence is preserved.
  • The retained summary comparator resolves its maintained source files when recording the source digest.
  • The isolated BEAM Python environment uses certifi==2026.10.19.

Install and update

In SillyTavern, choose Extensions → Install extension and enter:

https://github.com/lambdadb/SillyMemory

Leave the branch field empty to follow main. Existing installations can use Manage extensions → SillyMemory → Update, then reload. Updates follow the installed Git branch; automatic updates remain disabled. No npm install, compilation or server restart is required.

Existing 0.7.0 per-chat activation, saved connection scope, collection/index formats, retrieval defaults and native reply/streaming behavior are unchanged. When updating from 0.6.0, enable memory separately in each desired chat.

Installation guide · Update and rollback · Benchmark profiles

Validation and limits

The release passes 244 JavaScript tests and 32 Python tests, syntax, SDK and release checks. Candidate installation and native Update on the pinned host passed 22 assertions; the release preserves that candidate's browser runtime and version metadata. See the acceptance record for the exact measured commits and scope.

This remains experimental. Other host versions and browsers are unverified; group/tool conversations and concurrent multi-device writers are unsupported. Code rollback does not restore local or remote data. See current limits.