Agent memory — memory

The agent’s own observations, written back via the MCP remember tool (or POST /remember). Joinable into views like any other source — what an agent concluded about service=checkout last week sits in the same timeline as the service’s logs and deploys.

Set up

None needed. The first remember call auto-provisions an agent_memory source; every connected agent has the tool:

Use navflow to remember that the checkout latency spike on July 1 was caused by the pool-size change.

Create a memory source explicitly (console or YAML) only to set a custom fallback key or run several memory lanes:

- name: agent_memory
  connector: memory
  config:
    key: agent

Configuration

Verify

After a remember call, the observation appears in the source’s Recent events, keyed by the entity it was remembered against — and in that entity’s correlated timeline.