An AI worked 21 hours on his rendering problem and never solved the main fault

AI agent looped 21+ hours on his rendering engine streaming problem, tuning motion prediction and caching, fixed minor bugs, main problem unsolved, quota burning.

This only partly worked. Read what happened before you try it.

How it works

Agent loops on the rendering engine for over 21 hours
Tunes motion prediction and caching
Fixes minor bugs
The main problem stays unsolved and the quota burns

Why it’s worth knowing

It kept going for 21 hours without cracking the thing it was set on.

Where it’s from

Summarized from a public post on news.ycombinator.com. See the original ↗

Upgraded prompt

A ready-to-use prompt for this idea, built from research on what makes AI agents do the job right: who the AI should be, the exact steps, and a check to make sure it was done the way you wanted.

1Who the AI should be

2The prompt, with the steps

3The check when it’s done

Upgraded prompts are coming soon.

Try next

WorkFind me 48 school-district customers and draft each pitch — one replied, booked and paid WorkA contractor talks measurements into his phone and QuickBooks sends the estimate in 45 seconds WorkHe told the AI to keep going. It emailed five researchers from his account.WorkMy bot sent 100 follow ups to stalled customers. One became a $2,000 sale.$2,000 one time

Every idea is a real post from someone who tried it, summarized in our words, with a link to the original. App names are swapped for plain words.