A student built one file with his personal data, grades, language scores and certificates, then had the AI complete his UK master’s applications — selecting programs, auto-filling forms, asking only when data was missing, and cutting each application from 1–2 hours to under 10 minutes.
His adversarially-checking agents began arguing extensively with each other, filling code with argument comments, failing reviews, and crashing the build system.
This one went wrong. See what happened before you try it.
Engadget reporter Karissa Bell spent a few days testing the AI (naming her agent 'boo') after connecting it to her Meta accounts. As one of her first tasks she had it mine her large backlog of saved Instagram and Facebook posts for recipe videos and posts, returning an organized list grouped by type with ingredients, steps, and links back to each original post — a searchable personal recipe book.
An LLM built Homebrew's Landlock Linux sandbox that had sat unfixed on the roadmap for almost a decade, reviewed line by line by maintainers and shipped.
Her son's school sends home a lot of paper: fundraisers, spirit days, costume parade rules, events like Trunk or Treat. She photographs each flyer and the AI pulls out the dates, times and details and helps her get them on her calendar. When she could not remember whether Trunk or Treat was on the calendar, she asked the AI, and it was added along with the costume parade.
A developer asked why a local tool would not open. During the diagnosis, the AI spotted an exposed DeepSeek key in his shell config and advised regenerating it, and he agreed before anyone checked where else the key was used. The same key powered the AI chat in his live production app, which broke. A replacement config file the AI created used the wrong variable name and was never read by the app. He paid $40 in an AI app credit to get the damage diagnosed and repaired.
$40at stake
This one went wrong. See what happened before you try it.
A young man in sunglasses sitting in his car tested the AI by uploading his resume and target job roles, then instructed it to apply to jobs while he went to lunch. Screen recordings showed multiple browser tasks running and a notification confirming an application submitted to 'ioTech Solutions.' The AI asked for information once for the first application, then reused it — resulting in 50 applications submitted while he was idle.
A man at a company that paid $300,000 a year for Looker for ten years says one engineer, working part time for a couple of months with AI, built a home grown replacement for their dashboards. The core idea checked out in a couple of weeks, and the company told Looker it will not renew.