search_memoryLABSCO SUMMARY
Two stores, and the split is the design.
Most memory tools give you one bucket, which means either your project notes drown your general standards or the reverse. Reserving result slots for guidelines from the global store fixes that directly: a brand-new project inherits how you work, and a mature one still gets reminded of it. The per-type expiry is the other quiet good idea — an error pattern from last quarter should age out, an architecture decision should not.
What it is
A memory layer for AI coding agents that lives in SQLite on your disk. Two stores — one inside the project, one global — and a search that reads both, so project context wins while your cross-project standards still surface.
What you get
search_memory— searches both stores and labels which scope each result came fromstore_learning— saves a memory; passingscope: "global"writes to the cross-project storerecall— formatted markdown context for a topic, ready to readget_project_context— a project summary including the global guidelines that applylist_recent_memories— browse recent memories filtered by type- Seven memory types with different lifetimes:
decision,preference,file_contextandguidelinenever expire, whileerror_patternlasts 90 days,research60 andoutcome30 - A search that reserves slots for global guidelines, so a mature project's local context cannot bury your standards
- Resources
sugar://project/context,sugar://preferencesandsugar://global/guidelines - An optional second server,
sugar mcp tasks, backing a task queue that reads the same memory
Requirements
pipx install sugarai, then sugar init in the project. Memory lives in .sugar/memory.db for the project and ~/.sugar/memory.db globally. Semantic search comes from the [memory] extra — sentence-transformers all-MiniLM-L6-v2, 384-dimension vectors, with sqlite-vec — and without it search falls back to FTS5 keyword matching and then LIKE. The memory server needs no API key and makes no external calls. The task server takes optional ANTHROPIC_API_KEY, GITHUB_TOKEN and SUGAR_DEFAULT_REPO.
Setup effort
One command — pipx install sugarai
USE CASES
Stopping the agent from re-asking what you already told it
Have it search memory for relevant context at the start of a session before it asks you to re-explain the architecture.
Recording a convention once
Store it as a preference or decision and let it surface whenever the topic comes up again.
Carrying your standards between projects
Save guidelines to the global store so security and commit conventions follow you into every new repository.
Checking what has been learned lately
Browse recent memories by type to see what the agent has been recording.
5 tools
Listed in project docs. Your client may show a different list.
store_learningrecallget_project_contextlist_recent_memoriesBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Requires
- pipx on PATH
- Python 3.11+
INSTALLATION
Connect your client
Server setup
pipx install sugaraiMCP Clients
Claude Code — Memory server
claude mcp add sugar -- sugar mcp memoryClaude Code — Task server
claude mcp add sugar-tasks -- sugar mcp tasksOpenCode
sugar opencode setupClaude Desktop
{
"mcpServers": {
"sugar": {
"command": "sugar",
"args": [
"mcp",
"memory"
]
}
}
}