Topic starter
18/08/2026 2:19 pm
TL;DR: Long-running loops outgrow context windows, compaction loses critical IDs, and pod restarts force replay decisions that can duplicate side effects or reopen the same PR, according to Edge Delta. The real control problem is durable execution, not just more iterations, because agent state must survive both memory pressure and crash recovery.
Editorial analysis by NHI Mgmt Group, based on content published by Edge Delta: “Agents That Run for Hours Without Forgetting, or Going Broke”.
Key questions
Q: What breaks when agent loop memory is compressed too aggressively?
A: Over-aggressive compression can drop the exact IDs, counts, timestamps, and prior decisions the agent needs to continue safely.
Q: Why do long-running agent workflows need replay protection?
A: Because a multi-hour workflow will eventually restart, and anything already pushed outside the system must not be executed again.
Q: How do teams know if agent memory controls are actually working?
A: Look for evidence that sensitive data stays bound to the correct identity, that memory entries can be traced and removed, and that replay tests do not produce cross-session leakage.
Practitioner guidance
- Define durable execution for agent workflows Record completed steps, side effects, and returned values so a restart resumes from saved state instead of rerunning external actions.
- Preserve exact identifiers during compaction Require summaries to retain IDs, counts, timestamps, file paths, error messages, and prior decisions, and reject any summary that invents or truncates facts.
- Treat replayable actions as idempotency-sensitive Assign stable identities to commits, PRs, tickets, or other external actions at first execution and reuse those identities on recovery.
Bottom line: Long-running agent loops fail when state is treated as disposable chat history instead of governed memory.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
18/08/2026 3:11 pm
Durable execution is the real control plane for agent memory. Long-running agentic workflows fail less because the model stops reasoning and more because the system treats memory as disposable conversation history. Once an investigation crosses the context boundary, the platform must preserve exact IDs, decisions, and action results as governed state. For IAM and NHI programmes, that shifts the design problem from prompt quality to lifecycle control over agent state.
A question worth separating out:
Q: What is the difference between context compaction and durable execution?
A: Context compaction reduces the working history so the model can keep operating, while durable execution preserves the identity and result of side effects across restarts. Compaction is about what the model remembers, but durable execution is about what the system guarantees will not happen twice. Both are needed, but they solve different failure modes.
👉 Read our full editorial: Agent loop memory and replay controls fail without durable context