Human Feedback Types
missingNone explicit
No explicit feedback protocol extracted.
"LLM agents benefit from using memory systems to improve performance on long-horizon, multi-session tasks."
HFEPX · Eval paper review
David H. Yang, Blake Bullwinkel, Amanda Minnich, Mohammad Mohammadi Amiri +1 more
Published
Nov 6, 2026
Citations
0
Trust level
Low
Usefulness score
0/100 (Low)
Extraction confidence
15% (Low)
Derived from extracted protocol signals and abstract evidence.
Rater population
Not reported
Signals refreshed
Nov 6, 2026
This paper is adjacent to HFEPX scope and is best used for background context, not as a primary protocol reference.
Use this as background context only. Do not make protocol decisions from this page alone.
All signals on this page are inferred from the abstract only and may be inaccurate. Do not use this page as a primary protocol reference.
Best use
Background context only
Use if you need
A secondary eval reference to pair with stronger protocol papers.
What to verify
Read the full paper before copying any benchmark, metric, or protocol choices.
Main weakness
This paper looks adjacent to evaluation work, but not like a strong protocol reference.
Treat as adjacent context, not a core eval-method reference.
If you are doing eval pipeline work, start here
LLM agents benefit from using memory systems to improve performance on long-horizon, multi-session tasks. However, memory introduces a critical attack surface. Malicious instructions encountered in one session may be stored and propagated through memory before being retrieved and acted upon in later sessions. Because memory systems differ in how they process and retrieve information, the downstream effects of poisoning can vary significantly across systems. To quantify the effects of poisoning across different memory architectures, we introduce MemoryDojo, a benchmark for tracing the lifecycle of poisoned information through agent memory and measuring its influence on subsequent agent behavior. MemoryDojo is easily extensible, consists of 155 multi-session long-horizon trajectories covering four domains, and supports five different memory systems. Through our evaluation, we find that all memory systems are susceptible to memory poisoning, with substantial variation in downstream effects. We further propose a memory-aware poison optimization process that increases the poisoning efficacy, highlighting differences between memory architectures. We hope that MemoryDojo will support research on understanding and mitigating agentic memory risks.
These are the protocol signals we could actually recover from the available paper metadata. Use them to decide whether this paper is worth deeper reading.
None explicit
No explicit feedback protocol extracted.
"LLM agents benefit from using memory systems to improve performance on long-horizon, multi-session tasks."
None explicit
Validate eval design from full paper text.
"LLM agents benefit from using memory systems to improve performance on long-horizon, multi-session tasks."
Not reported
No explicit QC controls found.
"LLM agents benefit from using memory systems to improve performance on long-horizon, multi-session tasks."
Not extracted
No benchmark anchors detected.
"LLM agents benefit from using memory systems to improve performance on long-horizon, multi-session tasks."
Not extracted
No metric anchors detected.
"LLM agents benefit from using memory systems to improve performance on long-horizon, multi-session tasks."
No benchmark or dataset names were extracted from the available abstract.
No metric terms were extracted from the available abstract.
LLM agents benefit from using memory systems to improve performance on long-horizon, multi-session tasks.
Based on abstract + metadata only. Check the source paper before making high-confidence protocol decisions.
Human feedback protocol is explicit
No explicit human feedback protocol detected.
Evaluation mode is explicit
No clear evaluation mode extracted.
Quality control reporting appears
No calibration/adjudication/IAA control explicitly detected.
Benchmark or dataset anchors are present
No benchmark/dataset anchor extracted from abstract.
Metric reporting is present
No metric terms extracted.