Comment by nowittyusername

Multi agent systems work just fine IMO, a lot of articles I read where the writer tests a hypothesis, the issue operational foundation of the test was flawed. When set up properly it works really well. I wont go in to all the details of how i use mine but ill give some brief ideas. I call my systems cohorts, and each cohort usually consists of at least 3 agents. All 100% independent of each other. Usually consisting of a Manager, doer, and the reviewer. Manager works at a lot slower cadence and delegates work, approves, shuts down and so on... among many other things like questioning the premise, gated checks etc... Doer is straight forward that's the work horse that does most of the development and reviewer checks all the work. Naively just this setup will work but not nearly as well when set up properly. The important distinction is the operational agents.md document which has a guide on things like when and how to question the premise, trying to prevent sycophancy, taking a step back at certain intervals to question direction of project and scope of the code and many other things that make sure every participant also constantly looks out to prevent blind trust in his cohort mates. Its a relatively small guide compared to the system prompt of each agent but works well imo. This works well enough though there are caviats, its slow. Though the time i spend debugging shit and coming back to interact with my agents has significantly dropped. meaning while each feature takes longer to implement, when its implemented it almost always is just how i wanted so reduces interaction time between me and the cohort. I take that trade off as i have less things to worry about and can focus my energies elsewhere like walking around in circles of my apartment babbling to myself like a schitzo tiger in a cage...