Fable and GPT-5.6 at max effort did a task that would have been a near 6-month project in a week, building a data capture pipeline, a synthetic data baseline, and building and testing 100 classification model variants with near-SOTA results.
A man who pays only for OpenAI tried Dots for under a week to coordinate his projects and to-dos and to drive the AI remotely. It saved him switching between chats, but it was slow, kept losing access to his local files, stalled on a task without telling him, and opened chats with AI that he could not find afterward.
This only partly worked. Worth knowing before you try it.
Tony Xu recalls using AI as his always-on agent in early 2026: he handed it a blog post draft task over Telegram, and the AI cloned his repository, studied his older articles for structure and voice, drafted the post, and he then checked the structure, facts and wording before publishing. He liked the capability but quit over the upkeep: a self-hosted gateway and services he had to run himself.
He maintains about ten repositories in his spare time, including work on Bootstrap, and the issue trackers grow faster than his evenings. Since October 3, 2026 a conductor AI session paces background agents that read and draft under written rules, and he gets one question at a time. On Bootstrap every open item is analyzed and a fix prepared when needed, and nothing is posted without a maintainer.
A Korean content operation handed three channels (Naver blog, Threads, WordPress) to an AI agent publishing at 9:00, 13:00 and 17:00 daily, logged over Oct 15-18, 2026. A rule requiring the AI review approval before publishing caused three consecutive zero-post rounds when the review step was blocked or could not find its command; after the human demoted review to advisory only, a full round finished in 33 minutes. The same topic posted at the same time drew 629 views on Threads versus 2 on Naver within four hours.
This only partly worked. Worth knowing before you try it.
He gives the agent his ideal customer and one pain point. Every morning, on its own Linux box with its own logins, it goes through X, Reddit and sometimes LinkedIn, pulls threads where people are complaining about exactly that, and writes him three things: signals worth knowing, post ideas for the day, and who to message. He reads, picks, and posts.
A Builder.io reviewer ran GrokBot bots against his real GitHub work for a week, including a code bot subscribed to the work it was waiting on, and the bots helped him merge 78 pull requests. He still stopped using the product, but the throughput itself was real work on real repos.