MemGPT deep reading

Series · 1 posts

← Back to Paper Reading

  • MemGPT: Treat Context as Paged Memory — Do Not Mistake the OS Metaphor for Enterprise Memory

    Intermediate Agent runtime, safety, and evaluation
    MemGPT deep reading: Part 1 , Note: Aug 27, 2026 , Paper: 2023 , AI Engineering

    A deep read of Packer et al., arXiv:2310.08560 v2: finite context as RAM, OS-like tiers, and function-mediated paging. DMR moves GPT-4 from 32.1% to 92.5%; nested KV shows multi-hop lookup—not ACL memory governance.

    Understand it in 90 seconds
    Problem
    Fixed-length context windows break long conversations and long-document analysis; naively lengthening transformer context raises quadratic cost, and long windows still may use middle tokens poorly.
    Core insight
    Do not start by buying a bigger RAM stick. Treat the LLM’s prompt tokens as main context (RAM), keep chat history and document stores in external context (disk), and let function calls decide what to write out, retrieve, and evict—like OS virtual-memory paging.
    Strongest evidence
    On Deep Memory Retrieval (Table 2), GPT-4 fixed-context accuracy is 32.1% versus 92.5% with MemGPT; GPT-4 Turbo moves 35.3% → 93.4%. On Nested KV (Figure 7), fixed-context models fall to 0% at deeper nesting while MemGPT+GPT-4 keeps multi-hop lookup alive.
    Main boundary
    The system depends on tool/function-call fidelity; the paging policy is itself an agent decision that can store or drop the wrong facts; the evidence is dialogue consistency plus sampled/synthetic document tasks—not ACL, audit, or rollback memory governance. Later Letta productization is not this paper’s experiment artifact.
    Read the full deep dive

For speaking invitations, internal engineering sessions, or architecture exchange, see the topics and public work I can bring into the conversation.

Speaking & contact