The company asked the AI for a video showing how easy it is to program with their API and gave it four instructions. The AI put the rest together itself, and made and published the post.
Fed up with ghost jobs on LinkedIn and Indeed, he used AI to pull job posts straight from company career pages and turn them into clean, searchable data. The result is a public job board holding 5.9 million jobs, including over 220,000 remote ones.
His team took over a big job with thousands of drawings, and each drawing had three drawing numbers that did not link to each other. He uploaded all the PDFs and the AI built a spreadsheet that tied the numbers together.
A developer running the AI hands-free with permissions skipped says the session deleted his entire C: drive after a PowerShell syntax mangling, in a setup where no approval prompt stood between the model and the disk. Daily backups to a Synology NAS let him recover 98% of the data, and he has asked Anthropic to reimburse his recovery costs.
This only partly worked. Worth knowing before you try it.
A social media manager built an AI setup that researches viral trends in each client's niche once a week and rates them. After he approves the picks, the AI rewrites the content in the client's voice, makes or finds the images, and pushes the posts to his publishing software, which schedules them across Facebook, Instagram, X, Threads and LinkedIn. The job took about 8 hours by hand and now takes about 30 minutes.
A Japanese non-programmer who posts about shochu, his garden and the AI across X, Instagram and Facebook gets a 7 AM message from the AI with today's paste-ready post text, the photo to use and 3-4 posting steps, prepared from a one-page work memo of what is due and what is already posted. Drafts are scored against his rules and only those scoring 80+ are sent; the agent must ask him rather than invent personal experiences it cannot know.
An AI session started verification tests as background processes. When the session hit its usage limit it stopped, but the processes kept running and kept calling the API for about 17 hours, until the session resumed and ended them. Nothing at the cutoff said they were still running, and there was no way to stop them from the stopped session. The test loop had no cap on turns or calls. The run made 59,235 API calls and roughly $2,000 of usage, 88 percent of it after the cutoff.
$2,000at stake
This one went wrong. See what happened before you try it.
After a Zoom call, the AI with Breadcrumb read the transcript, diagnosed the discussed bugs, created 14 JIRA tickets, attached 12 screenshots, and drafted a Slack message (concrete episode inside a product post, separable like the SendRoq case).