Users report that a long-running multi-agent planning session “forgets” constraints agreed in the first ten minutes once the transcript grows large, even though no code bug resets state. Traces show oldest turns disappearing from the prompt assembly. Which context-window issue is this, and what is the best remediation direction?
Select an answer to reveal the explanation.
Short Explanation
Answer A. The blueprint lists sliding-window amnesia among context-window issues to diagnose. When oldest turns fall out of the active window, early constraints vanish unless you compact history and persist critical facts for re-injection. GPU, DNS, and image sizes are unrelated to conversational context loss.
Full Explanation
Correct answer: A. Diagnose context window issues including sliding-window amnesia, summary drift, vector-only recall, and entity continuity problems. Sliding-window amnesia appears when prompt builders keep only the newest N tokens/turns; early requirements silently drop. Remediation: hierarchical summaries, structured constraint stores, and retrieval of “must keep” entities into each new turn.
B is incorrect: hardware throttling might slow responses but does not selectively drop early dialogue turns from prompts.
C is incorrect: DNS issues affect connectivity, not prompt content selection.
D is incorrect: graphics assets are irrelevant to multi-agent context windows.
Also watch for summary drift if compaction itself rewrites constraints incorrectly—validate summaries against source constraints.