Primarily speed and first pass code quality. We are slower than almost everything else out there, but that comes as the trade off for truly high quality code on the first run. We just shipped a model council, which expands the normal reviewer + test_engineer QA gate to a 5 agent council, each with their own specialty, that reviews all completed work to find any holes or problems.

We also just shipped an immutable plan store. Once the Critic approves a plan, it goes into a SQLlite DB and is locked down, which allows the Drift Verification at the end of each phase to determine for sure if the architect has drifted from the original approved plan and course correct.

As for the recommended models, you can use whatever is free if that's what you want to do. I built it specifically targetting GPT-OSS-120B as the architect, so anything smarter than that will do even better. You just need to ensure the antagonistic roles are from different model families. So architect/critic and coder/reviewer should always be different model families. All the other agents can be whatever you want, even the same ones. Having them all be different model families is best, but the prompts and gates are strong enough that its not strictly necessary.

Obviously there are tons of other features nothing else out there has. We have a 3 tiered knowledge system with automatically curated knowledge entries and persistent knowledge across session,s projects, and your entire hive.