A Japanese Threads creator split his account's operation into six AI agents with one deliverable each (researcher, writer, poster, fetcher, analyst, supervisor) and reports 1,181+ posts and over 10 million cumulative impressions. The writer agent may only cite numbers stored in a single 'truth file' so it cannot inflate results, the poster must confirm the published URL rather than the button click, and the fetcher records 'not retrieved' instead of zero when a fetch fails.
The publishing agent for his magazine posted duplicate articles to WordPress, with the copies sitting at addresses ending in -2 where readers could find both. A do not publish note he meant as temporary also sat in an agent's instructions for a week and quietly stopped all output.
This one went wrong. See what happened before you try it.
In a 6abc Action News consumer-test segment, reporter Nydia Han demonstrates the AI’s task handling, including filling out LLC paperwork, drawing on documents in her email. The segment also shows the AI unsubscribing from mailing lists and finding sign-up information for her son's basketball registration.
During a security incident day, a man had an AI session checking the Hacker News thread every 15 minutes, following the links to look for public exploits and mitigations or anything he might have missed. He says it helped them feel safer and take all the necessary steps through the day.
He pointed the AI at his JavaScript project and asked for a full TypeScript migration without changing behavior. 236 commits and a full day later the project compiled clean, the linter passed, and 55 of 56 tests passed, with the one failure traced to a commit where a value was accidentally hardcoded.
He stopped posting jobs. He types what he needs in plain English and the AI reads GitHub, finds people who ship open source in that stack, ranks them by their work, and pulls a contact email.
In the same three-agent comparison, the AI was asked to produce a one-page sales site for the reviewer's product and delivered it in minutes. Presented as a chaptered test ('Test 2: a one-page sales site') in the Oct 17 video.
He released version 0.6.0 of his software, and his agent fleet built most of it. A pre-launch check caught a routing bug where one agent was being sent another agent's model id. Now every routing path runs as a canary before a release.
Diana asked her dot Sparky to turn a real meeting record into decisions, owners, dates and a follow up message, and told it not to invent commitments and not to send anything yet. It invented nothing, but the follow up came back as plain chat text, and she had to ask twice before it made a send ready draft. When she told it to send, it sent at once.
This only partly worked. Worth knowing before you try it.