I started using Pi with Astra on a whim after really enjoying Astra and reading somewhere that you get close to identical results as with the codex harness but for a significant hunk less token usage.

Coming from mostly using Claude models, the terse factual statements coming from Astra via the Pi harness are a breath of fresh air over having to wade through the flowery verbose nonsense that Claude constantly outputs

I recently had Astra review a fairly detailed design doc I have for an audio VST fork, that I originally wrote with Opus and/or Fable a few months ago. The doc reaches deep into signal flow and module topology while lifting most of the DSP code from other open-source projects. I had it review for feasibility and architectural soundness.

Astra found a number of flaws that would have come up during implementation and we worked through them. But then I had Fable 5.1 review that document and it found a number of issues with Astra's changes, the least of which had was that Astra duplicated a lot of technical notions that it added rather than using references to an authoritative section. It also flagged some of Astra's designs as technically impossible, pointing out why and I'm actually in the process of digesting its feedback and updating the design spec. (I hand-review each point and we work through a solution together -- I don't trust either model to come up with something that follows my vision on their own)

I'm not promoting one or the other, I just found it interesting how this sort of adversarial review found pretty significant flaws in the other model's work. I am curious as to whether this process will eventually converge on a document that both agree on or if the models are going to perpetually nitpick each other.

I haven't actually started implementation yet, so maybe one or the other is full of shit. Just trying to come up with an architecturally sound design for something I want to write, when I lack the DSP knowledge to be able to write it myself. But the intent is to pass an agent the design doc and list of milestones and let it handle implementation.