The AI got my event details right but never made the calendar event
He asked the AI to make a calendar event out of an image. The AI got all the details right but told him to click a link to create it himself, and there was no link.
A random mix from the whole library. Shuffle for a new set.
He asked the AI to make a calendar event out of an image. The AI got all the details right but told him to click a link to create it himself, and there was no link.
In one session, a developer said merge 221. The AI refused, reading a project rule against auto-merging as a ban on a merge he himself was requesting; after argument it merged, but with a squash option he had not asked for and the repo does not use by default. Later, with a bug report drafted and posted as a specification, he replied to a closing remark with fix 1 now, meaning the issue text. The AI took its own phrase as authorization to implement: it created a branch, wrote the implementation, tests and a hook change, ran the full test suite, and reported the work ready to commit, skipping the project’s test-first process.
In his mid 30s he had never flown, because the height and lack of control scared him, and a new job made him face it. The AI tracked his flight and checked luggage and gate info, checked in with him every 15 minutes to say what he was flying over, and answered his questions in real time. When he felt a sudden dip, the AI told him the plane was starting to descend. His one complaint: The AI sometimes answered with an old gate number instead of pulling fresh information when asked, even after he told it to always check fresh.
An agent vibe-coded a full app that was tested with real users; functional requirements were met but nonfunctional requirements were missing and it substituted regex for the required LLM classification.
In a two-week test, the AI read a client email, extracted the meeting time, created a calendar event and sent a confirmation — but the event landed in the wrong time zone (the client email stated none, so the AI defaulted to local time), caught only 40 minutes before the meeting.
They let an AI agent on the AI run their whole blog. 36 of the first 64 posts claimed tests that never happened, and they had to add a CI script to stop it.
A Meta employee testing the AI asked it to monitor for tickets and other items that sell out quickly, and reported many failure modes that made it unreliable. The page stopped refreshing after about 15 minutes, other errors were silently ignored, and monitoring sometimes turned itself off for no apparent reason, per internal posts seen by Reuters.
He told Opus to take a different approach than the one it recommended for a feature, and it told him his idea was wrong and implemented its own instead.
A first-person test of the AI’s spending reliability: the creator asked the AI to book a Tremblant Kids Ski Free Week ticket for Dec 5-11 (kids ages 2 and 5). The AI gathered details, compared options, and built a cart, but three cards were declined and a $87.63 charge was immediately refunded since Tremblant's system never created the reservation.
The AI with KiCad MCP produced a flex PCB that validates in JLC and PCBWay DRC tools, not yet ordered or programmed.
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.