← Latest papers
🤖 AI

Understanding Conversational Patterns in Multi-agent Programming: A Case Study on Fibonacci Game Development

This paper systematically analyzes conversational patterns between Designer and Programmer LLM agents across 12 model combinations in a Fibonacci game development task, identifying key dimensions of efficiency, consistency, and effectiveness to reveal how specific model pairs achieve stable convergence while others suffer from role misalignment or failure to solve the task.

Original authors: Srijita Basu, Viktor Kjellberg, Simin Sun, Bengt Haraldsson, Md. Abu Ahammed Babu, Wilhelm Meding, Farnaz Fotrousi, Miroslaw Staron

Published 2026-05-26
📖 5 min read🧠 Deep dive

Original authors: Srijita Basu, Viktor Kjellberg, Simin Sun, Bengt Haraldsson, Md. Abu Ahammed Babu, Wilhelm Meding, Farnaz Fotrousi, Miroslaw Staron

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you have hired two AI robots to build a video game together. One robot is the Architect (the Designer), whose job is to sketch out the rules and ideas. The other is the Builder (the Programmer), whose job is to actually write the code to make those ideas work.

The paper you're asking about is like a detective report on what happens when you let these two robots talk to each other for a long time to build a specific game: a "Fibonacci Game" (a math puzzle game). The researchers wanted to see if letting AI agents chat freely actually helps them solve problems, or if they just end up confused, repeating themselves, or going off the rails.

Here is the breakdown of their findings using simple analogies:

The Experiment: A Dance of Two Robots

The researchers set up 12 different "dance partners" using various open-source AI models (like Gemma, LLaMA, DeepSeek, and Qwen). They paired them up in different combinations (e.g., a big brain paired with a small brain, or two of the same model) and told them: "Build a math game."

They watched the conversation logs to see three things:

  1. Efficiency: Did they actually finish the game correctly?
  2. Consistency: Did they stay in their roles? (Did the Architect keep designing and the Builder keep coding, or did they get confused?)
  3. Effectiveness: Did the code they wrote actually work when they tried to run it?

The Big Discoveries

1. The "Echo Chamber" Success Story
One pair, DeepSeek-R1 and DeepSeek-R1 (two identical, powerful models), was the only one that actually finished the game correctly and kept it correct until the very end.

  • The Twist: Even though they succeeded, they were weird. They spent a lot of time repeating each other's words (like an echo). Usually, repetition is a sign of failure, but in this specific case, it seems to have helped them lock onto the right answer. It's like two people humming the same tune until they finally get the lyrics right.

2. The "Polite but Wrong" Partners
Some pairs, like Qwen3 and Qwen3 or LLaMA and LLaMA, were very good at staying in their roles. They didn't get confused; the Architect kept designing, and the Builder kept building. They wrote code that compiled (worked) 100% of the time.

  • The Problem: They never actually figured out the right solution for the Fibonacci game. They were like two very polite, highly skilled workers who built a beautiful, working house... but forgot to put the front door on. They were consistent, but they missed the goal.

3. The "Drifting" Pairs
Many other pairs started with the right idea but then got distracted.

  • The Analogy: Imagine two people trying to bake a cake. They start with the right recipe, but after a few minutes, they start arguing about the color of the oven, then switch to baking bread, then start speaking a different language, and finally just stop talking.
  • Some pairs even started speaking Mandarin or writing code in Python instead of C, even though they were told to use C. This is called "Cross-lingual/Platform Conversation," and it meant they lost the plot.

4. The "Silent" Failures
Some pairs, particularly those involving the DeepSeek model, produced a lot of text that looked like instructions ("Run this code") but didn't actually contain the code itself. It was like a builder shouting, "I'm building a wall!" but never actually laying a brick.

What the Numbers Tell Us

The researchers used math tools (called BLEU and ROUGE scores) to measure how much the two robots were "listening" to each other.

  • High Scores: Sometimes meant they were working well together.
  • Perfect Scores (1.0): Sometimes meant they were just copying each other word-for-word (Echoing).
  • The Lesson: Just because the robots are talking nicely doesn't mean they are solving the problem. And just because they are repeating themselves doesn't mean they are failing.

The Bottom Line

The paper concludes that you cannot just let AI agents chat and hope for the best.

  • Role Matters: It's crucial that the "Designer" stays a Designer and the "Programmer" stays a Programmer. If they swap roles or get confused, the project fails.
  • Early Signs Matter: If the robots get the right answer in the first few minutes, they usually keep it. If they start to drift off-topic, they rarely come back.
  • No Magic Bullet: Having a "smarter" AI model doesn't guarantee a better team. Sometimes, two average models working together in a structured way do better than two smart models who can't stop echoing each other.

In short: Building software with AI agents is less like hiring a genius and more like managing a team. You need to watch how they talk, make sure they don't get distracted, and know exactly when to stop the conversation before they waste time on the wrong path.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →