AgentMemory instance: you build the memory, connect it to your account, and hand it to the wrapper.
Setup
Install the SDK and the HTTP adapter, then build one connected memory that every integration below shares:pip install "amfs-crewai[crewai]". If you already have the framework installed, the plain package is enough. Get a key from the Connect to SenseLab guide.
CrewAI
Add SenseLab tools to your CrewAI agents:entity_path, key), write one (entity_path, key, JSON value) and list entries as part of its task. Requires CrewAI 0.80 or later; tools() raises ImportError with the install hint if CrewAI is missing.
LangGraph
Keep graph state in SenseLab, keyed bythread_id:
put is a new version of the same entry, a thread’s full history is kept and list returns it.
AMFSCheckpointer is a minimal checkpoint store with put, get and list.
It does not implement LangGraph’s BaseCheckpointSaver interface, so call it
from your own nodes or wrap it rather than passing it straight to
graph.compile(checkpointer=...).LangChain
Use SenseLab as chat memory for LangChain:mem.history("_langchain_chat", "conv-123") shows how the conversation grew.
AutoGen
Use SenseLab as a key-value memory store for AutoGen agents:Strands Agents
Add memory to a Strands agent as a plugin:amfs_read, amfs_write, amfs_search, amfs_recall, amfs_list and amfs_record_context — and also records the agent’s other tool calls into the causal chain as contexts, so the decision trace covers the whole session rather than only the memory operations. Pass AMFSPlugin(mem, auto_trace=False) to register the tools without that tracing. Requires strands-agents 1.0 or later.
If you’d rather have one action-based tool than the full plugin, amfs_memory handles store, retrieve, search and list:
amfs_memory builds its own AgentMemory — identity from AMFS_AGENT_ID
(default strands-agent), storage from amfs.yaml or the local .amfs/
directory — so it does not reach SenseLab. Use AMFSPlugin with the
connected memory from Setup for that.Close the loop
The wrappers above read and write. What makes the memory improve is telling SenseLab how the task went, on the samemem the framework used: every entry the agent read during the run is already in its read log.
Building your own integration
All integrations are thin wrappers around theAgentMemory API. To build your own:
- Accept an
AgentMemoryinstance in your constructor - Map your framework’s memory/tool API to
mem.read(),mem.write(),mem.list(),mem.search() - Use
entity_pathto scope data (per conversation, per task, per agent)
What’s next
Python SDK
The full
AgentMemory API that every integration wraps.Core Concepts
Understand versioning, provenance, and causal graphs in SenseLab.
