I made a desktop app that allows you to queue agent roles to communicate and work on structured projects. Lets you easily define roles, protocols, templates, projects, and work-packets. Useful or nah?
First of all, I'm not charging for this in any capacity. If people say they will find this useful I'll either open-source it or give it away for free.
I built ACC (Agent Control Center) as a way to "automate" the refactoring and optimization of a project I've been working on. The project was highly technical (molecular simulation) so I found that having the agent approach the code with a certain behavioral bias was actually beneficial. For instance I had an agent just focus on optimizing the mathematics, another optimizing the architecture, and another doing micro-optimizations in the kernels.
The way this works is you have a top level AGENTS/CLAUDE.md file, a context file, role AGENTS/CLAUDE.md files, protocols, templates, projects, and work-packets. When an agent is ran it reads the top level file and the file for their role. The top level file gives a brief description of the project (your typical claude.md file), and the role file gives the agent a behavioral bias (for example, I made my QA a strict, snarky mf who would check every test and future failure case).
In their role file there are links to the protocols you assign to this role with a description of when to use the protocol. A protocol has assigned templates so the agent populates things in an expected format. protocols are just small units of behavior (skills essentially).
You can set a "project initiative", and with the default protocols roles will propose projects to meet that initiative and break that project into smaller units of work called work-packets. A role will fulfill their duties on a work-packet, populate an "artifact" attached to the packet describing what they did, then assign the work-packet to the next role.
All of this is easy to do in the UI. You can directly interact with the CLI, set/read AGENTS/CLAUDE.md files, set/read protocols, assign protocols to roles, make/read templates, link templates to protocols, create/manage projects, create/manage work-packets, set project initiative, set what each role dos/doesNot own, blah blah.
What are peoples thoughts on this? On one hand if you just list out all the deliverables and requirements in one markdown one agent could act as all roles, and having multiple agents could just be a waste of tokens. On the other hand if that list of deliverables and requirements gets too big it can overcrowd the context window and hurt the models performance. Another cool thing about roles is I can do things like assign my "doer" to be claude, and my QA to be codex to kind of get the best of both models (for the cost of both ;( ).