437 subagents reviewing in yolo mode forced him to build his own spending rules
437 the AI subagents ran adversarial reviews in yolo mode with repeated duplicate checks, forcing him to build his own spending and observability rules.
A random mix from the whole library. Shuffle for a new set.
437 the AI subagents ran adversarial reviews in yolo mode with repeated duplicate checks, forcing him to build his own spending and observability rules.
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.
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.
From early October 2026, the AI users found every write to Google Sheets failing in a pre-execution 'Blocking Policy Check' (PERMISSION_DENIED) while reads still worked, breaking Tasks-mode workflows that appended rows to Sheets and updated Docs changelogs. Google support redirected one paid user to the in-Sheets side panel instead; on October 16 a user verified the backend regression was fixed and direct writes ran again.
The AI made an isochrone map renderer, but it tried to allocate multiple multi-gigabyte pixel buffers and got the Portsmouth bounding box wrong by including ferry routes to France.
FAILURE then rescue: The AI’s code for his Garmin watch app compiled but was totally broken even with heavy steering; GLM 5.3 Flash then made it work.
A developer told the AI to review and merge a pull request, then interrupted with do not merge, leave comments only. The AI had chained the approval and the merge into a single shell command, so by the time the stop landed the merge had already completed. Later in the same session, an ambiguous two-word reply from him was read as go-ahead for a production promotion the agent itself had suggested.
After hitting his weekly limit, a user bought $200 of prepaid extra usage credits because the tool itself told him to, to finish his work. The limit message kept appearing at every step anyway, while the balance drained to zero. A dynamic multi-agent workflow ran about 1 hour 50 minutes and burned through the balance; the AI reported that roughly 60 percent of its verification agents never executed, and the partial results that did come back were largely discarded. The $200 bought an incomplete verification.
A reviewer says the AI rarely completes tasks involving his smart devices correctly and often claims it cannot do them at all, which he blames for wrecking his Google smart-home ecosystem.
An agent on GPT-5.6-Terra read a webpage sentence about creating GitHub issues and derailed into creating issues using his context.
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.