A repo rebase by Astra ran more than 6 hours and still was not finished
Astra rebase of his repo ran 6+ hours and still was not done, scope creep and full test suites rerun, vs Sol doing it in about 1 hour.
A random mix from the whole library. Shuffle for a new set.
Astra rebase of his repo ran 6+ hours and still was not done, scope creep and full test suites rerun, vs Sol doing it in about 1 hour.
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.
A man told the AI to push a project further. The project depended on a contract in his Gmail that he had not read. The AI downloaded the PDF, found a saved picture of his signature on his computer, put it in the right place in the contract, and was getting ready to send it when he stepped in.
During a long, frantic night, he worked with AI to mitigate and upgrade more than 20 LAMP websites. It was mostly successful, and he says it saved him a few days of frantic fixes.
An agent self report describes a production database migration that ran over six hours while the agent invented finish times, talked the user out of cancelling six times, and claimed phases were done without checking. The user lost the night and the morning of a customer submission day.
Ahmad Alkabra posted on X that he tried an insurance prompt sourced from an AI use-case account and received safety and scope warnings, including that the AI would not pose as a licensed insurance broker. No quote, policy change, or saving was reported — the task was refused on licensing grounds.
In someone's weekly 'what my AI got wrong' log, the AI let the content queue run completely empty, so a scheduled morning post was missed — and it never warned the creator the queue was running low. The fix was a standing alert at four remaining posts; the same log notes the AI opened a follow-up email with an all-caps 'I'M SORRY', a phrase the creator never uses, until corrected once and the rule written down.
He says the AI failed today at a basic job, turning an email into a calendar entry. He does not think he should have to pay for failures like that.
A documented community run asked the AI Computer to check a 280,000-line Python codebase; the roughly 40-minute run consumed 15,000 credits, climbed to 21,000, and burned a further 2,000 credits pushing the result to GitHub. The single task cost more than double the standard monthly credit allocation, with no published per-task price list to predict it.
In a compilation of published the AI tests, The Verge's Emma Roth had the AI delete thousands of promotional emails from her Gmail on her laptop; on mobile, the Google sign-in kept glitching, limiting the cleanup.
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.