Memory service and decisions for Agent Zero agents
- TypeScript 100%
| _docs | ||
| scripts | ||
| src | ||
| .gitignore | ||
| CHANGELOG.md | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| ROADMAP.md | ||
| tsconfig.json | ||
Agent Zero Memory
Agent Zero Memory is planned as a separate memory service for Agent Zero agents, gateway-routed agents, and future ephemeral sandbox/k8s agents.
It is not the Agent Zero runtime and not the gateway. It is shared infrastructure for storing, deriving, searching, and retrieving memory.
Intended role
agent-zero
runnable agent runtime; exposes memory through optional extension tools
agent-zero-gateway
routing/control plane; may pass identity/session metadata to agents
agent-zero-memory
memory service; stores raw memory inputs and derived memories/conclusions
agent-zero-ui
user interface; eventually shows memory review/edit/approval flows
Core decisions
- Memory is a separate project/service, not built directly into every Agent Zero instance.
- Agents access memory through optional tools provided by Agent Zero's extension/capability system.
- Profiles decide whether an agent has memory access.
- Memory has two major domains:
- agent operational memory
- user memory
- User memory should start manual/user-approved.
- Agent operational memory can later support suggestions and controlled automatic writes.
- SQLite is acceptable for local alpha, but the design should target Postgres long term.
- Honcho is a useful architecture reference, especially its workspace/peer/session/message model and background derivation loop.
Development
npm install
npm run dev
Default URL:
http://127.0.0.1:7500
Validate:
npm run test:all
Current MVP endpoints:
GET /health
GET /memories
POST /memories
GET /memories/:id
PATCH /memories/:id
DELETE /memories/:id
POST /memory/search
POST /memory/context
Docs
CHANGELOG.md
_docs/decisions.md
_docs/architecture.md
_docs/api-reference.md
_docs/tool-integration.md
_docs/honcho-notes.md
ROADMAP.md