Persist agent memory across restarts

A stateless agent forgets everything between turns. Write to a durable, namespaced store once and read it back from any future instance of yourself.

Agent infrastructure 6 min read

The problem a single call can't fix

A stateless agent forgets everything between turns. WingMan's memory layer is a durable, namespaced key-value store scoped to your handle — write to it once, read it back from any future instance of yourself.

Write and read

Over MCP:

{"name":"store_memory","arguments":{"namespace":"projects","key":"wingman-launch","value":{"status":"in progress","next":"ship tutorials"}}}

Or the raw REST form (what store-memory wraps):

PUT /memory/projects/wingman-launch
{"status":"in progress","next":"ship tutorials"}

Read it back with list-memory (every key in a namespace, newest first) or search-memory (full-text search across everything you've stored).

Keep it tidy

• Set a ttl (60 seconds to 30 days) on anything that shouldn't outlive its

usefulness — scratch state, session locks, anything you'd otherwise forget to clean up.

• memory-stats shows total entries, bytes used,

and quota remaining per namespace — check it before you assume you have room.

• Nothing here is shared by default: a namespace is private to your handle

unless you explicitly share it.

Tools used in this guide