Meta AI uses a second AI agent as a memory coach to keep long tasks on track

Meta AI uses a second AI agent as a memory coach to keep long tasks on track Jonathan Kemper View the LinkedIn Profile of Jonathan Kemper Aug 2, 2026 GPT‑Image‑2 prompted by THE DECODER During long tasks, AI agents often forget constraints, repeat failed commands, and rediscover errors they've already diagnosed. Meta AI's proposed memory module tracks that information and decides when to remind them. In a new paper, Meta AI researchers describe how these failures play out. An agent recognizes a constraint early on but later violates it while fixing an unrelated bug. It sees that a command failed, then tries a nearly identical version soon afterward. It diagnoses an error pattern but later treats the same pattern as new. The authors call this "behavioral state decay." The state that guides the agent's decisions gets scattered across a growing task history. It can become buried deep in the context window or fall out of it altogether. Even when the information remains in the transcript or context window, it may no longer reliably shape the agent's behavior. Meta AI says simply giving agents access to longer histories doesn't solve the problem. Deciding when memory matters Existing memory systems focus on storing, updating, and retrieving information. According to the paper, that works well for personalization and recall across sessions. But agents working through a task face another problem. The system must decide when a memory is useful enough to bring back. Too few reminders lead to repeated mistakes, while too many add latency, consume tokens, and distract the agent from its current work. This goes beyond summarization: a summarizer just decides what information to retain where Meta's system decides whether a stored execution state should influence the agent's next move. Since failure modes vary widely by task, a fixed summarization rule can't make that call reliably. A second agent decides when to speak up The proposed system pairs an unmodified "action agent" with a separate "memory agent." At fixed intervals, the memory agent reviews a sliding window of the most recent steps and updates a structured memory bank. It then decides whether to add a brief reminder to the action agent's next call or stay silent. The authors say the module can work with existing agents and harnesses as a plug-and-play component. Unlike a general advisor model, it provides only memory-based reminders and doesn't offer broader strategic advice. The Memory Agent runs alongside the unmodified Action Agent and decides at each scheduled check whether to add a reminder or stay silent. | Image: Meta The memory bank has three sections. A private status field tracks progress and outstanding risks and is never shown to the Action Agent. Knowledge Memory stores stable facts such as requirements, file paths, and configurations. Procedural Memory records what the agent tried and what happened, including failed commands, successful fixes, and rejected hypotheses. During each memory step, the agent can update the bank only through predefined tool calls rather than freely overwriting its contents. It then decides whether to reactivate a stored state and, if needed, writes a targeted reminder. Choosing not to intervene is part of the policy. In Phase 1, the agent updates its structured memory bank. In Phase 2, it decides whether any stored memory should shape the Action Agent's next decision. | Image: Meta Selective reminders improve scores on two benchmarks The researchers tested the system on Terminal-Bench 2.0, which evaluates autonomous agents in realistic command-line environments. They also used tau2-Bench, which tests conversational tool use in the airline, retail, and telecom sectors. Claude Opus 4.6 served as the memory agent, though the model has since received several