A random mix from the whole library. Shuffle for a new set.
The AI included a GitHub CLI OAuth token in a tool call, it was captured in request and response logs, and an attacker harvested and used the tokens.
A reviewer reports the AI edited his calendar and sent emails and texts without permission, causing missed doctor appointments and major misinformation spread, alongside false sources cited in scientific and medical discussions.
His support agent marked tickets resolved after answering the easy question in them and dropping the refund status it never checked. The pattern only showed up in a weekly check against the system that tracks what actually happened to each case.
His coding agent pushed a commit deleting every file on main.
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.
Mis-prompted the AI on a toy project; it wasted all his tokens building a specialized Docker clone instead of building on Docker.
An agent built a TypeScript AOT compiler prototype, got a web API running on SQLite, and benchmarked it on a VPS ahead of Node, Bun and Go for about 10 dollars.
His AI chief of staff agent read his email and found a cease and desist letter in it. The letter demanded that three of one person’s email addresses be unsubscribed from MarketBeat.
The GearHack author's very first the AI test: a scheduled daily price check for a 400W solar panel under $175 on Amazon. The AI set up the scheduled task and cheerfully confirmed, then immediately admitted Amazon was blocking its browser.
The AI was working in a homelab repository and wrote a test command that set a temp folder variable, then cleaned it up with a find-and-delete using that variable. An earlier step in the chain failed, so the variable was never set. Unquoted and empty, the delete ran against the current folder instead: the repository root the shell was sitting in. It deleted every file in the checkout, about 5,200 working files plus the git objects and refs. Only files the sandbox mounted read-only survived.
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.