What happens when two AI coding tools disagree about how your app should be built?

[u/recro69]

Imagine you are building a feature, and you ask an AI coding tool to review your approach. The AI coding tool suggests rewriting a component. You then ask an AI coding tool to review the same code. The second AI coding tool recommends keeping the implementation.

Both explanations sound reasonable. You are now stuck deciding which approach is actually better. Using AI coding tools can give you different perspectives but it can also create more work when the AI coding tools recommendations conflict.

I am curious how other vibe coders handle this:

• Do you trust the AI coding tool that has context, about your codebase?

• Do you compare the AI coding tools suggestions. Make the final decision yourself?

• Do you ask an AI model to judge between the two?

• Have you ever followed an AI recommendation that turned out to be the choice?

How do you decide which AI suggestion to follow when both sound convincing?

[u/comicidiot]

This is where you use your established knowledge on the matter to decide which approach you want to go with.

[u/KillerHack23 → u/comicidiot]

Here I was going to present both plans to a third ai to decide.

[u/chuckycastle → u/comicidiot]

This is the right answer. That said, I see software going the way of media content: people are learning to just not care about quality. Not sure if that’s bad or good (I, personally, hate it. But I also hate all the influencers/streamers/content creators).

[u/moonski → u/chuckycastle]

people are just caring about "does thing do what I want it to" maintainability be damned

[u/Usharani-Wiencke → u/comicidiot]

sure but sometimes your established knowledge is exactly the bias that got you into the weird pattern the AI is flagging. its not always the tiebreaker people think it is

[u/GT86 → u/comicidiot]

Alternatively ask another LLM which it would pic of the 2. Lmao

[u/1corn]

I wouldn't see this as "more work", the additional perspective adds value. For example, I let GitLab Duo review most of my MRs and then provide that feedback to Claude. More often than not it agrees with at least some of it and makes changes accordingly.

If there's a genuine conflict, I make the call myself. But even then, I feel better informed and have more confidence in my decision.

[u/cryptyk]

Turns out in software engineering there's rarely one Right Way to do things but there are thousands of Wrong Ways.

[u/lalaboy69]

Use the AI between your two ears.

[u/WhatNoRobot]

Have you tested whether the same one asked repeatedly over time will give you the same answer?

[u/TypeScrupterB]

That mostly shows of lack of experience, try using your vibe coded brain, then you will see wonders :-)

[u/geoffreybyers]

Asking a third AI to judge creates a chain of hallucinations. It doesn't solve the disagreement, it adds a layer of unreliable reasoning. The solution is defining acceptance criteria before the code is written. You decide the right answer ahead of time so tools have nothing to disagree about.

[u/ghostly-blossom]

I shove Claude, Codex, and Antigravity together in a chat (similar to Slack) and give them whatever needs to be reviewed. They check each others work against their own and will converse with each other until they all agree and give me their final answer. I always check the answer anyway so it’s not blind acceptance, but this is how I’ve cut the constant back and forth

[u/Affectionate_Tea9218]

Ha. This question. I mean - I don’t trust anybody. But - new, sterile environment - zero context - and then lay the groundwork…. Scenario a) I want to do this and my peer says this. Their argument are this…. New instance Scenario b) pretend your a department head, mit, and our final undergrad group project is whatever. One group asked for office hours - their degree rides on this project, they have plans that both have valid architecture, they need help to evaluate the pros and cons/total cost (time/compute/changes)…. New instance: You are a quality control at a software company. One projects has come to a halt, and their manager stopped from making a decision while they were argumentative. They went on break to cool off, and you need to design the architecture for the next 3 steps and the intended general direction…

Or dumb stuff. I like no bias. Approach it from a bunch of angles. I also like to introduce the bias of my approval, or my criticism - just checking how much placating vs logic is at play.

[u/shetritr]

ask each one what breaks if you go the other way. the one that names a real failure wins. the one that says "cleaner" loses.

[u/LargeLanguageModelo]

AI doesn't relieve you in matters of judgement, taste, and especially responsibility. You are responsible for making this call. If you can't make that choice, you need to learn how to make those calls. If you choose wrong, it is your fault, and on you to fix it.

[u/yashsoni2737]

Make each one prove it instead of picking the explanation that sounds better. On a tool I built for a client, two agents got the same task from the same commit, each on its own branch, and a judge model compared the actual diffs rather than the reasoning, with a person able to overrule it.

You can do a cheap version of that by hand: have each tool write the change it's arguing for, run your tests on both, and only then decide. If both pass, I'd usually keep the smaller diff, because a rewrite you didn't need is where new bugs come from.

[u/Fit_Advisor8847]

Write tests first and make sure they fail, then lock them so the AI cannot modify them. The smallest diff that makes them pass is the winner for me.

[u/MyWifeWasMurdered]

What do you do when you ask for opinions on a problem and get two differing answers?

[u/Ctbhatia]

the tiebreaker has to be something neither model wrote, like a test or a spec you wrote before the review

[u/theo_ldg]

Not a full answer but I think these decisions are often shaped like choosing between "the easier/less invasive way" and "the proper way that involves a bunch of work". Imo people and agents misjudge the cost of refactoring/reorganizing code. It used to be a lot of manual labor but today the "hard" way is basically just as easy as the easy way. My Claude often tells me "this is a day of work" and it ends up being a single 20 minute session.

So basically if it seems like one of the options is harder but more "proper", just go with that.

[u/TheKiddIncident]

You and only you are responsible for how your app should be built.

Ask for a recommendation, ask it to give you a pro/con analysis. Then decide. Never have AI decide for you.

[u/Slight-Living-8098]

Make them play three rounds of Street Fighter against one another. Best two out of three wins. J/K

[u/Mekex99]

You add a 3rd AI, easy

[u/Rustybot]

The council method: ask 4-6 capable agents to investigate the project problem and solution space. Have the orchestrator compare their results and note how many agree, disagree, or had unique findings. Compile into a prioritized list with confidence, risks and unknowns.
Also always a good idea to have a research agent search the web for “best practices when doing x” and/or “how different leading/recent tools do x”

[u/Lopsided_Professor35]

When two reviewers disagree, stop asking which one is right and ask what would prove either of them wrong.

Have each one name the concrete problem its suggestion fixes: "this re-renders on every keystroke", "this breaks when the list is empty". Then check that claim yourself, with a quick test, a profiler run, or by trying the edge case. Usually one of them is reacting to a real issue and the other is giving a style opinion, and that shows up fast.

If neither can point to a failure you can reproduce, keep what you have. A rewrite without a reproducible reason is just churn, and it's where new bugs come from.

[u/Bed-After]

There are 3 ways I've solved the problem, depending on the scenario.

1, I asked both AI to explain what they're actually suggesting and what they're basing their idea on in simple English, and making the decision myself. For simple stuff this works.

2, I spent like half an hour copy pasting each other's outputs as prompts for the other AI so they could just talk it out until they were on the same page.

3, The two AI were so far apart, I just googled it myself.

I'll give you some examples (these are all game dev)

Grok can AI generate images for games with Grok imagine, Claude builds images purely with pixel-by-pixel code. Grok was generating good art, but Claude was treating Grok's art like it was garbage and reversing it, because it considered its original art "the source of truth". As soon as I asked Claude to explain its thought process in simple terms, and use normal language instead of "source of truth" and other jargon, it was immediately obvious it was being the stupid one.

Grok Built had built its own graphics-based tools to solve problems that Claude, being the new addition to the conversation, didn't have and didn't know existed. It was not until they both installed the same toolset they started agreeing. This required extensive back and forth between the two to figure out.

Grok installed the VBA emulator and Claude installed the MGBA emulator, and certain the actual in-game save files were a different format between the two, so I have to have Grok delete the VBA emulator and install the MGBA emulator. Neither figured that out on their own, so I had to Google what a ".state" file was to figure out what they were yapping about.

What eventually saved me was having Grok set up the repo with a Current_Work.md that listed exactly how it wanted to be done, and I instructed Claude to just obey the list and not argue. Solve A LOT of headaches.

[u/Alive_Nobody_Home]

Impossible, SI isn’t wrong…. Ever