← All IntelClip / AI ToolsThe A/B test design: same builder model, different orchestrator
From Fable 5 & Qwen 27B – Traycer Multi-Agent Hands-On Test! · ≈13:57
Holding the builder model fixed and forbidding the orchestrator from writing code isolates how much of the output quality comes from orchestration alone.
What’s in it
- Holding the builder model fixed and forbidding the orchestrator from writing code isolates how much of the output quality comes from orchestration alone.
Clip transcript
as an orchestration agent and things like that. So I want to do just some AB testing to see how well the same exact model can build something when given a different orchestration agent. So we're starting with Fable 5 and I've told that you're going to be directing Quen 3.627B to build a realistic flight simulator game. The reason I want to use this prompt is because visually we'll be able to tell the differences between how this orchestrates that model versus how 56 Soul does or something else. And it's also just kind of fun to play. It's going to begin from the pilot's POV in a passenger jet starting on the runway. It should have interactive flight controls, detailed scenery of the ground, and be overall well done. You are not going to help code it. You are going to guide it as a skilled adviser would do. And then I'm telling it the quen model is being used through open code because I have that one selected right there. And we can see it did just actually create this sub agent for open code which has that model already selected. So I'm happy to
Comments
Checking sign-in…
Loading comments…