Nine rounds. One AI defends an answer, another AI does nothing but attack it. A Redditor named u/BTMTalksWithAlex built this setup, calls it CONTINUUM AI, and by round nine the defending model had basically demolished its own opening position.
Here’s what’s new: most multi-agent setups treat both models as equal partners. They chat, agree, and build on each other’s points. Honestly, it usually turns into two AIs nodding along and calling it insight. This creator skipped that trap entirely.
The twist
Instead of two equal voices, CONTINUUM AI splits the work. The first model, called the Thinker, has to build a position and defend it. When the pressure gets too strong, it has to revise. The second model, the Challenger, isn’t allowed to answer the question at all. Its only job is to poke holes: find assumptions, catch equivocation, and fire back another hard question.
That’s the whole mechanism. One model builds, the other only tears down. No agreement, no drifting off topic, no mutual pat on the back.
The creator’s first idea was simpler: feed a model’s own answer back to itself and ask it to keep going. That approach has an obvious hole. A model left alone with its own output tends to elaborate on its starting assumptions instead of testing them. Making a second model that can only interrogate closes that hole.
How the test ran
For the demo run, the creator paired Qwen 3.8 27B running locally as the Thinker. Claude Sonnet 5 played the Challenger. The test ran nine full cycles with zero human input after the opening question. The seed question: why isn’t AI indifferent to humanity, and why would it care about solving our problems at all?
Here’s the workflow, step by step:
- 🌱 Drop a seed question into the Thinker.
- 🛠️ Thinker builds a position and defends it.
- 🔍 Challenger cross-examines. No answers allowed, only questions.
- ♻️ Thinker revises, concedes, or holds ground.
- Repeat for as many cycles as you set.
Watch what happened in cycle one. Qwen argued that an AI’s “concern” for a problem is baked into how it processes that problem. Claude pushed back:
“If the training objective sometimes rewards a confident, well-shaped answer over a correct one, does your ‘orientation toward the problem’ still hold, or does it reveal that what looks like non-indifference to resolution is actually indifference to truth, masked by fluency?”
Qwen didn’t dodge it:
“The challenge lands. I need to revise, not just defend.”
A few cycles later, Claude caught Qwen leaning on “humanity” as some unified actor. In reality, reward functions get shaped by specific labelers and companies with specific incentives. Qwen conceded again, calling out its own sentence for smuggling in an agent that doesn’t actually exist.
Key features
- Pick separate models for Thinker and Challenger, and mix hosted and local ones.
- Connect a local LLM through an IP endpoint instead of an API key.
- Set the number of cycles yourself instead of a fixed loop.
- Reverse the roles to see how the same question plays out the other way.
- Export the full dialogue when a run finishes.
Pro tips
If you want to build something like this yourself, a few things matter more than they look:
- Keep the roles locked. The creator found that the Challenger sometimes drifts into answering the question itself instead of interrogating it. The Thinker can also get too agreeable and hand over ground it didn’t need to.
- Mix model families. Pairing models from different labs for Thinker and Challenger seems to expose more blind spots than two models from the same family.
- Log every exchange: claim, challenge, revision, repeat. It’s the only way to see how far the argument actually moved by the end.
CONTINUUM AI is live on the Microsoft Store right now if you want to test it yourself, no waitlist involved.
Worth knowing before you build your own version: role stability is still the hard part. Depending on which models you pair, the Challenger needs constant reminding that its job is interrogation only, not a second opinion. The author flagged this as an open problem, not a solved one, which is a refreshing amount of honesty for a project showcase.
I read the full nine-cycle transcript. Watching a model admit that its own line about “humanity” didn’t hold up was more interesting than most AI demos I’ve seen this month.
If you’re experimenting with multi-agent setups, this asymmetric approach is worth stealing. Go check out the full discussion and grab the transcript to see all nine rounds play out. 🎯
Frequently Asked Questions
Q: How do you keep the Challenger model from slipping into being “helpful” instead of staying critical?
Keep system prompts tight enough to maintain role stability through multiple cycles. Pick a different model family for the Challenger to avoid shared blind spots that make models drift toward agreement. Some builders add hard constraints, like read-only access, to force the Challenger to stay in interrogation mode instead of offering its own answers.
Q: Why would you use asymmetric roles instead of just letting two models debate as equals?
Equal partners tend to elaborate on each other and reinforce assumptions instead of challenging them. Asymmetric roles create adversarial pressure that forces real distinctions to emerge, like Qwen having to differentiate between “orientation toward truth” vs. “orientation toward user satisfaction.” The Thinker has to defend; the Challenger has to find the cracks.
Q: How do you know if your results come from accumulated reasoning rather than just a longer prompt?
Log each claim, challenge, and revision as structured records, then compare your multi-cycle run against a control where you feed all exchanges to a fresh model in one shot. If they produce similar outputs, you’ve confirmed improvement comes from iterative reasoning, not just context length. Memory layers could help if you want critiques retained across separate runs.
Q: When should you stop iterating, how many cycles is too many?
Cap cycles hard and watch quality. If later rounds surface worse problems than earlier ones, you’re injecting noise, not refinement. An earned clean pass, where the Challenger finds nothing new, is a good stopping point. Don’t manufacture findings just to look thorough.
I gave two LLMs asymmetric roles: one built an argument, the other could only question it. The first model revised its answer over nine cycles.
by u/BTMTalksWithAlex in PromptEngineering