← Latest papers
💻 computer science

QueenBee Planner: Skill-Evolving Communication Topologies for Token-Efficient LLM Multi-Agent Systems

The QueenBee Planner framework enhances token-efficient LLM multi-agent systems by treating inter-agent communication topologies as a self-improving design skill, where a learnable planner generates optimal message-passing structures that significantly outperform fixed or cold-start baselines in accuracy and cost while distilling execution traces into robust, falsification-resistant design rules.

Original authors: Congjia Tian, Yuhang Yao, Jiaming Cui

Published 2026-06-29
📖 5 min read🧠 Deep dive

Original authors: Congjia Tian, Yuhang Yao, Jiaming Cui

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 a team of 8 brilliant but isolated experts (the "workers"). Each expert has a small piece of a giant puzzle (a "shard" of data), but none of them can see the whole picture. Their job is to figure out the final answer, but they can only do it by talking to each other.

The big question the paper asks is: How should these experts talk to each other?

Should they all shout at once? Should they form a circle? Should they pass notes in a line? Or should they form a specific hierarchy where some people collect notes and pass them up?

In most computer systems, engineers pick one way to connect these experts (a "fixed topology") and stick with it. This paper introduces QueenBee Planner, a system that doesn't just pick a connection style; it learns how to design the best conversation flow for the job, getting smarter every time it tries.

Here is how it works, broken down into simple concepts:

1. The "Architect" vs. The "Workers"

Think of the system as having two distinct roles:

  • The Workers: These are the experts doing the actual math or reasoning. In this system, they are frozen. They don't learn anything new; they just do their job exactly as they always have.
  • The QueenBee Planner: This is the "Architect." It doesn't do the math. Its only job is to draw a map (a "communication DAG") that says: "In Round 1, Expert A sends a note to Expert B. In Round 2, Expert B merges that with their own notes and sends it to Expert C."

The magic is that the Architect learns. It tries different maps, sees which ones get the right answer with the least amount of talking, and remembers the good ones for next time.

2. The "Skill Bank" (The Architect's Notebook)

Instead of just guessing, the Architect keeps a notebook of "Design Skills." These aren't answers to specific puzzles; they are rules about how to connect people.

  • Preserve: "Hey, this specific way of passing notes worked great last time. Let's keep doing it."
  • Modify: "This note-passing pattern worked, but we have a slightly different puzzle now. Let's tweak it a bit."
  • Avoid: "Last time we tried this specific pattern, everyone got confused and the answer was wrong. Never do that again."

3. The "Safety Gates" (Preventing Bad Habits)

The paper is very careful about how the Architect learns. It knows that sometimes you get a lucky guess or a fluke success. If the Architect just memorized every lucky win, it would start making bad decisions.

So, the system has strict "Safety Gates" before it writes anything into the notebook:

  • The "Held-Out" Test: The Architect can't just say, "I did well on the practice test, so I'm smart." It has to prove it can do well on a new test it hasn't seen before.
  • The "Lucky Run" Check: If a design only worked once by chance, the system ignores it. It needs to see the design work consistently before adding it to the notebook.
  • The "Falsification" Check: If the Architect comes up with a fancy explanation for why a design works, the system tries to prove it wrong. If the explanation can't survive the test, the design isn't added.

4. The Results: Smarter Maps, Less Noise

The researchers tested this on two types of tasks:

  1. Counting Frequency (CF): A task where the team has to count how many times numbers appear in a giant list.
  2. Silo Tasks: A task where information is hidden in separate "silos," and the team must coordinate to find the global answer.

What happened?

  • Fixed Topologies: When the team used a pre-set connection style (like a standard tree or a circle), they made mistakes and used a lot of "tokens" (computer energy/money).
  • Cold Generation: When the Architect tried to draw a map from scratch without any memory, it was unstable and often wrong.
  • QueenBee (Self-Evolving): After a few rounds of learning, the Architect started drawing hybrid maps. These maps were often simpler and more direct than the fixed ones.
    • In the counting task, the QueenBee system reduced errors by 37% and cut the cost (messages and computer calls) by more than half compared to the best fixed method.
    • In the "Silo" tasks, the system learned to coordinate better than even a "perfect" fixed map could.

The Big Takeaway

The paper argues that the architecture (how agents are connected) is just as important as the intelligence of the agents themselves.

By treating "how to connect agents" as a learnable skill rather than a fixed setting, the system learns to build better communication networks over time. It doesn't just memorize answers; it learns the blueprint for solving problems efficiently. The workers stay the same, but the way they talk to each other evolves to become faster, cheaper, and more accurate.

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 →