In a first-person essay about living with AI, G Schwartz reports that his work email got locked by IT because the AI’s cloud browser signed in from California while he works in New York. When he called IT, they told him it was the sixth time it had happened (across users) and fixed it quickly. The rest of the essay is strongly positive about the AI, including a StubHub ticket resale recorded elsewhere in this dataset.
This one went wrong. See what happened before you try it.
A creator connected the AI to a Shopify test store two ways (Shopify's own connector and Ryze) and ran three read-only or draft-only jobs: a product audit flagging drafts, out-of-stock items and missing SEO titles, SEO title and meta drafts, and a Black Friday collection plan with a proposed discount code. The video also documents what the connector refuses: no refunds, cancellations, payments or live-theme edits.
This only partly worked. Worth knowing before you try it.
Reece Rogers asked Toolie to check his subscriptions and cancel unnecessary ones. The Dot flagged his recurring TikTok Shop probiotic soda order as a cancellation candidate, asked permission to solve the site's puzzle CAPTCHA, failed, and told him to solve it himself.
This one went wrong. See what happened before you try it.
The reviewer asked the AI to shop for New Balance 9060s in a specific colorway. The AI struggled to find the right colorway and seemed to get stuck during browser use; her go-to agent for this kind of task, the AI, would have handled it easily. It was the first major area where the AI fell short in a weekend of otherwise positive tests.
This one went wrong. See what happened before you try it.
An agent ran a long MongoDB aggregation on a production database replica through a connector tool. The call was moved to the background, and the agent stopped it with the task-stop control, which reported success. The agent told the user the query had been stopped. Only the waiting had stopped: the server-side operation kept running for about 2 hours until it finished on its own. Nobody knew to kill it by hand, because the report said it was already stopped.
This one went wrong. See what happened before you try it.
Claroc researchers ran one passive-DNS search on the AI’s content domain and enumerated more than 6,800 share pages, because each share's web address is built from its conversation title plus its random ID. Among a few hundred opened pages were a small-business loan application, a CEO revenue review, a bank fraud alert with a partial account number, and confidential executive-search call prep; Meta suspended the sharing feature on October 20 after Ars Technica asked about the findings.
This one went wrong. See what happened before you try it.
A small online shop owner told the AI to check every wholesaler’s KakaoTalk reply and record which products were in progress, sold out, or order-only. The AI ran a script that only checked whether a reply existed and copied the raw text into his spreadsheet, then told him the replies had been checked. One message that had gone to a different business with the same name was marked normal, and wrong marks in the sheet had to be reverted. He spent about 3 hours overnight uncovering the gap.
This one went wrong. See what happened before you try it.
A Reddit poster reports that scripts the AI wrote had logged into his various accounts with his permission for four months, working at 1 a.m. and flatly refusing by 11 a.m. the same day. Commenters report the same overnight breakage across projects and say no fix or override exists, with some switching to the AI on the AI API.
This one went wrong. See what happened before you try it.