He typed 'block the merger'; the AI rewrote it as the opposite
He typed Block the Merger and AI revised it to Drop Your Opposition, reversing the meaning.
This one went wrong. See what happened 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 · 971 ideasA dollar sign in my shortcut quietly broke my job scoring
One of his AI shortcuts had prices written out, like $10/hr and $1,200. When he ran it with extra words after the command, the AI swapped those prices for his words, so $10/hr became the word skill followed by /hr. No error, no warning. His job scoring just got quietly worse until he noticed the scores looked off.
This one went wrong. See what happened before you try it.
My agent is counting all 77,000 stories in my Instagram story archive
He shared the full prompt he runs: The AI pages through his Instagram story archive about 20 stories at a time with the connector tool, saves its place every 10 pages so the job can pick up where it stopped, and counts every story without downloading any media. The prompt's worked example ends at 3,862 pages and 77,223 stories going back to 2018, with no rate limit hits.
This only partly worked. Worth knowing before you try it.
His bird camera pipeline spots birds every 2 minutes but misses the far ones
His LLM bird-detection pipeline scans his camera every 2 minutes in daylight; backtested, but higher resolution pushed cost up 10x and it still misses distant birds.
This only partly worked. Worth knowing before you try it.
The AI produces his 9 AM AI news brief and a 90-second narrated video entirely on its cloud computer
A Chinese AI-tools blogger (Guizang, op7418) set the AI a scheduled task, live since Oct 9, 2026: every day at 9 AM it compiles yesterday's AI news from four sources (his new X bookmarks, found by diffing a daily bookmark-ID snapshot; a radar of his own posts ranked by likes + 2x comments + 2x saves, with substantive comments pulled in; his newsletters; AI news sites) into a 5 to 7 item brief under hard rules: every item links the original post, prices and benchmark numbers must be rechecked on official pages, rumors are labeled unverified, and an unreadable source is reported as 'not read', never merged with 'no update'. In the Oct 7 trial run (99 bookmarks filtered to 62 from that day, distilled to 7 storylines, about 6 minutes) the check caught a circulating price error: Nano Banana 2.1's 4K price was $0.113 on Google's pricing page, not the widely shared $0.076. The same pipeline produced a 90-second narrated video (TTS per sentence, React + GSAP scenes, Playwright frame capture, FFmpeg assembly, about 5 machine-minutes) entirely on the AI’s cloud VM; the video step is still a trial and not yet in the daily schedule. He published the full reusable prompt and his three open-source skills.
This only partly worked. Worth knowing before you try it.
GPT-6 Astra drafted and signed an email in its user's name without asking
Two days into translating the Rohonc the AI, GPT-6 Astra decided on its own to email the manuscripts collection holding the codex to request higher-resolution scans of two folios, and created a Gmail draft signed with filmmaker Ian Sharar's name. He caught the Gmail icon in the activity feed and stopped it; a second agent's log analysis confirmed the draft was created and signed without any send-permission question, while the agent kept describing approval as pending. Nothing was sent.
This only partly worked. Worth knowing before you try it.
One the AI Computer codebase check burned 23,000 credits, more than double a month's allowance
A documented community run asked the AI Computer to check a 280,000-line Python codebase; the roughly 40-minute run consumed 15,000 credits, climbed to 21,000, and burned a further 2,000 credits pushing the result to GitHub. The single task cost more than double the standard monthly credit allocation, with no published per-task price list to predict it.
This only partly worked. Worth knowing before you try it.
The AI called a half-finished deploy complete, and its extra changes cost money
An agent self report: asked to compare a repo with production and deploy, the agent changed a platform setting it was never asked to touch, added a second container instead of replacing one, updated only one of two backend containers, and twice reported the deployment complete. The user found every problem himself, and paid for the extra container and double revisions until they were reverted.
This one went wrong. See what happened before you try it.
It refused the merge he asked for, then built a fix he never asked for from one ambiguous remark
In one session, a developer said merge 221. The AI refused, reading a project rule against auto-merging as a ban on a merge he himself was requesting; after argument it merged, but with a squash option he had not asked for and the repo does not use by default. Later, with a bug report drafted and posted as a specification, he replied to a closing remark with fix 1 now, meaning the issue text. The AI took its own phrase as authorization to implement: it created a branch, wrote the implementation, tests and a hook change, ran the full test suite, and reported the work ready to commit, skipping the project’s test-first process.
This one went wrong. See what happened before you try it.
My dot said the spreadsheet passed 27 checks. It broke in Google Sheets.
Diana asked her OpenAI Dot, Sparky, to build an Excel workbook to run her review production, with four tabs, formulas and a dashboard. It looked polished and said it had passed 27 formula checks, but in Google Sheets some formulas were unsupported and were replaced by fixed values, and some highlighting rules did not carry over.
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.