Introduction An obscure quirk of the /proc/*/mem pseudofile is its “punch through” semantics. Writes performed through this file will succeed even if the destination virtual memory is marked unwritable. In fact, this behavior is intentional and actively used by projects such as the Julia JIT comp
MemGPT
Memory-GPT (MemGPT) - Towards LLMs as Operating Systems - Teach LLMs to manage their own memory for unbounded context!
nanomem: An Extremely Simple, Inference-Time Memory Module
nanomem is an extremely simple, user-owned memory module that casts memory management as LLM calls / agent loops on a markdown file tree. You interact with the tree with natural language commands like nanomem add <fact>, nanomem retrieve <query>, and nanomem import <chatgpt>. As such, nanomem is by design interpretable, partitionable, portable, and versioned.
Woah. Letta vs Mem0. (For AI memory nerds)
365 votes, 55 comments. I’m an absolute AI memory nerd, and have probably read every proposal made about memory, and demoed virtually all of the…
The Memory Walled Garden
The gap between first and third party memory systems
Understanding memory management
Learn MemGPT memory management techniques for controlling LLM context windows with in-context and external storage.
mem-agent: Equipping LLM Agents with Memory Using RL
The insights and the technical report behind Mem-Agent, our 4B model for persistent memory in LLMs
A practical guide to WebAssembly memory | radu's blog
Memory in WebAssembly is one of the topics that creates confusion for newcomers, particularly for those with experience in languages with memory management features like garbage collection, such as JavaScript, Go, or Java. In this article we explore using memory in WebAssembly in various scenarios - passing JavaScript arrays to Rust and AssemblyScript modules, checking for some basic memory leaks using Valgrind, or exchanging strings between runtimes and modules using Wasmtime.
kyju.org
Horribly misusing Rust features to provide provable memory safety and tracing garbage collection for pointer soup.
I Benchmarked OpenAI Memory vs LangMem vs Letta (MemGPT) vs Mem0 for Long-Term Memory: Here’s How They Stacked Up
145 votes, 53 comments. Lately, I’ve been testing memory systems to handle long conversations in agent setups, optimizing for: Factual consistency…
CaviraOSS/OpenMemory
Local persistent memory store for LLM applications including claude desktop, github copilot, codex, antigravity, etc.
OpenMemory - AI Memory MCP Server for Coding Agents | Mem0
With OpenMemory, add persistent, project-aware memory to Cursor, Windsurf, and VS Code agents. Store preferences, patterns, and context that get retrieved automatically.
Inference Time Memory Module | Research | Tiles
Simple inference-time memory module that treats memory management as a series of LLM calls and agent loops over a markdown-based file tree.
Memory system - Please Leave here your opinions (if you have any) · Issue #74 · code-yeongyu/oh-my-openagent
I heard many people wants that memory system- but it's really easy to be redundant from my experiences. Projects like claude-mem or many others have memory system. Want to hear your opinions re...
Been tinkering with what cloud functions could look like on AT Proto by storing WASM blobs. Influenced by the IPVM design of my big brain former co-workers from Fission github.com/avivash/at-functions
GitHub - avivash/at-functions
github.comBeen tinkering with what cloud functions could look like on AT Proto by storing WASM blobs. Influenced by the IPVM design of my big brain former co-workers from Fission github.com/avivash/at-functions
GitHub - avivash/at-functions
github.comi can’t help but think we’re far from nailing memory systems this one here is extremely interesting. two LLMs at once, one just managing and surfacing memory for the other
Asa
I'm not a fan of the decoupled 'memory retrieval → task execution' loop, so my agent has a subconscious background thread that looks for relevant, unique memory context in its experiential database while it runs and injects it on top of the live context window.
