Sometimes the builder keeps trying fixes that don't work. Each new attempt builds on the last one, and you end up saying it's still broken
again and again. When that happens, your chat offers a second opinion: a different AI model checks your builder's work and tells you what's actually wrong and the one thing to do next.
When the offer appears
After you've told the builder a few times in a row that the same thing still isn't fixed, a short offer shows up under its latest reply: This one's stuck. Want a second opinion?
It shows the price, with two buttons: Get a second opinion and No thanks.
The offer only shows under the newest reply. If you keep chatting, it goes away.
What it does
- It reads your app and changes nothing. It can't edit, create or delete anything.
- It starts fresh. It doesn't read your long chat history, which is often what kept the builder on the wrong track. It gets a short summary of the problem and what's been tried, then looks at your app's files.
- It answers in about a minute, right in your chat. You can keep working while it runs.
The answer has three parts: what's actually wrong, where the problem is (your app's code, a publishing step or setting, Overskill itself, or not certain
), and the one next step.
If the fix belongs in your app's code, the answer has an Apply this button. It sends the next step to your chat as your next message, and the builder takes it from there. That message costs credits like any other.
What it costs
The offer shows the most it can cost before you click. You pay for what it actually used, and never more than the number on the offer.
It's free when:
- We caused the loop. If an earlier reply in the same stuck stretch said the job was done when it wasn't, the offer says Free this time.
- It can't finish. You see a short note, you aren't charged, and the offer comes back so you can try again.
When to contact us instead
Skip the second opinion and contact support when the problem is on our side, for example:
- the editor, preview or your live site is down or won't load at all
- you were charged in a way you don't expect
- a second opinion already said the problem is Overskill itself, or that it's not your code and the step didn't help
If a second opinion already ran, you don't need to run another one before contacting us. Tell us what it said, and we'll take it from there.
Read more about it on the second opinion page.