/ Paper arXiv 2611.14320
Curator's notes
WikiTrace links each memory insightinsightA concise lesson extracted from a trajectory about why it succeeded or failed. to its original trajectorytrajectoryThe sequence of actions and observations recorded while solving a task., letting LLM agents verify and correct lessons, reducing performance drops from faulty memory.
The system stores why a past answer worked and lets the AI check that reason before using it again, preventing mistakes.WikiTrace links each memory insightinsightA concise lesson extracted from a trajectory about why it succeeded or failed. to its original trajectorytrajectoryThe sequence of actions and observations recorded while solving a task., letting LLM agents verify and correct lessons, reducing performance drops from faulty memory.WikiTrace augments LLM agents with evidence-linked memory, coupling concise insights to trajectorytrajectoryThe sequence of actions and observations recorded while solving a task. summaries and raw traces, enabling on-demand verification and correction during inference.Curator's notesWritten by AI from the paperReport a mistake
What's new
Introduces evidence-linked memory storing raw trajectories with insights, enabling agents to check and amend lessons on the fly, unlike prior memory that lacks traceability.
Key result
WikiTrace consistently outperforms existing memory approaches on five benchmarks while reducing memory-induced degradationmemory-induced degradationPerformance loss caused by an agent following incorrect or misapplied stored lessons..
Why it matters
Builders can create more reliable LLM agents that learn from experience without harming future task performance.
Why this ranked
MeasuredPublic numbers, not AIHow ranking works
54 / 100#3 of 198 papers that day, from GitHub, Hugging Face, Hacker News and Semantic Scholar, looked up the morning it was ranked.
Builder evidence20.1 / 40
- Code released
- ★ 19 GitHub stars
- +4 stars since the day before
Community attention18.1 / 30
- ▲ 65 upvotes on Hugging Face
- 0 points on Hacker News
Author track record11.2 / 15
- Authors' median h-index 7.5 (Semantic Scholar)
- From KAIST (a known lab)
What the paper shows4.7 / 15
- Less like recent papers than 94% of that day's candidates
Abstract
From the paperThe authors' own words.
External memory enables LLM agents to improve from experience by distilling trajectories of past tasks into concise lessons for new tasks. However, memory can also lead to memory-induced degradation, where an agent fails on tasks it would solve without memory, often because it follows a lesson that is incorrect, or misapplies or misreads a valid one. This is because lessons are inferred from trajectories labeled only with task success or failure, yet are typically provided without the trajectories they came from, leaving the agent no way to check them. To address this, we introduce WikiTrace, an evidence-linked memory system designed to let agents check each lesson against its original trajectory. Specifically, motivated by the finding that a trajectory often still holds the evidence needed to catch an erroneous lesson, WikiTrace stores each lesson as a concise insight linked to a summary of why its trajectory succeeded or failed and to the raw trajectory itself. Then, on a new task, the agent starts from all insights and, whenever one lacks details needed to act, conflicts with another, or comes from a failed task, descends through its links with terminal tools to fill in missing details or correct the insight before acting. We validate WikiTrace on five agentic benchmarks, showing that it consistently outperforms existing memory approaches and a baseline given the same insights alone, while also reducing memory-induced degradation. Our code is available at https://github.com/yukyeongleee/wikitrace
From the full paper
From the paperCopied from the paper itself by our code.
Reading the paper on arXiv…
What you could build
Written by AIIntermediateRequires integrating retrieval, summarization, and tool-use pipelines with LLMs.
- Implement a tutoring bot that revises its advice by consulting original solution steps.
- Create a game AI that checks past strategies against recorded play logs before reusing them.
- Develop a code assistant that validates suggested snippets against the execution traces that generated them.
Try it
Code, models and demos that use this paper.
- Code:
- ★ 10 on GitHub ↗
Ask this paper
/ Ask a questionAnswers come from the full paper and name the section
/ Quiz yourself
How does WikiTrace allow an agent to handle a lesson that lacks needed details on a new task?
The agent follows the lesson's links to the summary and raw trajectory, using terminal tools to retrieve missing information or correct the insight before acting.
/ Your notes
Select text in the abstract to highlight it or add a note. They stay in this browser.