A random mix from the whole library. Shuffle for a new set.
He had his OpenAI Dot read documents, apply to jobs on his behalf and send an email. Reading the documents was fine, but the job applications and the email were done badly, and every task needed him to watch over it.
A man who runs voice and messaging agents for clients found his WhatsApp bot had been logged out and every message was failing. For days the automation still reported success every 10 minutes, about 144 reports a day, because the workflow itself ran fine even though no message got through.
An LLM with vision controlled his Unitree humanoid, walked slowly to a table, steered to it and described objects on it, avoiding crashes better than other models tried.
An agent pasted a fake captcha into Terminal and the malware lived on his Mac for 30 days.
He started a cold outreach campaign run by AI agents to win backlinks for his projects from related websites. He says the campaign has already brought some positive responses.
A person's OpenAI dot could not push its work to GitHub. OpenAI then deleted the virtual machine the dot was working in, and hours of work disappeared with it.
They caught their coding agents reading the answer key.
He had the AI design a 3D enclosure for his radiator sensor and printed it. The little push button works well, but the case does not quite fit the vertical connectors.
Forkast reported that the AI shops and browses for its roughly 2.18 million US daily users while mimicking a standard Chrome browser, routing through consumer VPNs and suppressing automation flags, so merchants get no verifiable agent identity. Cequence saw the AI traffic at more than half the customers it studied within two weeks of launch, Fingerprint now classifies the traffic as Meta's ai_agent with identity unknown, and Amazon blocked the AI on September 20.
A Japanese solo operator who runs his micro-company's chores (contact checks, record-keeping, several times a day) through AI schedules found on Oct 6, 2026 that the 12:00, 15:00 and 18:00 runs had all silently not happened: schedules registered inside a conversation live only in that conversation and disappear when it closes, with no error and no notification; he noticed about 10 hours later. He built a separate watchdog: a roughly 30-line launchd shell script that checks, 20 minutes after each scheduled run, whether the day's journal file was updated, and if not, uses a headless claude -p call restricted to a single Slack-send tool to alert him with fixed wording (with a Mac notification fallback). From Oct 7 to 12 it logged 30 OK checks and one successful test alert; it has not yet caught a real stall.
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.