Skip to content
This repository was archived by the owner on Jul 17, 2026. It is now read-only.
AreteDriverPublic archive
forked from ikay13/memboot

About

Zero-infrastructure persistent memory for any LLM

Topics

Resources

Security policy

Stars

1 star

Watchers

0 watching

Forks

 
 

Repository files navigation

memboot

Status: Archived — Lessons learned have been upstreamed into Animus. See animus/memory for the spiritual successor.

What Was memboot?

memboot was an experiment in local-first, project-aware memory for AI coding assistants.

It explored ideas that were under-served in 2025–2026:

  • AST-aware chunking — indexing Python functions, classes, and methods as semantic units
  • Episodic memory primitives — decisions, notes, observations, and patterns with bitemporal tracking (valid_from / recorded_at)
  • Security-first indexing — SSRF guards, credential skip during chunking, SQLCipher encryption
  • Zero-infrastructure vector search — SQLite + TF-IDF with no Docker or external DB required
  • MCP-native integration — stdio JSON-RPC server for Claude Code, Cursor, Windsurf, Zed, and other AI IDEs

Why It Was Archived

memboot succeeded as a learning vehicle but failed as a standalone product:

  1. Its vector search was inferior — SQLite + TF-IDF lost to Chroma on latency, scale, and retrieval quality in every dimension.
  2. Its moat was thin — AST chunking and regex credential skip are moderate-effort features for a funded competitor.
  3. The right home for these ideas is Animus — a sovereign AI operating environment, not a standalone CLI tool.

What Survives

The valuable parts of memboot have been extracted and upstreamed into Animus:

memboot Component Animus Destination
chunker.py (AST parsing) animus.ingest.code
models.py (Memory types) animus.memory.types
security.py (SSRF, encryption) animus.security.guards
mcp_server.py animus.mcp.memory_server
query.py (search logic) animus.memory.retrieval (backed by Chroma)
CLI workflow (init, remember, query) animus CLI subcommands

What We Learned

  1. AI agents need project-aware memory — codebases are graphs, not bags of files. AST chunking matters.
  2. Security is not optional — credential skip and SSRF guards should be defaults, not afterthoughts.
  3. Bitemporal tracking is underrated — valid_from vs recorded_at lets you answer "what did we believe at the time?"
  4. MCP is the right integration layer — stdio JSON-RPC is simpler and more robust than HTTP APIs for IDE plugins.
  5. Don't build your own vector DB — Chroma, Qdrant, and pgvector exist. Use them.

License

Apache 2.0


For the future of local-first AI memory, see Animus.

About

Zero-infrastructure persistent memory for any LLM

Topics

Resources

Security policy

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages