Skip to main content
Search

# Persistent Memory

9 related articles

Subscribe to updates
  1. QwenLM/qwen-code

    Qwen Code turns the coding agent into a long-lived service, letting browser, editor, SDK and automation clients share one session

    QwenLM has released Qwen Code, an open-source AI coding agent whose entry points span the terminal, IDE plugins, a desktop app, a Web UI, SDKs and chat integrations including Telegram, DingTalk, WeChat, WeCom and Feishu. It ships with Auto-Memory, Skills, SubAgents and MCP, plus Agent Teams, Agent Arena and Dynamic Workflows, some marked experimental or opt-in. A daemon mode lets browser, editor, SDK and automation clients share one agent session, and clients can reconnect to active sessions.

  2. arXiv

    Agents stop writing every lesson to memory: FGSE tests each update for transfer, falsification and regression first

    Long-running LLM agents often write each episode's lesson straight into memory, yet local success is not a reliable sign of reusable, safe knowledge. FGSE turns every candidate lesson into a structured hypothesis with a precondition, behavior change, expected effect and verifier, applies it only in a temporary state, and tests it on target-transfer, falsification and archived-regression probes before committing, narrowing or rejecting it. On verifier-rich benchmarks including WebArena, AppWorld and τ-bench, FGSE with a DeepSeek-V3.1 backbone reaches 39.8 WebArena success rate and 78.8 AppWorld average completion, while cutting falsification failures, regression damage and harmful committed updates to 5.0%, 1.3% and 3.6%.

  3. MongoDB | Blog

    Vercel AI SDK gets persistent memory: MongoDB's open-source integration stores chats, facts and events in Atlas

    MongoDB released and open-sourced an integration that turns MongoDB Atlas into the persistent memory store for AI applications and agents built with the Vercel AI SDK. The SDK itself ships no database, so an application previously started every conversation with no knowledge of the last one, and developers had to design schemas, write cleanup jobs and set up vector search themselves. The integration sorts memories into session, semantic, procedural, episodic and scratchpad types with separate retention policies, and creates vector indexes automatically while detecting embedding dimensions at startup.

  4. Claude Code stops forgetting between sessions: claude-mem captures tool observations and writes semantic summaries for later sessions

    claude-mem gives Claude Code persistent memory across sessions: it automatically captures tool-usage observations during a session, generates semantic summaries, and makes them available to future sessions, so Claude keeps continuity of knowledge about a project after sessions end or reconnect. Installation runs through npx claude-mem install or the plugin marketplace, and the installer configures everything before asking the user to sign in and choose a memory provider.

  5. arXiv

    Sensors stop re-uploading similar scenes: on a hit, six bytes retrieve the stored image

    Memento sends sensor observations by reference: the device searches a vector table in persistent memory for a similar past sample and, on a hit, transmits only an index, and modeling shows that on low-rate links such as LoRa a 25% hit rate cuts latency and energy by roughly a quarter.

  6. arXiv

    LiveMACEBench evaluates five frontier LLM agents over 30 days of live markets and finds return rankings diverge sharply from capability metrics

    The work introduces LiveMACEBench, a process-aware benchmark that uses live cryptocurrency and U.S. equity markets as a naturally evolving testbed in which five frontier LLMs run continuous paper-trading trajectories under matched Base, Tool Use, Persistent Memory, Rule Following, and Multi-Agent Collaboration configurations, evaluated through both realized outcomes and trace-derived diagnostics; across roughly 30 days it finds a pronounced outcome–capability gap, with return rankings fluctuating and often diverging from capability-specific measurements while similar outcomes arise from markedly different patterns of mechanism use.

  7. arXiv

    Galahad turns LLM document reading into a one-time cost with byte-exact KV memory: 100 of 100 on a 97,000-token corpus at 0.59–0.64 s per question

    Sietse Schelpe of Corbenic AI presents Galahad, a memory layer in which Taliesin saves and reloads byte-exact KV state and Blaise passes the model only the section a question needs; on a recall test with 100 facts hidden in a 97,000-token corpus (Gemma 4 31B), Taliesin alone answered 98 of 100 on llama.cpp at 3.0 s and 572 J per question against 10 of 100, 9.3 s and 2,754 J without Galahad, and with Blaise added the model answered 100 of 100 on all three runtimes at 0.59–0.64 s and 200–213 J, while a tuned RAGFlow pipeline answered 77.

  8. arXiv

    APM-Bench tests cross-session persistent memory for streaming video assistants across 549 sessions and 104 life trajectories, finding existing methods struggle to combine recall, latency, and storage

    The work introduces APM-Bench, which reformulates egocentric streaming interaction as multi-session life trajectories (549 sessions, 104 trajectories, 2,719 candidates, averaging 69 minutes of video per trajectory) and evaluates general video models and eight specialized memory systems on cross-session understanding, real-time perception, and adaptive response, plus an evidence-availability-aware test; results reveal a clear utility-latency-storage trade-off: raw video memory gives the strongest cross-session performance but needs GiB-scale storage and high latency, text summaries cut storage to the KiB scale at the cost of cross-session performance, event-structured memory shows the strongest utility among specialized systems, and adaptive response remains difficult even with rich history

  9. Asana runs AI agents as role-scoped teammates with shared memory and public activity feeds, and details three deployments in sales Q&A, renewal-risk digests, and engineering loops

    Asana Chief Product Officer Arnab Bose describes how Asana runs AI agents as "AI teammates" inside its existing Work Graph: agents are built around roles (such as content writer, insights analyst, project manager, work intake specialist, campaign analyst, or campaign coordinator) with pre-built skills and integrations, distinct identities and controlled permissions, effective access bounded by the permissions of the person who triggers them, and coachable shared memory in which only admins and editors can commit feedback to permanent memory; the piece gives three deployments—Slack channel questions turned into Asana tasks and routed to product backlog or enablement documentation updates, an At-Risk Renewal agent producing a daily global renewal-risk digest for executives and regional leade

You’re all caught up