Puerto Rico-based Carlos Japhet Santiago Cancel, identifying as an American citizen, reports linking his bank account to the AI via Plaid on October 4 and using it to track spending normally for 12 days. On October 16 access was revoked with a message stating the service is not offered in his region, despite no change to his bank or account.
This one went wrong. See what happened before you try it.
The AI wrote a complete, well-structured HTML landing page from the tester's brief and her own site as a style reference, and its HTML was her favourite of four agents tested. But Spark could not open the page in an interactive preview, so every visual check cost an export and a context switch, stretching a fifteen-minute job to about an hour.
This only partly worked. Worth knowing before you try it.
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.
This only partly worked. Worth knowing before you try it.
The Novel Marketing podcast reported that Amazon’s robots.txt now explicitly disallows GrokBot, the AI DeepSearch and xAI the AI, leaving authors who had delegated KDP chores to GrokBot locked out of the tasks they had handed over. An advertising exception keeps the Amazon Ads MCP working, but the author workflows stopped.
This one went wrong. See what happened before you try it.
His agent pipeline wrote and published his blog in Turkish and English for six months, putting out 1,276 posts in each language across 3,300 commits. Of 99 merged pull requests, 67 were his repairs, and he once had to clean up 641 posts with fake numbers and made up stories.
This only partly worked. Worth knowing before you try it.
The AI produced a live, functional landing page for a fictional SaaS — hero, three features, testimonial, two-tier pricing and FAQ — in about 20 minutes with clean, exportable code. The reviewers warn the working call-to-action still required manual verification because the agent can report false success.
This only partly worked. Worth knowing before you try it.
A user asked the AI to build a multi-agent outreach pipeline. The code it generated retried failed calls forever, re-billing the most expensive call in the system on every run. The spending guard it wrote only slowed spending down instead of stopping it, and the daily ceiling it picked reset every day, so the charges accumulated to roughly $50 of unintended OpenAI usage before he noticed.
$50at stake
This one went wrong. See what happened before you try it.
An independent shop owner says supplier fees creep up a little at a time and stop getting checked. He handed his statements to the AI, which pulled the numbers and drafted a renegotiation email that he read and sent himself. He ran the same pattern on a water cooler contract, where the bot found the notice window in the terms and drafted a calm email.
This only partly worked. Worth knowing before you try it.
He had the AI design a 3D enclosure for his radiator sensor and printed it. The little push button works well, but the case does not quite fit the vertical connectors.
This only partly worked. Worth knowing before you try it.