Connect your runtime
Choose the boundary you control. Integrations do not all expose identical evidence.
| Runtime | Start here | Important boundary |
|---|---|---|
| OpenClaw | Setup | Supported hook profile includes full-fidelity multimodal capture |
| Pydantic AI | Capability adapter | Keeps framework history and model selection |
| LangChain / LangGraph | Middleware | Keeps checkpoints and workflow state |
| Custom host / MCP | Generic adapter | Host must report actual delivery truthfully |
| Python application | Embedded memory | Retrieval alone is not model-input evidence |
| HTTP application | HTTP API | Local authentication and scope still apply |
| Context provider | Delegation | HMAC request auth and signed decisions |
Before activation
Use persistent authenticated subject, agent and workspace identities. IDs supplied by an untrusted prompt do not grant authority. Shadow mode observes and prepares without injecting. Review the control plane before activation.
Provider versus host
A host adapter delivers context to the model and reports lifecycle events. A delegated provider chooses context for a registered scope. AtMem authenticates the request, verifies the signed response and records authorization/delivery. Provider delegation does not imply that the provider stores every agent session.
Compatibility
AtMem is 2.3.6 and the OpenClaw bridge is 2.3.6; AtBot remains 0.1.0. The locked OpenClaw conformance profile uses 2026.8.1, not a promise about every future host. Framework exact-delivery support does not imply the same durable multimodal capture coverage as OpenClaw. See release compatibility.