smolagents Memory

https://huggingface.co/docs/smolagents/tutorials/memory

Hugging Face barebones agent framework. Memory lives as a Python list; no built-in persistence. Step callbacks let you mutate memory between steps. Persistence is left to the user — community proposals exist for "memory bank"-style additions.

Active · Verified 2026-10-22 · fresh as of 2026-10-22 · 57 cited facts, 5 with a third-party source · 1 recorded change · Suggest a correction

At a glance

Tier
T2
Created
2024-12 vendor fix
Latest release
v1.26.0 (2026-05-29) registry fix
License
Apache-2.0 repo fix
Freshness
2026-10-22 fix
Layer
agent-infra repo fix
Licensing
open-source repo fix
Deployment locus
local vendor fix
Platform vs product
platform vendor fix
Accelerator
betaworks-camp-2016 third-party fix
SDK languages
python repo fix
Protocols
mcp-client repo fix

Memory taxonomy

storage
kv
retrieval
injection
persistence
session
update
append-only
unit
episode
governance
inspectable
conflict
append

When to use

Optimised for: simplicity / barebones agent loop

Anti-fit: not for production multi-session use - in-process Python list, no persistence

Pros & cons

Pros

HuggingFace's minimal-agent framework; tiny dependency surface; useful for embedded / edge deployments.

Cons

Memory features are intentionally minimal; not the right fit for sophisticated long-term memory needs.

Claims & capabilities

HuggingFace lightweight code-first agent framework; memory exposed as ordered list of past steps (history of plan/exec/error); step callbacks let users dynamically modify memory; long-term memory and memory-bank are open community-requested features

Technical surface

API surface
SDK: Python (agent.memory.steps; CodeAgent/ToolCallingAgent)
Backend storage
in-memory
Deployment
Both (OSS self-hosted; Hugging Face Inference Endpoints / Enterprise Hub managed)
Embedding model
multiple supported
Multi-tenancy
not applicable — library
MCP
via official adapter — smolagents.MCPClient
A2A
searched not found
OpenTelemetry
via adapter — Arize Phoenix

Similar systems

Other framework-embedded memory in the catalog, ranked by inbound references.

  • Spring AI ChatMemory T3

    Wraps conversation memory behind an Advisor abstraction. MessageWindowChatMemory default 20-msg sliding window (preserves system messages); pluggable ChatMemoryRepository backends (in-memory, JDBC, Cassandra, Neo4j). Memory injected as cross-cutting concern at the ChatClient level.

  • Flowise Memory T1

    Discontinued: Flowise (acquired by Workday, Aug 2025) was sunset in 2026 — code freeze 2026-07-29, GitHub repo archived 2026-08-13, end of life 2026-08-31. Was a visual LangChain canvas with LangChain-native memory nodes (Buffer, Buffer Window, Conversation Summary Buffer) backed by an internal chat_message DB table; Buffer Window kept the last K interactions, Summary Buffer compressed older turns while keeping recent ones verbatim.

  • LangGraph Persistence T2

    Distinct from LangMem. Built-in checkpointer saves graph state per super-step (short-term, thread-scoped). Store System adds long-term hierarchical key-value memory across threads with optional vector search + TTL. Postgres / Mongo / Redis stores for production.

  • AutoGen Memory T2

    AutoGen's memory layer: ListMemory chronological context plus teachable agents that vectorise corrections; integrates with Mem0/Zep rather than building deep memory natively. Microsoft AutoGen is in maintenance mode (community managed, bug and security fixes only), and Microsoft points new projects to Microsoft Agent Framework.

  • CrewAI Memory T2

    Memory subsystem inside the CrewAI orchestration framework; integrates with Mem0 for the long-term tier.

  • Hermes Agent memory (Nous Research) T3

    Nous Research's open-source self-improving agent keeps an agent-curated MEMORY.md/USER.md notebook injected at session start, full-text (FTS5) search over past sessions that returns raw messages without LLM summarisation, and optional Honcho user modelling. one of the most-starred agent projects of 2026.

Sources (56 cited facts, 5 third-party)

Each fact links to the page it came from; the badge says who published it (how to read sources).

What changed

Changes to this record's lifecycle, licence, release, pricing and hosting facts, from the catalog's git history. Subscribe (Atom)

  1. 2026-10-22
    • Latest release “v1.24.0 2026-01-16” → “v1.26.0 (2026-05-29)” source
    #195