Lindy AI Memory

https://docs.lindy.ai/teammate/memory

Memory is a file explorer for what Lindy knows: files it creates or uses, files users upload, skills (.skills/ folders with SKILL.md) and durable knowledge in a .memory/ area. Scoped Personal (owner only), Team (admins edit, members read-only) and System (read-only); every save is versioned and restorable.

Deprecated · Verified 2026-10-23 · fresh as of 2026-10-23 · 45 cited facts, 5 with a third-party source · 2 recorded changes · Suggest a correction

At a glance

Tier
T1
Latest release
not applicable — not OSS fix
License
not applicable — not OSS fix
GitHub
not applicable — no GitHub repo fix
Freshness
2026-10-23 fix
Layer
agent-infra repo fix
Licensing
commercial vendor fix
Deployment locus
cloud vendor fix
Platform vs product
product vendor fix
Accelerator
ai-grant third-party fix

Memory taxonomy

storage
kv
retrieval
injection
persistence
cross-session
update
extraction
unit
fact
governance
user-controllable
conflict
llm-arbitrate

When to use

Optimised for: selective high-signal memory injection

Anti-fit: not for code-first developers

Pros & cons

Pros

Lifelong-agent positioning — memory isn't a feature but the product premise; most opinionated about memory of any framework.

Cons

Closed ecosystem; lock-in risk is highest of the framework-embedded options.

Claims & capabilities

A background memory agent rebuilds each user's and team's memory files every 12 hours from Slack, Gmail, meetings and Lindy tasks, keeping episodic, procedural and semantic memories; an index file and master memory file are always in context (Lindy engineering blog, 2026-08-16).

Technical surface

API surface
searched not found
Backend storage
searched not found
Deployment
Managed cloud only (SaaS)
Embedding model
searched not found
Multi-tenancy
searched not found
MCP
yes — MCP client: connects to hosted streamable-HTTP MCP servers and builds actions from their tools
A2A
searched not found
OpenTelemetry
searched not found

Compare Lindy AI Memory with…

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 (44 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-23
    • Homepage “https://docs.lindy.ai/fundamentals/lindy-101/memory” → “https://docs.lindy.ai/teammate/memory”
    • Pricing “Plus $49.99/mo; Pro $99.99/mo; Max $199.99/mo; Enterprise custom; 7-day trial, no permanent free tier (third-party, Apr 2026)” → “Free: $50 in credits for 7 days, no card; Team $29.99/user/mo (3,000 credits, extra $10 per 1,000); Enterprise custom” source
    #223
  2. 2026-10-22
    • Pricing “Free plan; Plus $49.99/mo; Pro $99.99/mo; Max $199.99/mo; Enterprise custom with SSO/SCIM/audit logs” → “Plus $49.99/mo; Pro $99.99/mo; Max $199.99/mo; Enterprise custom; 7-day trial, no permanent free tier (third-party, Apr 2026)” source
    • MCP support first recorded as “yes — MCP client: connects to hosted streamable-HTTP MCP servers and builds actions from their tools” source
    #219