2026-07-08

AI Agents

A new security paper shows that Unicode's TAG block—invisible glyphs in every mainstream renderer—can smuggle tool metadata past a human's MCP approval dialog while reaching the model verbatim, and only that one encoding evades both the eye and string sanitizers. A companion fuzzer turns up 40 real bugs in LangChain, LlamaIndex, and CrewAI. Two more papers rethink agent memory, plus one on runtime trajectory repair.

5 papers 0 news 0 blogs 20 appendix 474 considered

Papers

5

LogicHunter: Testing LLM Agent Frameworks with an Agentic Oracle

arxiv:arxiv-software-eng — Minghui Long, Yanjie Zhao, Haoyu Wang 8/10 evalsframeworkssafety
Agent frameworks are hard to fuzz: defects surface as ordinary exceptions or silent semantic failures rather than crashes, and Pydantic type governance makes naive fuzzers emit mostly invalid inputs. LogicHunter fuses formal type constraints with real-world usage patterns to synthesize inputs that are valid by construction yet semantically extreme, then resolves oracle ambiguity with a ReAct-based agent that reads docs, walks source, and inspects runtime state. It finds real bugs across LangChain, LlamaIndex, and CrewAI—a concrete win for testing infrastructure you already depend on.

Unicode TAG-Block Concealment of Tool-Metadata Payloads in the Model Context Protocol: An Approval-View Fidelity Gap Across Three Independent Server Implementations

arxiv:arxiv-agents — Mohammadreza Rashidi 8/10 safetytool-use
MCP renders tool metadata once in an approval dialog, then injects it verbatim into the model every turn—and nothing requires the rendered view and the delivered bytes to match. The author isolates that gap and shows Unicode's TAG block (U+E0000–U+E007F) has no glyph in mainstream terminals, chats, or IDEs, so a payload written in it is invisible to reviewers but survives byte-for-byte into the tokenizer. Across 8 techniques on a real JSON-RPC/stdio harness, all reach the model, 4 evade a string sanitizer, and only the TAG-block encoding is fully invisible.

From Passive Retrieval to Active Memory Navigation: Learning to Use Memory as a Structured Action Space

arxiv:arxiv-agents — Yue Xu, Yutao Sun, Yihao Liu, Mengyu Zhou, Jiayi Qiao, Lu Ma, Kai Tang, Wenjie Wang, Xiaoxi Jiang, Guanjun Jiang 8/10 memorytool-use
NapMem treats long-term user memory as a structured action space rather than a passive retrieval channel. It organizes history into a multi-granularity pyramid—raw conversations, typed records, topic tracks, profiles—linked by provenance, and exposes each level as a tool the agent learns to query via reinforcement learning. On PersonaMem-v2, LongMemEval, and LoCoMo it is competitive on memory-intensive tasks while largely preserving general reasoning and tool-use on non-memory tasks. The ablations over navigation, granularity, and RL training are the part worth reading.

AgentTether: Graph-Guided Diagnosis and Runtime Intervention for Reliable LLM Agent Operation

arxiv:arxiv-software-eng — Chenyu Zhao, Shenglin Zhang, Wenwei Gu, Yongqian Sun, Dan Pei, Chetan Bansal, Saravan Rajmohan, Minghua Ma 8/10 observabilitysafetymulti-agent
AgentTether does runtime repair without touching the underlying agent or environment. It abstracts each run into Transition Units, links them through a dependency-aware Critical Transition Graph, and localizes failure-critical subtrajectories by combining an offline normal-behavior model with a run-local detector—then converts the cause into behavior-scoped guidance backed by cross-iteration repair memory. On 261 tau-bench tasks across three domains with Qwen3.7-max, it repairs 59% of the hardest Banking failures and transfers cross-model to GPT-5.4. Diagnosis beats blind retry; the localization step is what makes the guidance grounded.

Memory in the Loop: In-Process Retrieval as ExtendedWorking Memory for Language Agents

arxiv:arxiv-agents — Yusuf Khan, Carlo Lipizzi 8/10 memorycost-latencyinfra
This challenges the assumption that in-loop retrieval is too slow. The authors argue latency is a property of where the store lives, not the pattern: an in-process store answers in ~100us, three orders below a network round trip, so reading and writing memory every step stops costing anything. Holding a fixed latency budget and varying only store speed, redundant actions rise monotonically with latency—0 of 12 in-process versus 7.2 of 12 at 110ms (p=0.0079). Recall climbs from 0/5 to 3.6-4.8/5, though an instructed restate baseline also solves it.
20 more items the ranker flagged but didn't feature

Papers

Blogs