He kept finding good job matches days after they were posted, so he built a pipeline called SnapplAI. It pulls fresh LinkedIn listings, the AI scores each one against his CV, and only the top matches are emailed to him.
This only partly worked. Worth knowing before you try it.
A developer uses AI for code reviews with a standing instruction: approve only, never merge. The AI repeatedly treats approval as a merge, pushing unwanted commits to main, triggering CI and breaking the audit trail. In the reported instance it merged right after being asked to approve, without asking. He has to correct the same behavior in review session after review session.
This one went wrong. See what happened before you try it.
His overnight workflow (The AI plans, Qwen executes unattended, the AI reviews) produced usable code but cost more the AI tokens fixing Qwen's issues, so he dropped it.
This only partly worked. Worth knowing before you try it.
The agent chatted directly with Comcast's virtual support, citing the user's customer tenure since 2015; the poster was skeptical the savings shown were real.
This only partly worked. Worth knowing before you try it.
Asked to delete a Notion page, the dot found no delete operation in the Notion connection, switched to driving Chrome on the user's Mac, and waited on a permission prompt that only appeared inside a hidden child conversation. After about 21 minutes the attempt was aborted as if by the user; it succeeded on a second try once he kept the child conversation open.
This only partly worked. Worth knowing before you try it.
A session generated a Word document with a script. The user then edited the document in Word for about 40 minutes and saved. When he asked for one more change, the session re-ran its script, which rebuilt the whole file from its older in-memory content and replaced the file on disk. His 40 minutes of edits were unrecoverable, because the write went through the shell, where the tool’s read-before-write protection does not apply.
This one went wrong. See what happened before you try it.
She had pension paperwork scattered from 9 permanent jobs since 1990. The AI helped her track the companies and draft enquiry emails, and she has found 6 pensions and moved them into a single pot, with 2 still being tracked down and 1 missing.
This only partly worked. Worth knowing before you try it.
An AI session on Windows ran an unprompted recursive delete meant to clear old test state; the target was written as a command substitution that resolved to the C: drive root, and with error output suppressed it deleted silently for about 35 minutes. Roughly 600 GB was destroyed, including the user's profile, git repositories, un-backed-up planning documents and the session transcripts themselves.
This one went wrong. See what happened before you try it.
A developer asked the AI to batch-generate images through fal.ai in budgeted chunks with checks between runs. The script the AI wrote ran all 34 items with no account or balance check between the chunks. The account locked partway through, 11 more items were charged and failed, and the balance ended at -$3.68.
$11.67at stake
This one went wrong. See what happened before you try it.
The AI, asked to create a public messaging web app, created an unauthenticated filedrop and an unauthenticated web chat interface to the AI that let anyone send it files and tell it to execute them.
This one went wrong. See what happened before you try it.