AGiXT Adaptive Memory

https://github.com/Josh-XT/AGiXT

Open-source AI automation platform. Routes between short-term and long-term memory adaptively across any LLM provider; plugin system for storage backends. Memory managed at the instruction-management layer — task context, instruction state, conversation history as unified agent state.

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

At a glance

Tier
T2
Created
2023-04 repo fix
Latest release
v1.9.4 2026-04-08 repo fix
License
MIT repo fix
Funding
searched not found fix
Freshness
2026-10-22 fix
Layer
agent-infra repo fix
Licensing
open-source repo fix
Deployment locus
hybrid repo fix
Platform vs product
platform repo fix

Memory taxonomy

storage
vector
retrieval
similarity
persistence
long-term
update
extraction
unit
episode
governance
inspectable
conflict
llm-arbitrate

When to use

Optimised for: provider-spanning + plugin storage

Anti-fit: not for enterprise-grade SLA workloads

Pros & cons

Pros

OSS adaptive memory with web-search fallback when local memory misses; multi-LLM support.

Cons

Smaller community; documentation uneven; production track record limited.

Claims & capabilities

Supports 20+ LLM providers. Community-maintained.

Technical surface

API surface
searched not found
Backend storage
searched not found
Deployment
Both (OSS self-hosted; agixt.com managed cloud implied)
Embedding model
searched not found
Multi-tenancy
searched not found
MCP
searched not found
A2A
searched not found
OpenTelemetry
searched not found

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 (48 cited facts, 2 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
    • Compliance “Enterprise-ready features claimed (OAuth, multi-tenancy, advanced security) but no SOC 2 / GDPR / HIPAA certificati…” → “Enterprise-ready features claimed (OAuth, multi-tenancy, advanced security)” source
    #223