What Should Agents Say? Action-state Communication for Efficient Multi-Agent Systems
This paper introduces PACT, a protocolized action-state communication framework that compresses free-form natural language exchanges in multi-agent systems into compact records, significantly reducing token usage and inference costs while maintaining or improving task performance across various system topologies.
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
The Problem: The "Over-Share" Meeting
Imagine a team of detectives (agents) trying to solve a mystery. In current systems, every time one detective finishes their work, they write a massive report and paste it into a shared notebook for the next detective to read.
This report includes:
- The final answer.
- The clues they found.
- But also: Every random thought they had, every dead end they explored, every time they re-read a clue, and a long, rambling explanation of how they thought.
The Issue:
As the investigation goes on, this shared notebook gets huge.
- It's expensive: Reading a 100-page notebook costs a lot of money (in this case, "tokens" or computing power).
- It's slow: The next detective has to read all that noise before they can get to the new clues.
- It's confusing: The important facts get buried under pages of "I thought about this, then I thought about that."
The paper argues that we are currently letting agents "over-share" their private thinking process, which clogs up the system.
The Solution: PACT (The "Executive Summary" Rule)
The authors propose a new rule called PACT (Protocolized Action-state Communication and Transmission).
Think of PACT as a strict rule for the team's shared notebook: "No rambling allowed."
Instead of pasting the whole messy draft, an agent must now translate their work into a compact, three-part "Action-State Record" before passing it on:
- ACTION: What did I just do? (e.g., "I searched the database.")
- STATE: What evidence did I find? (e.g., "I found a receipt from 1995.")
- RESULT: What is the useful output? (e.g., "Here is the receipt image.")
The Analogy:
- Old Way: Detective A hands Detective B a 50-page diary of their entire day, including what they had for breakfast and every thought they had while walking to the store.
- PACT Way: Detective A hands Detective B a sticky note that says: "I went to the store (Action), found a receipt for a blue car (State), and here is the photo (Result). Now you check the car registry."
What They Found
The researchers tested this idea in two different ways:
- Split Evidence: Two agents had to share clues to solve a puzzle.
- Assembly Line: Four agents worked in a line (Planner → Critic → Refiner → Solver).
They compared PACT against five other ways of communicating (like sending the full text, just the conclusion, or a short summary).
The Results:
- No "One Size Fits All": They found that no single way of talking worked best for every situation. Sometimes sending just the conclusion worked; sometimes sending the full text was okay.
- PACT Wins: However, PACT was the most consistent winner. It saved a massive amount of "money" (tokens) while keeping the team just as smart, or even smarter.
- In their tests, PACT reduced the amount of data sent by about 39% on average.
- In real-world coding tools (like OpenHands and SWE-agent), it cut the data usage by nearly 50% without breaking the code.
Why It Works
The paper explains that the next agent in the chain doesn't need to know how the previous agent thought. They only need to know:
- What action was taken.
- What the current situation (state) is.
- What the result is.
By filtering out the "internal monologue" (the private thinking) and only sharing the "public facts," the system becomes faster, cheaper, and less likely to run out of memory.
The Bottom Line
The paper concludes that we shouldn't just let AI agents chat in free-form, unstructured paragraphs. Instead, we should force them to follow a strict "protocol" where they only share the essential updates (Action, State, Result). This turns a chaotic, expensive conversation into an efficient, high-speed relay race.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.