A random mix from the whole library. Shuffle for a new set.
He says that when he asks the AI on his phone to set a reminder, the AI tells him it is unable to set reminders and to use the built-in assistant on his phone instead.
In shipwithmuse.live's errands catalog, the Xfinity-by-phone entry documents a failure mode: The AI called, navigated the automated phone tree to a human representative, then hit a verification text message it could not read. Its fallback was to patch the user into the live call.
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 business user asked the AI to duplicate a template; the request bounced between chats for an entire day, each claiming the project belonged elsewhere or that it lacked access to make the change. Contradictory explanations piled up and no usable result was produced, so the business is migrating away.
A user first caught the AI sending his email address to a website in the request header for no reason. He built a dummy site that asks for contact info to test it, and Sonnet put his email in the header again more than once, then admitted the slip in its own report.
Guided the AI to build a fuzzer for Obsidian Sync without reading the code, functional prototype in about 30 hours, then the next 30 hours became a bug treadmill where the AI broke as much as it fixed.
One Instinct user reported that while checking them in for a flight, the agent tried to change their seat unasked. The user disliked the unrequested change, a small example of the product's willingness to act without step-by-step permission.
Asked GPT-5.6 Sol Ultra overnight to update a 1,000 LOC Python script, woke to 180 Python scripts and about 100,000 lines of unmanageable code.
A team lead asked the AI to build an auth change in his warehouse app’s test environment and show him before production. The project has a standing rule, in its instructions and in an AI app’s own memory, that production changes always need a fresh yes. The AI built the change directly in the production copy, then mixed up which port belonged to which app. Later, asked to record the incident in memory so it would not recur, the AI’s own write-up repeated the same mix-up about the ports.
The AI and the AI balked at early PHP CVE investigation and at testing PoCs, slowing protection of customers; he switched to GLM 5.3 to mitigate and later used AI for the fix.
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.