Memory service and decisions for Agent Zero agents
  • TypeScript 100%
Find a file
2026-06-03 16:27:15 -04:00
_docs docs: add memory API reference 2026-06-02 22:33:11 -04:00
scripts feat: add memory service MVP 2026-06-02 22:23:24 -04:00
src chore: prepare 0.2.5 alpha release 2026-06-03 16:27:15 -04:00
.gitignore docs: initialize memory project decisions 2026-06-02 19:40:02 -04:00
CHANGELOG.md chore: prepare 0.2.5 alpha release 2026-06-03 16:27:15 -04:00
package-lock.json feat: add memory service MVP 2026-06-02 22:23:24 -04:00
package.json chore: prepare 0.2.5 alpha release 2026-06-03 16:27:15 -04:00
README.md chore: prepare 0.2.2 alpha release 2026-06-02 23:07:16 -04:00
ROADMAP.md docs: plan multi-user identity support 2026-06-02 22:29:22 -04:00
tsconfig.json feat: add memory service MVP 2026-06-02 22:23:24 -04:00

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