(.NET) With a multi layered system with agents as tools, how should threads and shared chat message store be used?

[lukemarsh135]

For context - im building a multi agent system that at the lowest level of agents can call APIs. I have an 'orchestrator' agent which delegates user requests to other agents. Under that agent, i have around 13 category agents (ProductsAgent, CustomerAgent etc), and each one of those agents has versioned category agents under it (ProductsV1Agent, Customer V1Agent, CustomerV1.1Agent and so on).

These versioned agents can make api calls to endpoints based on dynamically loaded open api docs taken from swagger, and then broken down into rest api operations that the versioned agents can see.

The issue we're getting is that when a request requires multiple tool calls in different categories, the communication/information sharing between the 3 layers of agents isnt as good as we need it.

So one of my questions is, should each agent have its own thread and a single shared chat message store that the thread 'points' to, or should there only a single shared thread and a single shared message store? Initially, we designed it with the latter, but now have shifted it to a thread for each agent and one chat message store. This still hasnt fixed the issue of communication - its almost like the agents have been lobotomised and have lost all common sense: asking the user for details it should be able to fill out itself (based on system prompts and agent instructions), not communicating required info to other agents, based on info in the open api json document

I hope i explained my issue and question well enough, thanks in advance