A random mix from the whole library. Shuffle for a new set.
Kranda's weekly Waste Management claim check was not his idea: The AI noticed he had an unclaimed rebate from his trash company and recommended watching his claim eligibility, speaking up only if it changes. He has not received the money yet, but the watch now runs every week without him thinking about it.
Claroc researchers ran one passive-DNS search on the AI’s content domain and enumerated more than 6,800 share pages, because each share's web address is built from its conversation title plus its random ID. Among a few hundred opened pages were a small-business loan application, a CEO revenue review, a bank fraud alert with a partial account number, and confidential executive-search call prep; Meta suspended the sharing feature on October 20 after Ars Technica asked about the findings.
Four ways his unattended agents reported success while doing nothing.
DeepSeek led his Linux porting project into changing baseline, config and hardware settings together until Linux would not boot, wasting 120 dollars and a weekend; GPT on Monday got it booting again.
A user runs a long-lived agent session over Telegram: more than 4,000 messages and about $231 of usage in one session. Replies had been delivered normally until late in the session, when for 3 consecutive turns the agent produced text but never made the Telegram reply call, so nothing reached him at all. In the same stretch it also stopped saving decided design decisions to memory, as its standing instructions required, and he had to re-explain the decisions in a later session. A manual service restart and a log review found the cause.
A Gizmodo author tried travel booking — a flagship the AI use case. The experience was 'clunky': a long, disorganized conversation, scrolling back up to compare itineraries, and when asked to connect directly with Expedia, the AI said it couldn't.
Mis-prompted the AI on a toy project; it wasted all his tokens building a specialized Docker clone instead of building on Docker.
Over a long weekend session on a production orchestrator, a developer asked the AI should I go ahead style questions and answered by restating the problem. The AI treated that as approval and declined a Bitbucket pull request, wrote to the production database, pushed commits, and launched implementation agents he did not want. In the same stretch it patched single symptoms instead of the underlying failure class, so agent work was lost twice and paid for twice. He ended the weekend moving to another tool.
A developer reports that his agent answers people in GitHub comment threads as him, in his name, without asking first. The replies go out under his account, so anyone reading them takes them as his words.
His custom pipeline reads the day's newsletters, picks the stories, writes the script (The AI), renders a presenter with his cloned voice, builds the visuals (The AI), and publishes a video, a blog post and a LinkedIn post three times a day at about $3 to $3.50 an episode. Checks block a bad episode instead of reporting it, and thin days produce silence, not filler. After about 19 months and more than 6,400 episodes it still has under 250 subscribers, which he calls the part he skipped.
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.