OpenClaw is great at running multiple agents, but shared “project truth” still tends to live in chat scrollback: stack choices, auth rules, API conventions, and the “don’t break this” stuff that new agents keep re-asking.
Nemp Memory makes that shared truth persistent and local:
Stores decisions in .nemp/memories.json (repo / project scope)
Optional global memory: ~/.nemp/memories.json (cross-project)
Save + recall by keyword (substring match across keys/values)
Works through AgentSkills (skills as Markdown + YAML frontmatter) so it’s portable as long as the runtime can execute shell commands and read/write files
Multi-agent friendly: any agent sharing the workspace reads/writes the same JSON memory file
Example:
Agent A saves auth-strategy = JWT, 15m expiry.
Agent B runs /nemp:context auth and sees it immediately before coding.
No message bus, no vector DB, no infra — the filesystem becomes the shared memory layer.
Nemp is a minimal shared artifact in the workspace: agents can write decisions once and re-use them instantly. It’s deliberately dumb (local JSON + shell commands), which is what makes it fast, portable, and easy to audit.
Comments
OpenClaw is great at running multiple agents, but shared “project truth” still tends to live in chat scrollback: stack choices, auth rules, API conventions, and the “don’t break this” stuff that new agents keep re-asking.
Nemp Memory makes that shared truth persistent and local:
Stores decisions in .nemp/memories.json (repo / project scope)
Optional global memory: ~/.nemp/memories.json (cross-project)
Save + recall by keyword (substring match across keys/values)
Works through AgentSkills (skills as Markdown + YAML frontmatter) so it’s portable as long as the runtime can execute shell commands and read/write files
Multi-agent friendly: any agent sharing the workspace reads/writes the same JSON memory file
Example: Agent A saves auth-strategy = JWT, 15m expiry. Agent B runs /nemp:context auth and sees it immediately before coding. No message bus, no vector DB, no infra — the filesystem becomes the shared memory layer.
Repo: https://github.com/SukinShetty/Nemp-memory
First comment (answering “Why does OpenClaw need this?”)
OpenClaw solves orchestration (multiple agents + skills). The missing piece is persistence across agents and across time.
Without a memory layer:
Every new agent starts “blank” and asks for the same setup details
Parallel agents drift into conflicting assumptions (DB/auth/API conventions)
Tomorrow’s session repeats yesterday’s context dump
Nemp is a minimal shared artifact in the workspace: agents can write decisions once and re-use them instantly. It’s deliberately dumb (local JSON + shell commands), which is what makes it fast, portable, and easy to audit.