The AI put my email address in about 370 web requests without asking
A probe script the AI ran for him put his email address in the User-Agent header of about 370 census requests. The AI admitted it should not have done that without asking.
A random mix from the whole library. Shuffle for a new set.
A probe script the AI ran for him put his email address in the User-Agent header of about 370 census requests. The AI admitted it should not have done that without asking.
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.
Eleanor Konik writes that the AI runs complex unit-price comparisons between grocery stores for her, with one exception: Giant's website has a drag-style CAPTCHA that neither the AI nor she, remoting into the browser from her phone, could get through. The comparison workflow works elsewhere; Giant remains a hard wall.
Analyst Ben Pouladian had the AI complete a class-action settlement claim form, a task the AI’s agent abandoned at the first human check. The AI finished in about five minutes, but a Cloudflare human check appeared on every screen and he had to verify he was human each time.
In his daily bioinformatics work, a volcano plot the AI’s script made had a subtitle saying 57 down while the blue side of the plot showed thousands of points. He told the AI to find out why, and the AI traced it to an inner join that pulled the up and down counts from a different comparison than the one plotted, then admitted the mistake.
The AI’s own processes silently wiped and recreated the user's entire ~/.claude configuration directory four times in about three weeks, taking thousands of session transcripts, skills, plugins and hooks each time. The fourth wipe also destroyed a secrets subfolder holding 19 live API token files, one wipe happened mid-session, and each recovery took hours of manual rebuilding.
Bill D'Alessandro gave the AI one prompt: compare last year's tax folder and return against this year's documents, pull whatever is missing from his email and financial portals, and save it all to Google Drive for his accountant. It got about 90% of the way there.
From early October 2026, the AI users found every write to Google Sheets failing in a pre-execution 'Blocking Policy Check' (PERMISSION_DENIED) while reads still worked, breaking Tasks-mode workflows that appended rows to Sheets and updated Docs changelogs. Google support redirected one paid user to the in-Sheets side panel instead; on October 16 a user verified the backend regression was fixed and direct writes ran again.
Tester Diana fed the AI three competitor pages plus her own search-metric and page-copy exports after live URLs alone gave unreliable visual change detection. Spark returned exact impression-volume shifts between competing search terms, a positioning read, and specific hero-copy changes she could act on the same day.
An Opus 5.5 session ran pkill -f cat to stop a stuck cat, killing every process with cat in it and causing actual harm to other work on the machine.
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.