Memory and evidence, under your control

An opt-in 2.3.15b1 beta adds governed RAG/MCP and verified feedback. The stable installation examples below retain 2.3.14. Use the explicit beta pin in the release note to test it.

AtMem is a host-neutral Agent Black Box and reversible memory control plane. Keep scoped memories useful across sessions, control which context reaches an agent, and investigate the evidence a supported host captured.

Start with a working example

Install and run your first memory. The Python example runs without an API key or a model download. Then connect an agent and review shadow mode before enabling context injection.

Stable 2.3.14: memory, context and evidence

AtMem 2.3.14 retains source-backed, read-only discovery for explicitly configured SDK/host integrations. Start with the integration guide and release note. It does not automatically enable agent tools or change ordinary memory defaults.

Shared coding memory

Optional AtMem Code connects source-backed project structure with searchable coding experience. Share authorized project memory across agents, inspect what was retained, and move encrypted project memory between clones. Start with the Code guide and 2.3.9 release note. Existing memory, evidence and integration boundaries remain in force.

Explore the documentation

• Product portfolio: AtMem, AtBots, AtFlows and AtSys roles, source repositories and integration boundaries.
• Getting started: installation, first memory and troubleshooting.
• AtBot: optional model-assisted memory proposals governed by AtMem.
• AtFlows: local observability, optional shared login and evidence-review leads.
• Integrations: OpenClaw, frameworks, MCP and delegated providers.
• Reference: commands, HTTP, retrieval, evidence and storage.
• Examples: small runnable workflows and expected results.
• Releases: changes, compatibility and upgrade instructions.

Know what the evidence proves

AtMem retains what supported host boundaries supply. A tool returning successfully is not independent proof that a purchase or message succeeded externally. Missing historical content cannot be reconstructed from a hash. Read evidence and roles before choosing a capture profile.

Guides describe stable behavior unless marked beta. For older installations, read that version's release notes and upgrade instructions; full historic guide sets are not published here.