Efficient LLM Collaboration via Planning
The paper proposes COPE, a test-time collaboration framework where small and large language models alternately act as planners and executors in a multi-stage cascade, achieving performance comparable to large proprietary models while drastically reducing inference costs.
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 complex task to solve, like fixing a broken engine or solving a tricky math puzzle. You have two helpers available:
- The Local Handyman: A small, free, and fast worker who lives right in your garage. They are great at simple jobs but sometimes get stuck on complicated problems.
- The Master Architect: A huge, expensive expert who lives in a distant, high-tech tower. They can solve almost anything, but hiring them costs a fortune every time you ask for help.
The problem is: If you hire the Master Architect for every single job, you'll go broke. If you only use the Local Handyman, they might fail on the hard stuff.
This paper introduces a new way to work called COPE (Collaborative Planning and Execution). It's like a smart team-up system that lets these two workers collaborate efficiently without wasting money.
How COPE Works: The "Plan First" Strategy
Instead of just asking the Handyman to "fix the engine" and hoping for the best, COPE uses a Planning step. Think of a "Plan" as a quick, high-level map or a set of instructions written before the actual work begins.
Here is the step-by-step process of how they collaborate:
Stage 1: The Handyman Tries to Lead
The Local Handyman tries to do the whole job alone. First, they write a quick "Plan" (a simple goal or guideline) for themselves, and then they try to solve the problem based on that plan.
- The Check: If the Handyman is very confident they got it right (like if they tried it three times and got the same answer), they finish the job. It's free and fast!
- The Fail: If they are unsure or the answer looks shaky, they don't give up. They move to Stage 2.
Stage 2: The Architect Draws a Map, The Handyman Builds
Now, the expensive Master Architect steps in, but only for a moment. The Architect doesn't do the heavy lifting yet. Instead, they write a new, better Plan (a clearer map) based on the problem.
They hand this new Plan to the Local Handyman. The Handyman then tries to solve the problem again, but this time they are following the Architect's expert map.
- The Check: If the Handyman, guided by the Architect's map, feels confident, they finish the job. You only paid for a tiny bit of the Architect's time to draw the map, saving a lot of money.
- The Fail: If the Handyman is still stuck even with the map, they escalate to Stage 3.
Stage 3: The Architect Takes Over
If the first two steps didn't work, the Master Architect finally does the whole job themselves—both planning and executing. This is the most expensive step, but it only happens when absolutely necessary.
Why This is a Big Deal
The paper found some surprising things about how this teamwork works:
- Big brains help small brains: When the Master Architect writes the plan for the Handyman, the Handyman gets much smarter. It's like a student suddenly understanding a math problem after a professor explains the strategy (the plan), even if the student does the actual calculations.
- Small brains can confuse big brains: Interestingly, if the Handyman tries to write the plan for the Master Architect, it actually makes the Architect perform worse. The Architect is so smart that a simple, low-quality plan from the Handyman can actually distract them. This is why the system is designed so the Architect only plans for the Handyman, not the other way around.
- It saves money without losing quality: In tests involving math, coding, and even complex agent tasks (like a robot navigating a house), COPE achieved results that were just as good as, or even better than, using the Master Architect alone. However, it cost 45% to 75% less because the expensive Architect was only called in for the hardest parts or just to draw the map.
The Bottom Line
COPE is like a smart manager who knows when to let the local worker do the job, when to ask the expert for a quick tip (the plan), and when to call the expert to do the whole thing. By using "Planning" as a lightweight bridge between a small model and a large model, it allows them to work together efficiently, solving hard problems without breaking the bank.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.