SillyMemory 0.6.0 (experimental)

SillyMemory 0.6.0 — experimental pre-release

Prepared release boundary: 2026-10-21. Dated preparation, main promotion, version
tags and GitHub Release publication are separate steps. Confirm published versions
in GitHub Releases.

Supported host: SillyTavern 1.19.0, commit
06bde939fb1e9c4c8d8641d810f0a916b5bce127, with Chromium.
Other host versions and browsers remain unverified.

Changes from 0.5.0

• Connect, prepare and enable memory in guided steps. Prepare chat memory runs the
  existing synthetic connection test when needed; its temporary data must be
  cleaned up before proceeding. Connected credentials collapse automatically,
  while Advanced and checkpoint controls remain available.
• Open Memory above the native composer for operation progress, last-prompt
  verification and recovery actions. Ready means a supported chat can use memory;
  Last prompt verified describes the final host prompt check, not answer quality
  or provider receipt. Partial/unavailable verification remains explicit.
• Recover synchronization from the chat panel. Retry reply uses the native
  Regenerate action only for an unchanged pending normal/regenerate user turn,
  after rechecking chat/source, connection, readiness and host activity. It is an
  explicit new model request, never an automatic retry. Continue and swipe keep
  their native controls. Turning memory off restores native history behavior.
• See an applicable blocker before changing settings: unsupported chats and saved
  checkpoints take priority over Vector Storage. Built-in Vector Storage is not
  a dependency; SillyMemory connects directly to LambdaDB. Its existing conflict
  notice opens native settings without changing another extension's settings.
• Use the public benchmark reproduction profiles for
  bounded LongMemEval and BEAM evaluation. They are development tools, not a new
  installed retrieval mode or a new release-level quality guarantee.

Query1, managed OpenAI Small embeddings, Bayesian fusion, Jev 1.13.0 candidate 200 /
final 50 reranking, source validation, pair-aligned recent history, chunk packing,
4,096-token memory allocation/maximum and the host one-quarter-context cap keep
their 0.5.0 policies. The SDK and shipped bundle are unchanged. No query rewrite,
summary generation or extra inference phase is added to ordinary retrieval.

Installation, update and data

Follow the installation guide. Install the repository URL with an empty branch field to follow public main.
Use Extensions → Manage extensions → SillyMemory → Update, then reload.
The Update button follows the installed Git branch, not the newest tag/Release.
Automatic updates remain disabled; users do not need to build the extension.

This change introduces no new collection/index format or migration step relative
to 0.5.0. Its index requirements still apply to earlier experimental collections;
updating code does not repair their indexes. Keep original chats and backups.
Installation checks establish Git update and preference preservation, not live
existing-collection compatibility. See 0.5.0 storage requirements.

Credentials keep their account/endpoint/project scope. Browser storage remains
accessible to same-page extensions. No server plugin, host-credential forwarding,
new provider key or proxy is added. For rollback, disable memory, preserve native
chats, and pin the published v0.5.0 tag using the release procedure.
A code rollback does not undo remote writes or restore deleted data.

Acceptance and limits

See 0.6.0 acceptance for exact producer/installation/update
commits, commands, inherited runtime evidence and retained reports. Current
release preparation does not add paid-provider or answer-quality experiments.

Group/tool conversations, arbitrary host/browser compatibility and concurrent
multi-device writers remain unsupported. Flattened Text Completion prompts report
verification unavailable. Host context/output space, the 8 KiB complete-query
limit and recent-window limitations still apply. Existing benchmark scores and
historical managed-service acceptance retain their original protocols and scope.