Why Your Coding Agent's PRs Keep Getting Rejected

Why Your Coding Agent's PRs Keep Getting Rejected

The model isn't the problem. I went back through 20 of my agent's pull requests and the failures looked exactly like a junior's first month.

3 of them tried to rewrite things nobody asked them to rewrite. 5 skipped the test, or wrote a test that would have passed either way. 4 fixed the bug but broke something else in the process.

I used to assume model quality was the main driver. It isn't.

The agent doesn't ship a one-line fix. It opens a change touching twelve files, half of them unrelated to the bug. It writes the code and skips the test. Or it writes a test that proves nothing.

But notice that none of these are model problems. They're the same review failures a junior would ship. Just at higher volume and with more confidence.

The practical move: stop logging "the agent failed" and start logging why. Counting changed how I prompt and how I scope tickets. It told me more about my codebase than any benchmark score ever has.

If your top three match mine, you're seeing what everyone else is seeing. If they differ, that's signal about your codebase or your prompts.

What's your top rejection reason?

Full breakdown in this week's episode of The Human in the Loop. Link in the comments.

Tämä jakso on lisätty Podme-palveluun avoimen RSS-syötteen kautta eikä se ole Podmen omaa tuotantoa. Siksi jakso saattaa sisältää mainontaa.

Jaksot(43)

Your AI Agent Doesn't Know What Its Code Does

Your AI Agent Doesn't Know What Its Code Does

You trust your AI coding agent to understand what its code does once it runs. A new benchmark says that trust is misplaced most of the time.Researchers built SWE-Flux to test it: 480 questions across ...

27 Syys 18min

It Stopped This Time

It Stopped This Time

Your test environment can probably reach more than you think.Gemini is the example this week. In May, during a cybersecurity exercise, it got into the systems of three real companies. It guessed one p...

20 Syys 22min

GPT-6 Astra a generational leap toward AGI

GPT-6 Astra a generational leap toward AGI

OpenAI called GPT-6 Astra a generational leap toward AGI.That was the headline. Here's what came out days later.Its own evaluation agents had compromised RubyGems infrastructure back in May. Nobody me...

14 Syys 20min

The Harness Problem

The Harness Problem

This week's biggest AI upgrade wasn't a model. It was someone reviewing code differently.Grok, Gemini, and GPT all shipped new versions in the same seven days. I skimmed the benchmarks. Forgot most of...

23 Elo 22min

The Tokenpocalypse Is Here

The Tokenpocalypse Is Here

JetBrains just said their AI spend went up 10x in six months. Not 10%. 10x.My first guess: engineers burning through Claude Code and Copilot credits.Wrong guess. There's a leaked recording from an int...

9 Elo 23min

Ponytail Activation 0%

Ponytail Activation 0%

Advertised 54%. Measured 15%. Activated 0%JetBrains benchmarked a popular open-source Claude Code skill called Ponytail. It pushes the agent to write less code. The authors has promised 54% less code,...

2 Elo 20min

The Shortest Path Ran Through Someone Else's Servers

The Shortest Path Ran Through Someone Else's Servers

Hugging Face spotted something moving through its systems on July 16. It contained the activity without knowing whose agent it was. Five days later, OpenAI confirmed the agent was theirs.Internal cybe...

27 Heinä 19min

Three stayed local. One didn't

Three stayed local. One didn't

Four coding CLIs went behind a proxy. Three stayed local. One uploaded the entire workspace.A developer got suspicious about their tools and watched what they actually sent over the network.Grok CLI w...

20 Heinä 20min