Skip to content

V3.4.10 Fortress

Varun Pratap Bhardwaj edited this page Apr 14, 2026 · 1 revision

V3.4.10 "Fortress" — Cloud Backup & Data Quality

Released: April 2026

V3.4.10 "Fortress" adds cloud backup to SuperLocalMemory. Your memories are no longer trapped on one machine — back them up to Google Drive or GitHub with one click.

What's New

Cloud Backup

  • GitHub Backup: Connect with a PAT, SLM creates a private repo and backs up all databases as GitHub Release assets. Fully automatic.
  • Google Drive Backup: Connect via OAuth, SLM creates a SLM-Backup folder and keeps your databases synced. Setup Guide
  • Manual Export: Download a compressed .gz backup from the dashboard anytime.
  • Background Sync: All uploads run in background threads — the dashboard never freezes.

Dashboard Account Widget

  • Sidebar shows your connected cloud accounts with avatar and username
  • Sync status indicator: green (synced), yellow (pending), red (failed)
  • Quick-action buttons: Google, GitHub, Sync Now, Export

Entity Quality

  • Expanded stop-word blacklist (200+ terms) prevents garbage entities like "All", "Not", "April"
  • Conservative entity type classifier — single words default to "concept", not "person"
  • One-time cleanup migration removes existing garbage entities on upgrade

All Databases Backed Up

Previous versions only backed up memory.db. V3.4.10 backs up ALL managed databases:

  • memory.db, learning.db, audit_chain.db, code_graph.db, pending.db
  • Managed database registry — new databases auto-included

Auto-Backup Integration

  • BackupManager.check_and_backup() now runs on the maintenance scheduler
  • After each auto-backup, cloud destinations are synced automatically

Schema Changes

Two new tables (silent migration — no action needed):

backup_destinations  — Cloud backup targets (Google Drive, GitHub)
entity_blacklist     — Stop words that should never become entities

Migration

Fully automatic. Update via npm or pip:

npm update superlocalmemory
# or
pip install -U superlocalmemory

On first restart, the new tables are created and the entity blacklist is seeded. Existing data is untouched.

What's Next: V3.4.11 "Scale-Ready"

Planned for the next release cycle:

  • Tiered storage (Hot/Warm/Cold/Archive)
  • LanceDB vector store (millions of vectors)
  • KuzuDB graph database (billions of edges)
  • Graph pruning and fact consolidation
  • Master Plan

Clone this wiki locally