Local-first memory engine for AI-agent teams — SQLite core, federated sync, MCP + Web console.
4.3K
A local-first, open-source memory engine for AI-agent teams.
One SQLite file is the whole brain: durable memories with a hard requester-aware ACL, an associative resonance recall graph, budgeted context packs, and federated sync across nodes with a real trust model. Ships an MCP server (so Claude Code / Codex / any MCP client can remember across sessions) and a FastAPI web console — all behind one bearer token.
docker run -d --name agent-memory \
-p 8000:8000 \
-v agent-memory-data:/data \
yamantaka520/agent-memory-os:latest
The container generates a Web API token on first boot — read it from the logs:
docker logs agent-memory | grep -i token
Then open http://localhost:8000 and paste the token. The MCP server runs the
same image; the database lives in the /data volume and self-migrates forward on
every upgrade.
services:
agent-memory:
image: yamantaka520/agent-memory-os:latest
ports: ["8000:8000"]
volumes: ["agent-memory-data:/data"]
restart: unless-stopped
volumes:
agent-memory-data:
shared / full / team: / project:) is an enforced authorization
scope. Revocation propagates — revoking access retracts already-synced memory./healthz (readiness) and /metrics (Prometheus), one-click
maintenance, backup rotation, a read-only token tier, and a self-updater.latest — the newest stable release1.0.0, 0.14.0, … — pinned versions (use a pin in production)Multi-arch: linux/amd64 and linux/arm64.
| Variable | Purpose |
|---|---|
AGENT_MEMORY_WEB_TOKEN | Set a fixed Web API token instead of the generated one. |
AGENT_MEMORY_WEB_READONLY_TOKEN | A second, GET-only token for dashboards/auditors. |
AGENT_MEMORY_NODE_NAME | This node's name in sync/federation. |
The image's HEALTHCHECK probes /healthz. A two-node sync mesh and full env
reference are in the Docker guide.
pip install 'agent-memory-os[full]')Content type
Image
Digest
sha256:7e9afcf1a…
Size
95.6 MB
Last updated
4 days ago
docker pull yamantaka520/agent-memory-os