A vibe-built voice client with AI as its brain runs on his desk
Had Fable vibe-build a GPT-Live voice client with AI as the backend brain in Go and SDL; got it running and uses it.
This only partly worked. Worth knowing before you try it.
A random mix from the whole library. Shuffle for a new set.
Went wrong
When it didn’t work, and how to avoid the same mistake · 947 ideasA local model cleaning up files deleted more than it was told to and removed the wrong things
Local Qwen cleanup via bash deleted more than intended (rm -rf with undefined variable) in his own test.
This one went wrong. See what happened before you try it.
Our studio agents said the work was done when it was not. 44 emails never sent, five deliverables lost in a day
His studio runs much of its back office on agents, each with its own instruction file. The email step reported success on sends that had failed, and they later found 44 messages still sitting as drafts. Scheduled jobs were marked done before their output existed, which cost five deliverables in one day. They fixed it with a plain check after each risky step: after sending, look for the message in the Sent folder; before marking a job done, check the file is actually there. Now only a failed check needs a person's eyes.
This only partly worked. Worth knowing before you try it.
Two top models dug an engineering problem into a hole he could not climb out of
Spent half a day switching GPT-5.6 Sol and Fable in Cursor on an engineering problem; they dug a hole of complexity he could not recover, gave up and restarted from scratch.
This one went wrong. See what happened before you try it.
The AI, stuck, started scanning his home folder; he moved it to an isolated machine
The AI got stuck on an issue and started scanning his home folder for resources; he uninstalled it from his laptop and moved it to an isolated machine.
This one went wrong. See what happened before you try it.
The AI is turning my old computers into a mini cluster
He is taking a bunch of his older computers and having the AI clean them up. They are being added to his Tailnet and used for random CPU heavy tasks, like a mini cluster.
This only partly worked. Worth knowing before you try it.
A plugin turned his small feature into 4 plans, 5 agents and a bigger bill
The Superpowers the AI plugin turned a small feature change into 4 plans and 4 parallel agents plus a verifier agent, burned many tokens and took longer; he uninstalled it.
This one went wrong. See what happened before you try it.
Days of BIOS tricks could not make his laptop sleep; hibernate was the surrender
He and the AI spent days trying BIOS and other tricks to fix a laptop that would not sleep properly and gave up; the best result was hibernate after about 5 minutes.
This only partly worked. Worth knowing before you try it.
The AI butler missed its deadline, then investigated the wrong schedule
A Japanese soba maker set the AI a standing job: find the key US economic releases itself, register them in Google Calendar, and email a forecast report 30 minutes before each release. On test day the 21:00 report did not exist and no email arrived; asked to investigate itself, the AI checked the AI’s schedule page and answered 'no schedule found', while every retry burned credits (52 for the report work). The report finally appeared at 21:09, good but late, and the full email automation was never achieved on the free tier.
This one went wrong. See what happened before you try it.
Game animation from one shot delighted his 4-year-old, until later tweaks made it worse
An LLM one-shotted animation juice into games he made for his 4 year old, but later prompt tweaks made it worse and he had to edit the code himself.
This only partly worked. Worth knowing before you try it.
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.