A support multi-agent solution uses a triage agent, a billing specialist, and a technical specialist. After a user corrects an earlier account number, the technical specialist continues troubleshooting the wrong account because it only saw the first message. What should you implement so agents behave correctly with evolving conversation context?
Select an answer to reveal the explanation.
Short Explanation
You want context-aware multi-agent behaviors so shared session context updates on corrections and each specialist receives the current account identity before tool calls. If the user fixes the account number, the next specialist must see the corrected value, not the old one. Freezing early messages, raising temperature, or wiping history won't keep identity propagation reliable.
Full Explanation
Correct answer — implement context-aware multi-agent behaviors so shared session context is updated on corrections and each specialist receives the current account identity before tool calls. Context-aware multi-agent behaviors require disciplined context management across agents: accumulate relevant turns, update on corrections, retrieve current entities, and inject them before tool use. Shared session state carrying the authoritative account identity prevents specialists from acting on superseded values. The option that stores only the first user message in long-term vector memory and bans agents from reading later turns freezes the first message in long-term memory and maximizes stale-entity risk. The option that increases temperature on all agents so they invent plausible account numbers when context is stale increases variability and fabrication; it does not fix identity propagation. The option that deletes conversation history after every agent hop to force each specialist to ask the user to restate everything harms UX and does not implement structured context sharing. Exam tip: corrections must invalidate prior entity bindings in shared multi-agent context.