SlackDominic MarksProblem & solution
Managing context in long-run agentic applications
Summary
Long-running multi-agent systems struggle with context management because accumulating raw message histories degrades inference quality, increases latency, and exceeds context window limits. In a collaborative security investigation platform, passing unrestricted history can also introduce confirmation bias across specialized agents. To maintain coherence across unbounded rounds of investigation, the system eliminates raw message history carryover between invocations. Instead, it coordinates agents through three structured context channels: a Director's Journal for orchestration memory, a Critic's Review that scores findings to filter hallucinations, and a Critic's Timeline of validated chronological events. This architecture provides agents with tailored context without overwhelming their inference capacity.
Context
In long-running multi-agent security investigations spanning hundreds of inference requests, accumulating complete message history between API calls consumes context window capacity, increases latency and cost, and degrades response quality. Furthermore, sharing excessive unfiltered message history across specialized agents can encourage confirmation bias and stifle independent reasoning.
Approach / What changed
The architecture replaces raw inter-round message history accumulation with three specialized context channels. A Director agent maintains a structured Journal containing categorized entries such as decisions, observations, findings, questions, actions, and hypotheses to track investigation progress. A Critic agent evaluates domain Experts' findings to produce a credibility-scored Review report and constructs a chronological Timeline of credible events.
Takeaways
Rather than passing full raw message histories across invocations, long-running agent workflows can prevent context window exhaustion by utilizing structured online context summarisation channels.
The Director's Journal acts as a shared working memory categorized into six entry types: decisions, observations, findings, questions, actions, and hypotheses.
The Critic agent filters hallucinations and misinterpretations by validating expert findings against cited tool artifacts and assigning credibility scores to generate reviews and timelines.
Source and freshness
- Source
- slack.engineering
- Published
- Added to Yomu
- Last updated
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.