← Latest papers
🤖 machine learning

Flat Score, Amplified Failures: How the Error Budget Masks Damage in Quantized LLM Agents

This paper reveals that while standard benchmarks suggest 4-bit quantization is lossless for multi-turn LLM agents, it actually amplifies existing failure modes by up to 2.5×\times within a fixed error budget, a hidden degradation that only becomes visible through per-channel error analysis and stricter success criteria.

Original authors: Jiwon Jang, Kisu Yang, Heuiseok Lim, Hyunwoo Park

Published 2026-07-31
📖 6 min read🧠 Deep dive

Original authors: Jiwon Jang, Kisu Yang, Heuiseok Lim, Hyunwoo Park

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 building a robot butler to help you with chores. You want it to be fast and not eat up all your computer's memory, so you decide to shrink its brain. You take its complex instructions and compress them down, like squashing a giant, fluffy cloud into a tiny, dense marble. In the world of artificial intelligence, this is called "quantization." Scientists have spent years testing this, and they've found that if you just ask the robot a simple question once—like "What's the weather?"—it seems to work perfectly fine even after being squashed. It's like saying the robot is "nearly lossless," meaning it lost almost nothing important.

But here's the twist: real life isn't just one simple question. It's a long conversation where the robot has to open doors, check the fridge, call a plumber, and fix mistakes along the way. This is called being an "agent." The big question scientists wanted to answer was: Does that "nearly lossless" claim still hold true when the robot is doing a complex, multi-step job? If the robot makes a mistake, can it fix it, or does the whole mission crash? This paper dives deep into that exact scenario, looking at whether squashing the robot's brain hides a ticking time bomb that only shows up when things get complicated.


The Flat Score and the Hidden Explosion

The researchers set up a massive experiment using a simulated world where AI agents act as customer service helpers. They tested these agents in two different "neighborhoods": a Retail store (where the agent just talks to a database) and a Telecom company (where the agent has to talk to a simulated user who is also fiddling with their own phone). They took several different AI models and ran them at full precision (the fluffy cloud) and then at 4-bit precision (the tiny marble).

The result? On the standard report card—the "Final Score"—everything looked perfect. The squashed models scored almost exactly the same as the full-size models. In fact, in most cases, the difference was so small it was statistically invisible. It looked like the compression was free! The authors call this a "flat score."

But then, they started looking under the hood, at the actual steps the robot took. That's when they found the explosion.

The Amplifier Effect

While the final grade stayed the same, the squashed models were actually making way more mistakes along the way. In the Telecom neighborhood, the 4-bit models started hallucinating (making things up) about 2.5 times more often than the full-size models.

Here is the most surprising part: The squashed models didn't invent new mistakes. They didn't start calling tools they never knew before. Instead, they just took the same mistakes the full-size model made occasionally and turned up the volume on them.

Think of it like a radio. If a full-size model occasionally picks up a bit of static (a mistake), the 4-bit model doesn't create new static; it just cranks the volume knob until that same static is deafening. In one specific case, the model went from making 649 "hallucinated tool calls" (calling tools that don't exist) to 1,646 calls. It was the exact same list of wrong tools, just shouted at much higher frequency.

The Safety Net That Hides the Danger

So, if the robots were making 2.5 times more mistakes, why did their final scores stay the same?

The answer lies in the rules of the game. The benchmark they used allows the robot to fail up to 10 times in a single episode before it counts as a total failure. It's like a video game where you have 10 lives. The full-size robot might miss a jump once or twice, but it recovers. The squashed robot, however, misses the jump 2.5 times as often. But because it still has 10 lives, it keeps recovering, keeps trying, and eventually finishes the level.

The "Error Budget" (those 10 lives) acts like a giant safety net that absorbs all the extra falls. The final score stays flat not because the robot is unharmed, but because the game is too forgiving. The damage is real, but it's hidden in the noise of the retries.

The "Tighten the Belt" Test

To prove this, the researchers played a clever trick. They took the safety net and shrank it. Instead of allowing 10 mistakes, they only allowed 2.

Suddenly, the mask fell off. When the budget was tight, the squashed models crashed hard. The gap between the full-size model and the 4-bit model exploded from a tiny 1.3 points to a massive 16.7 points. The squashed model failed because it didn't have enough "lives" left to recover from all its extra mistakes.

This test confirmed two things:

  1. The damage was real and hidden by the lenient rules.
  2. The damage only happened where the model was already prone to making mistakes. Some models (like the Qwen-3.6) were so good at their job that they barely made any mistakes to begin with, so squashing them didn't change anything. But for models that already had a "tendency" to hallucinate, squashing them made that tendency much worse.

The Fix: Stop the Leak, Don't Patch the Hole

The researchers also tried to fix the problem. Instead of trying to make the whole robot smarter, they gave it a simple rule: "If you try to call a tool that isn't on the list, stop and ask for a new one."

When they added this simple "reflexive repair," the squashed models in the damaged area saw their scores recover significantly, rising from a low of 65.4% back up to 71.3%. This was a major improvement over the damaged 4-bit version and even slightly higher than the original full-size model's score of 66.7% in that specific scenario. However, this fix only worked where the specific "leak" existed; in models that weren't prone to these specific mistakes, the repair didn't help and sometimes even slightly lowered the score. This proved that the problem wasn't that the robot's brain was broken; it was just that it kept reaching for the same few wrong tools over and over again.

The Takeaway

The big lesson here is that a good final score doesn't mean a safe robot. If you are building an AI agent that has to do complex tasks, you can't just look at the final grade. You have to look at the process.

If you compress an AI model to save space, you might not be creating new problems, but you could be turning up the volume on the ones that already exist. And if your system has a big safety net (like allowing many retries), you might not even notice the volume is turned up until the net gets too small to catch the falls. The paper suggests that before we start squashing AI brains for real-world use, we need to check if the model is already prone to making mistakes, because if it is, the compression will make those mistakes much louder.

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 →