SillyMemory 0.7.0 (experimental)

SillyMemory 0.7.0 — experimental pre-release

Release boundary: 2026-10-22. This experimental release promotes the reviewed
0.7.0 code to public main at 9c31f0ac1b3fe405f5916df5b9f6930ae29cd571.

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

Changes from 0.6.0

• Turn memory on or off directly in the chat panel. Each saved character chat has
  its own choice; extension settings manage the shared LambdaDB connection.
• Use native chat history, Save checkpoint, Create Branch and Back to parent chat
  as the ordinary workflow. Memory follows the selected path and its saved choice.
  Optional verified transcript/remote-memory saves live under Advanced → Frozen
  memory snapshots. Saving/resuming preserves activation and shows progress.
• Read status colors directly: green for ready/verified, orange for work in
  progress, yellow for warnings and red for errors. Ready and verified prompt
  delivery remain separate states.
• Expand Memory to preview selected source excerpts and inspect the full last-prompt
  memory. The panel shows estimated prepared input and memory tokens when the host
  exposes them. Optional dialogue-text comparison is local, excludes native
  system/character formatting and is not a full memory-off prompt or billing comparison.
• Reconnect from chat using the scoped saved key. Missing/rejected keys direct
  users to Connection settings. Reconnection ignores unsaved form edits and
  preserves per-chat choices; automatic reload/chat reconnect never starts an
  unprepared transport test.
• Complete initial Connect and prepare in one action, with temporary inference
  usage disclosed before connecting. Setup validates/saves the key, verifies test
  cleanup and leaves per-chat activation separate. Interrupted preparation exposes
  cleanup and Finish preparation.
• Refresh visible snapshot lists automatically on opening, chat changes and
  reconnection. List errors stay local; stale responses cannot replace a different
  story. Native input/confirmation popups handle rename/delete, including cancel,
  Escape and changed-chat protection.

Installation, update and activation

Install the repository URL with an empty branch field to follow public main.
Update through Extensions → Manage extensions → SillyMemory → Update,
then reload. Update follows the installed Git branch, not the newest tag/Release.
Automatic updates remain disabled; no build step or server restart is needed.

After updating from 0.6.0, turn memory on in each chat where you want it. The
old global enabled flag is not copied to every chat. Chats without a saved
sillymemoryEnabled preference start off. Existing explicit per-chat choices
from development builds remain saved in native chat metadata. Turning off keeps
stored memory but excludes that chat's automatic synchronization and retrieval.

Saved keys keep their account/endpoint/project scope and reconnect after reload.
Other same-page scripts can access browser storage; it is not a secret vault.
No new key type, server plugin, proxy or host-cookie forwarding is introduced.

Collection/index formats, ownership, Query1, managed embeddings/reranking, recent
history alignment, chunk packing, budgets and native reply/streaming formats are
unchanged from 0.6.0. No new remote migration is introduced. Earlier experimental
collections still require the 0.5.0 index configuration;
updating code does not repair indexes. Git installation/update checks do not prove
existing-collection compatibility or data migration.

Before changing versions, preserve native chats and backups. To roll back, disable
memory and pin published v0.6.0 using the release procedure.
Rollback does not undo remote writes/deletions or restore the previous global
activation choice. Resume normal branch updates only after leaving the pinned tag.

Acceptance and limits

See 0.7.0 acceptance for exact installation/update commits,
commands, retained artifacts and inherited runtime evidence. This preparation
adds no paid-provider or answer-quality experiments. Public-main fresh installation
passed 14 checks on the exact release commit, with zero page errors/provider
requests and disposable-profile removal. Main CI
passed on Node.js 20.12.0 and 24.

Group/tool conversations and concurrent multi-device writers remain unsupported.
Flattened Text Completion verification remains unavailable. Host context/output
space, the complete-query 8 KiB limit and recent-history limits still apply.
Previewed memory, prompt verification and token estimates do not establish answer
correctness, provider receipt, cost savings or new benchmark quality results.