Sugar – Cross-project memory for AI coding agents via MCP
Cross-project memory for AI agents when single-project solutions already exist.
Cross-agent memory SDK. Agents publish lessons, query shared knowledge, with built-in redaction. Python + TypeScript.
Local-first design — SQLite plus on-device ONNX embeddings — provides a small-footprint way to share operational lessons between agents, and automatic PII redaction is a thoughtful, tangible safeguard. The one-line publish/query API, cross-language SDKs (Python + TypeScript), and a planned FastAPI/Postgres+pgvector server show practical engineering trade-offs rather than vaporware.
AI/ML engineers and developers building autonomous/multi-agent systems who need shared operational knowledge and memory
I built Lore because my AI agents kept making the same mistakes. Agent A discovers that Stripe rate-limits at 100 req/min and figures out the backoff strategy. Next day, Agent B hits the same wall. No learning transfer.
Lore is a small library (not a service) that gives agents shared memory of operational lessons. One line to publish a lesson, one line to query it. PII is automatically redacted before storage.
Key design decisions: - Local-first — SQLite + ONNX embeddings, no server required. pip install lore-sdk and go. - Semantic search — Query by meaning, not keywords. "how to handle rate limits" finds the Stripe lesson. - Auto-redaction — API keys, emails, credit cards stripped automatically before storage. - Both languages — Python and TypeScript SDKs with cross-compatible SQLite DBs. - Optional server — Phase 2 adds a FastAPI server with PostgreSQL/pgvector for org-wide sharing across machines. The local SDK keeps working standalone.
What it's NOT: conversation memory (see Mem0/Zep), a vector database, or a RAG framework. It's specifically for structured operational lessons — "what went wrong and how we fixed it."
The SDK is ~500 lines per language. 258 tests. MIT licensed.
Would love feedback on the API design and whether this is a real pain point for others building with agents.
Cross-project memory for AI agents when single-project solutions already exist.
Unified MCP toolkit shipping in Python and TypeScript, but MCP server scaffolding is already crowded.
Predict-calibrate extraction reduces noise, but Zep and Mem0 already dominate the agent memory space.
Agent memory as git-diffable Markdown files beats opaque vector databases.
Another MCP orchestration wrapper—claims autonomy, but chaining APIs over Docker isn't novel.
Sandboxed agent that writes its own Python tools and remembers mistakes in JSON.