A hub-and-spoke system's "Policy Lookup" subagent consistently returns irrelevant policy sections, even though the correct policy area was identified in the coordinator's earlier conversation. What is the correct diagnosis and fix?

Question

Accepted Answer

B. The coordinator is not explicitly passing the relevant policy query to the subagent because subagents do not inherit parent context. Context isolation is the root cause: the subagent receives no information from the coordinator's conversation unless it is explicitly passed. The coordinator must include the specific policy area or query details in the invocation message. Option D (forwarding entire history) is the opposite of best practice — it defeats context isolation, inflates token costs, and introduces irrelevant information into the subagent's context.

A hub-and-spoke system's "Policy Lookup" subagent consistently returns irrelevant policy sections, even though the correct policy area was identified in the coordinator's earlier conversation. What is the correct diagnosis and fix?

Related Questions

Discussion