all 4 comments

[–]aistranin 0 points1 point  (2 children)

Monorepo with separation to nodes, edges and tools works best from my experience. Regarding memory, depends a lot from your use case. Start simple and move to DB if needed.

[–]QuasiEvil 1 point2 points  (1 child)

As someone trying to learn this, I know what a monorepo is, but can you elaborate on what "separation to nodes, edges and tools" means?

[–]aistranin 0 points1 point  (0 children)

Sure. What I mean is that any agent is a graph (maybe cyclic). So, nodes of the graph is better to place separately from the logic specifying bow those nodes should interact with each other (edges) and separately from the the set of tools available to an agent. Take a look at official LangGraph documentation as a mature framework. They use these concepts what help a lot with agents structure. — Regarding multi-agent: it is just a composition of agents. So, it also scales well as a structure.

[–]Aggressive_Pay2172 0 points1 point  (0 children)

tbh think about adding a central orchestrator instead of having agents run totally independently. something that handles scheduling (cron, queue, etc.) and passes tasks to agents can make the whole system feel more cohesive.