← Latest papers
🤖 machine learning

OMAC: A Holistic Optimization Framework for LLM-Based Multi-Agent Collaboration

This paper introduces OMAC, a general framework that holistically optimizes Large Language Model-based Multi-Agent Systems by identifying five key dimensions and employing specialized algorithms for both single and joint optimization, thereby achieving superior performance in complex tasks like code generation and reasoning compared to state-of-the-art approaches.

Original authors: Shijun Li, Hilaf Hasson, Joydeep Ghosh

Published 2026-04-22
📖 5 min read🧠 Deep dive

Original authors: Shijun Li, Hilaf Hasson, Joydeep Ghosh

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 are trying to solve a massive, incredibly difficult puzzle. You could try to do it alone, but you'd likely get stuck or make mistakes. So, you decide to hire a team of experts: a coder, a mathematician, a logician, and a creative writer. This is what Multi-Agent Systems (MAS) are: a group of AI "agents" working together to solve complex problems.

However, there's a catch. Usually, when humans build these AI teams, they act like rigid managers. They say, "You, the coder, talk to the mathematician. Then, the writer talks to the coder." They design the team structure and the rules by hand, guessing what might work best. If the team fails, they have to start over from scratch, guessing again.

OMAC is a new framework that changes the game. Instead of a human guessing the best team structure, OMAC is like a super-smart "Team Coach" that automatically figures out the perfect way to organize, train, and direct the AI team.

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

1. The Five Levers of Improvement

The authors realized that to make an AI team better, you only need to tweak five specific things (like adjusting the dials on a radio). They call these the "Five Dimensions":

  • Fixing the Players (Agent Functionality): Maybe the "Mathematician" agent is bad at explaining its steps. OMAC rewrites its instructions to make it clearer.
  • Hiring New Players (New Agents): Maybe the team is missing a "Editor." OMAC creates a new agent from scratch to fill that gap.
  • Picking the Starting Lineup (Candidate Selection): Not every problem needs all 10 agents. OMAC learns to pick the best 3 or 4 for the specific task at hand.
  • Deciding Who Talks When (Dynamic Participation): In the middle of a conversation, maybe the "Coder" needs to stop talking and let the "Tester" speak. OMAC learns to switch roles dynamically.
  • Managing the Handoffs (Communication Flow): Who should send their notes to whom? OMAC learns to route information so the right person gets the right data at the right time.

2. The Two Magic Tools

To tweak these five levers, OMAC uses two special AI tools that work together in a loop:

  • The "Creative Brain" (Semantic Initializer):
    Imagine a brainstorming session. This tool generates a bunch of different ideas for how the team could work. It might say, "What if the coder writes comments in the code?" or "What if we hire a 'Safety Inspector'?" It creates a wide variety of initial team setups.

  • The "Strict Judge" (Contrastive Comparator):
    This is the critical part. The team tries out these new ideas on practice problems. The Judge then looks at the Winners (the team setup that solved the puzzle perfectly) and the Losers (the setup that failed).

    The Judge doesn't just pick the winner; it asks, "Why did the winner win and the loser lose?"

    • Example: "The winner included a 'Safety Inspector' who caught a bug. The loser didn't have one."

    Based on this comparison, the Judge tells the Creative Brain: "Okay, next time, make sure every team has a Safety Inspector, and make the instructions for the coder more specific."

This cycle repeats: Brainstorm → Test → Compare → Refine. Over and over, the team gets smarter and the structure gets tighter.

3. The "One Thing at a Time" Rule

You might think, "Why not change the players, the lineup, and the communication rules all at once?"

The paper explains that if you change everything at once, you get confused. It's like trying to fix a car engine, change the tires, and repaint the car all in the same minute. You won't know which change actually made the car run better.

OMAC uses an Iterative Approach: It changes one thing (like the instructions for the coder), tests it, and locks it in. Then it moves to the next thing (like the lineup). By changing one thing at a time, it knows exactly what is working.

4. The Results

The researchers tested OMAC on three tough challenges:

  1. Writing Code: Can the AI team write software that doesn't crash?
  2. General Reasoning: Can the team answer tricky questions about history, science, and law?
  3. Math: Can the team solve complex math problems?

The Outcome: OMAC consistently beat the best existing methods. It didn't just make the team slightly better; it made them significantly smarter. And because it figured out the most efficient way for the agents to talk, it actually used less computing power to get better results.

The Big Picture

Think of OMAC as the difference between a human manager trying to guess the best way to run a company, and an AI coach that runs thousands of simulations every day to find the perfect strategy.

Instead of us humans manually designing how AI agents should talk and work, OMAC lets the AI teach itself the best way to collaborate. It's a "self-improving" system that builds better teams, faster and smarter than we ever could by hand.

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 →