He exported 10 hours of his AI usage (8,915 model calls, about 1.15 billion tokens) and had the bot study it. Chat with him was only about 11 percent; background subtasks the assistants started on their own were the rest, and 96 percent of input tokens were old context being read again. He set five standing rules, including a five minute wait limit and a cap on task size. A day later a second export showed total tokens down about 19 percent and tokens per call down about 28 percent, with average context per call down from about 128K to about 92K.
He is letting the AI run his websites, with him watching over it. Two days in, it has done about a week or two of work, using about 10 skills per site that each act like a manager with its own job.
This only partly worked. Worth knowing before you try it.
A solo developer who lost his business after a 2012 hospitalization built a self-hosted dead man's switch with AI so his projects and clients are handled if he is incapacitated. It has run for weeks, ships with 42 unit tests, and clients already cite it as a trust feature.
An engineer describes his board workflow: models review the design and write tooling, a script ranks net pairs by short risk, a deterministic router does the routing, and every attempt is simulated before anything is fabricated. An earlier language-model attempt at routing left 17 short circuits; the current workflow produced a fabrication-ready board.
He had the AI watch his online trainings and take the tests for him, and he collected 40 certificates in one day. He told it not to get perfect scores every time, and he says the system is broken if this works.
He gave the AI one big job: go through his entire Zotero library and build an Obsidian vault on disk that documents every article, sums each one up, pulls out the key ideas and links articles that share ideas. It ran for 34 hours straight on his 20 euro the AI plan without hitting a limit.
He spent 35 minutes on a call with Dots trying to create a task on his remote PC. Dots kept saying its spoken context was not being sent, told him to type it himself, then created a task that created another task, while the call was still telling him it had failed.
This one went wrong. See what happened before you try it.
An agent works his support queue and processes refunds on its own when the order is under $50 and inside 14 days. It cut about 40 minutes of daily sorting and checking, and he now looks only at the cases it flags.
He made a tool for students that started as a simple quiz solver extension and grew slowly to just over $100 in monthly recurring revenue, with very little marketing. A month ago he reverse engineered Anki using AI, so anyone can bring their Anki deck and study it in his tool. He says that is the thing that worked.