I too used to be a skeptic of the whole "agent-swarms" hype. But I do find some patterns useful with ultracode:

- parallelism: "if it makes sense, use ultracode to do this thoroughly" Claude decides if this is the type of task that can benefit from a dynamic workflow. For example where there is a large number of similar independent sub-tasks, it can choose to set up a dynamic workflow, and it even sets up verifiers/tests etc to validate its work. In some cases it pushes back and decides not to set up a dynamic workflow and instead works on the task directly.

- verification loops: "Set up a dynamic workflow with adversarial checkers, and iterate until they are all green, up to some sensible limit". Similarly, I can include code-simplification steps and documentation-update steps.

These patterns help me leave it unattended for longer periods of time and return to a reasonable assurance of correct code.

I'll sometimes use agent swarms for triaging quickly through a number of possible issues. For example, a single request for a code review to uncover all possible issues, followed by an agent swarm to dig deep into each issue to confirm or mark false positive.

I got a security scan by route for one of our services that was pretty good and raised some useful results. Uses are few and far between for me tho tbh, also really expensive. I usually run a single agent with a subagent or two MAX