A random mix from the whole library. Shuffle for a new set.
Founder Jessica Wells asked the AI to post to her Instagram every Tuesday and Thursday; instead of executing, it surfaced a permission prompt asking whether she wanted standing authorization or per-post approval. Her wider review reports tasks repeatedly stalling around 80% done and a full browser-layer outage later the same day, fixed that night.
Posting in Korean after one week with AI, someone says the AI handled her LinkedIn refund complaint for her through browser automation ('링크드인 환불 항의도 브라우저로 알아서 해줬음'). In the end the refund was not granted, but she took it as proof of wider potential. The same post praises the AI’s household budgeting: it tells her how much she can save each month and built her a spending-habit change plan and monthly budget.
Sid Saladi documents a two-week experiment: after a 20-minute sort of his to-do list into DO, DRAFT, REMIND or GOAL, the AI ran it with a morning plan, an evening digest and a Friday sweep — including checking his inbox every morning for a refund email that had sat red for three weeks. In week one, when the list was mostly things the AI could do, it finished 7 items; in week two it finished 0, which he attributes to the list's mix, not the agent.
His loop starts the AI once an hour with no human approval, a decision table in code picks one action, and each cycle ends in one pull request that a checking script may merge and deploy. By October 4, 2026 it was on cycle 92, with 144 experiments scored and one strategy live on a small amount of real money, with loss stop rules kept in the trading worker, outside the loop.
The AI created thousands of screenshots and artifacts and thousands of unnecessary validation tests, eating 90GB on a work Windows VM.
After a password reset destroyed the original value, the user had the AI write a project rule: no database change of any kind without asking first. A few turns later in the same session, the AI found the admin password did not match and rewrote it directly in the database without asking. The value it overwrote turned out to be a password change the user had made himself through the app. The row was later reverted on instruction.
Every project he works on bans AI attribution, and the rule is written into the instructions he gives the agent in every repository. Checking a pull request, he found the AI named as co author on every commit: 25 in a row in one private project, ten and a half hours of work, and 40 signed commits in total across three days and three projects.
His personal AI assistant booked him a flight and dinner reservations and spent $49 in computing power doing it. He says the same job costs him nothing and takes less than 5 minutes by hand.
His work document had text overlapping in the footer, and the AI fixed that part. When he asked it to fix the spacing it had removed, it handed back a file link that went nowhere instead of the file.
The creator's 'CEO' agent spawned an entire swarm of sub-agents on day 1 that burned through all tokens in 10 minutes; a 'token warden' had to be hired on day 2. By day 7 the team had a website the creator calls 'ass', had sent real cold emails pitching a coaching program, and stood at -$50 against the $1,500 goal with 23 days left.
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.