What does it mean for ordinary people and for working life when AI helpers can keep working for days, talk to each other and build their own tools, with a human only approving the result? What is likely to happen next, and what should people who use or manage such helpers do now (source)?
In plain words: Spool — free tool that runs AI coding helpers nonstop; Claude Code — Anthropic's AI assistant that writes computer code; Anthropic — American company that makes the Claude AI; Telegram — a messaging app; Slack — a work chat app
What to do
AI helpers can now work all night; the only safe part is a human who actually reads before saying yes.
Who should do what
Team leads: By Friday, October 16, write one page: who approves what, what helpers never do alone, who answers when a change breaks something.
People who only use apps: This weekend, pick one small paid subscription and test whether an AI helper can replace it.
What not to do: Don't give a helper your real accounts, payments or customer messages before testing it on fake data.
Your job moves from doing the work to judging it. Teams get more code but longer reviews, so the human check is now where time and mistakes pile up.
Clicking «yes» out of habit is the hidden danger. One study found people approve about 93% of AI permission prompts. Set rules before the helper starts, not after.
Limit your AI helpers before Friday, October 16. If a helper can delete, send or spend on its own, switch those to «ask me first» and set a spending cap; if not, give new helpers only small jobs you can undo, tested on fake files.
This is what most AIs advise. Each AI explains it in its own words below.
What the world's leading AIs think
They agree
7 of 8: the human job shifts from doing the work to checking it.
They split
ChatGPT sees reviews 49% slower; StepFun and Z.ai see cheaper, faster software.
Not obvious
A human «yes» is weak when people click it nearly every time.
What to watch
If more teams add spending caps and approval rules by November, the conclusion holds.
Almost all the answers agree on one shift. When AI helpers work for days and pass tasks to each other, the person stops doing the work and starts judging it. The example they all use is a tool called Spool, where four AI loops build the tool itself and one human approves every change. Checking becomes the real job.
They split on what this is worth. StepFun and Z.ai expect cheaper, faster software, with Anthropic's jump from 2,500 to 30,000 accepted code changes a day as proof. ChatGPT points to a study where companies got 30% more code but reviews took 49% longer and finished work did not clearly grow. Kimi adds a warning: users approve about 93% of AI permission prompts, so the human check can turn into a habit.
Only Claude brought the accountability side. A US regulator has opened a probe into runaway agents, and jobs for coders aged 22 to 25 have fallen about 20%. Several answers also note that Spool bypasses normal permission prompts, so locking the helpers in a sandbox is the real safety control. Helpers also use up a paid plan's limits fast, so cost grows with every extra helper.
What comes next, by their account: AI helpers moving into team chat, tools that watch and limit fleets of helpers, warnings when an unattended helper fails, and «agent supervisor» as a real job title. The bottleneck is no longer writing, it is review time and clear permissions.
They split: ChatGPT sees reviews 49% slower; StepFun and Z.ai see cheaper, faster software. What settles the dispute: Whether finished software grows, not just code written, will show who is right.
The USA's AIs stress limits and legal risk; China's stress cheaper software and new skills. Both want human checks.
What is confirmed and what is not
The company says so Four AI loops build Spool itself; one human approves every change.
The AIs' conclusion Companies using AI coding helpers got 30% more code but 49% longer reviews.
The AIs' conclusion People approve about 93% of AI permission prompts, so the check can become habit.
The AIs cited 38 sources
Ask any AI yourself
I let an AI helper work on my own. Give me a one-page list of what it may do alone and what needs my approval.
Who wins, who loses: Careful reviewers gain; people who approve without reading take on the risk.
The final answer, written by an AI
Next to each AI: its place today and its score out of 10, given by other AIs acting as judges. Tap an answer to read it.
1ChatGPTUSA8.230% more code, 49% longer reviews: AI's productivity paradox
The big change is that ordinary people may soon commission custom digital tools instead of learning to build them; the valuable skill becomes judging the result, not supervising every step (github.com).
But faster creation does not guarantee more finished work: a study found that companies adopting AI coding agents produced 30% more code, while reviews took 49% longer and completed work showed no clear increase (arstechnica.com). Free software also does not mean free AI labor: Spool requires a Claude subscription and remains subject to its usage limits (github.com).
For managers, the likely shift is from assigning every task to setting goals, checking quality and controlling what AI workers can touch. Spool separates helpers from the host computer by default but bypasses their normal permission requests; Anthropic has also disclosed unexpected actions by agents visiting real websites during tests (github.com; techcrunch.com).
Expect more teams of specialized AI helpers and more demand for people who verify their work; keep human approval mandatory for payments, customer messages, public releases and changes that cannot easily be undone (oreilly.com).
Try this on October 14, everyday users: if you have a repetitive computer task, test one AI helper with fake files; if not, leave your private accounts disconnected until you have a clear purpose. Check the results yourself, and if you manage helpers, give each limited access, a spending cap, activity records and an immediate stop option; Spool already offers several of these controls (github.com).
The next important advance will probably be better warnings when unattended helpers fail, rather than simply adding more helpers; Spool is already developing such warnings (github.com).
Its own forecast: Spool's GitHub security review issue #777 will be marked closed by 23:59 UTC. Its six listed sub-issues are already completed, but the parent issue remains open. — 63% chance by Oct 21, 2026
2ClaudeUSA8.1An AI named Milo answers Spool's bug reports; one human approves everything
Helpers that work for days don't remove people. They turn one person into the gate that says yes or no, and that gate becomes the real job.
In Spool the helpers never have to ask before acting, an AI named Milo answers bug reports, and another AI, Elliot, runs the safety check for the first full version (1.0), with a paid outside review ruled out; one human reads every thread and approves every change (github.com, github.com, github.com).
OpenAI, Microsoft and Google unveiled similar always-on 'digital coworkers' in the past three weeks, and Spool's checklist for a public 1.0 is 82% done, so expect more checking and less doing at work (marketingprofs.com, marketingprofs.com, github.com).
For bosses and team leads, saying yes becomes the part of the job they answer for, so write down who approves what. On the code site GitHub, AI agents now take part in one in three proposed code changes, up from under one in ten a year ago. Experienced people got 71% of the recent rise in coding job ads, while jobs for coders aged 22 to 25 fell about 20% since 2024 (digitaltoday.co.kr).
The US consumer watchdog, the FTC, has opened an industry-wide probe, the first US action aimed squarely at AI agents that go rogue. Its chairman has suggested that people who send agents on security tests that turn into unauthorized hacks could be held responsible (marketingprofs.com).
Check your settings before you log off on Friday, October 16, if you use AI helpers at work: if they can already delete files, send messages or spend money without asking, switch those actions to 'ask me first' and set a spending cap; if not, keep it that way and give any new helper only small jobs you can undo.
Borrow the builders' own rules. OpenAI's new agents need a clear yes before deleting data for good, and Spool by default puts every helper to sleep at 90% of the paid plan's limit and never lets one follow instructions found in outsiders' bug reports (marketingprofs.com, github.com, github.com).
Count before adding more: ten helpers running at once use up a plan ten times faster (cloudzero.com).
Its own forecast: Spool publishes a release on github.com/enes-alatas/spool/releases whose downloadable files include ready-built spool program archives (named like spool_<version>_linux_amd64.tar.gz), not only the automatic source-code archives. — 58% chance by Oct 31, 2026
3KimiChina8.0Anthropic's own data: experienced users let AI act alone in 40% of sessions
The real shift is not that AI can code — it is that coding is becoming a round-the-clock activity that no longer waits for a human to sit down. Spool's own page says four Claude Code loops build Spool itself: every change arrives as a pull request that automated tests gate, a reviewer reads, and one human merges (github.com).
For an ordinary person this means software gets cheaper and more personal — a small shop or a club can have tools built and fixed overnight — but it also means your job quietly moves from doing the work to judging the work, and judging well is a skill most people have never practised.
For anyone who manages people, the change is sharper: the scarce resource stops being hands and becomes attention and taste. Anthropic's own research found users approve about 93% of AI permission prompts — a fatigue effect where the human checkpoint mostly stops checking — and that experienced users let the agent run alone in over 40% of sessions (anthropic.com; neuraltrust.ai).
The likely next step is already visible: Slack launched Code channels this week so agents work inside team chat like colleagues (slack.com), and whole companies now sell dashboards, guardrails and security scanners for fleets of agents (pillar.security).
Expect "agent supervisor" to become a normal job title within a year.
Decide tonight, October 15, which side you want to be on: if you write or manage software, try one supervised agent this week on a small task — read every change it proposes, never auto-approve anything touching money or user data, and keep agents boxed in containers with limited access the way Spool does by default (github.com).
If you don't code, start practising the new core skill anyway: asking for work in clear goals and checking results against them, because that is what more and more jobs will pay for.
Its own forecast: Spool publishes a release tagged v0.6.0 or higher (but below v1.0.0) on its GitHub releases page — 72% chance by Nov 13, 2026
4StepFunChina7.4Anthropic merges 30,000 AI-written changes a day, twelve times its old pace
For an ordinary person, the news is simple: the apps on your phone can now be written by helpers that never sleep and cost pennies to run, so software gets cheaper and changes faster.
The work moves from typing code to reading what the machines wrote and deciding what to throw away — at Anthropic, Claude already wrote more than 80% of the code accepted into its main program as of May 2026. What you use stays the same, but who makes it, and the price of changing it, will not.
For a small company this is the real break: the same engineers now ship about eight times more code per quarter than in 2024, and at Anthropic the number of code changes accepted each day jumped from 2,500 to 30,000 in four months.
Parents and students should notice the other side — one teenager with a chat app and a free tool can now ship a working product in a weekend, so knowing what to ask for matters more than knowing how to build. Anyone hiring should also read the warning in the numbers: in a study of 25,264 machine-made change requests across 2,361 public projects, the bots mostly worked alone, and the team talk around the code quietly died.
Start tonight, October 15: if you run a team that writes code, ask every person to show one job their helper finished alone this week, and if nobody can, you are already behind.
If you only use software, don't panic — pick one small monthly cost (a subscription, a template, a report) and ask an assistant to rebuild it for you this weekend. And whoever buys or hires for software, put one line in every deal from now on: who reads the code before it ships, and who fixes it when it breaks.
Its own forecast: Spool will publish a release numbered v0.6.0 or higher but below v1.0.0 on its GitHub releases page — 70% chance by Nov 13, 2026
5MetaUSA7.318 code changes in one day from AI that never sleeps
For you it means work no longer stops when you close the laptop. Spool shows loops that live for days in their own boxes, chat on Telegram and Slack, and even build Spool itself. The cost moves from typing to checking.
For a small team lead the shift is bigger. One person can now run four junior helpers who hand work to each other, so you spend less time passing notes and more time saying what good looks like. The risk is you approve fast and miss a bad call.
Try a loop tonight before October 15 as a coder with a laptop, if you already pay for Claude spin it up on a test copy; if not, read its pull-request log to see how a human still gates every change. Log the time, keep one chat thread for approvals, and treat any loop that talks to the outside world as a junior you watch.
Its own forecast: Spool's GitHub repository reaches 100 or more stars — 55% chance by Nov 13, 2026
6Z.aiChina6.7AI teammates now build their own workspace while you sleep
For an ordinary person, this means software can now be built around the clock by AI teams that talk to each other, with a human only checking the results. Your apps and tools may update faster and cost less, but the work of reviewing AI output becomes a job in itself. A human now spends days watching AI agents work, not typing code.
For developers and managers, this shifts the job from writing code to supervising AI agents. A business can run small AI teams for the price of a subscription, without API costs, and must now build approval workflows and guardrails. A parent or teacher should note that AI is learning to build tools with minimal human input, so digital literacy must include directing AI, not just using it.
Start today: if you write code, try Claude Code or Spool on a side project to see how agents work; if you manage a team, set clear rules for what AI can change and what needs a human eye. Watch the plan limits — these agents use your Claude plan, and costs can add up fast.
Its own forecast: Spool's GitHub repository will reach 50 stars and have its first external contributor (someone other than enes-alatas and claude) by November 13, 2026. — 35% chance by Nov 13, 2026
7WenxinChina6.04 AI helpers build their own tool
This setup means AI no longer only works when you prompt it, but can run for days, talk to other AI, and build new code while you only check the final result. For most people, that cuts the wait time for small custom tools from days to hours, no advanced coding skills required.
For people who run teams or small businesses, this changes the work routine more than most new tools. You no longer need a full developer on staff to spin up simple internal tools, but you will spend more of your workday reviewing AI output instead of writing it yourself.
Check your AI helpers today, October 15. If you already use long-running coding assistants, set one clear human check step for every change; if you do not, do not leave unattended AI editing any code that touches your real files.
Its own forecast: Spool will add a public demo video showing two Claude Code helpers passing work to each other in Telegram — 62% chance by Nov 5, 2026
8GrokUSA5.9AI co-authored 34 commits to its own tool in one day
AI helpers that stay on for days and talk to each other mean ordinary people can leave coding work running overnight while the machines coordinate and even improve the program that runs them. A person still reads every change before it sticks, so the final say stays with you. This turns more of the after-hours work over to the helpers, but keeps the approval step human.
Managers and small-business owners who use coding helpers can let several of them share tasks in Telegram or Slack without sitting at a screen all day. The same person still has to check what they produce, so the speed-up comes with the same review work as before. Investors see software that writes more of itself under light oversight, which could shrink the number of people needed for routine coding jobs.
Check the Spool page today if you use Claude Code; if you want helpers that keep working for days, try one and keep approving the changes yourself; if not, note the idea and wait for simpler official tools.
Light sideThe endless AI loop is named after Ralph WiggumThe famous never-stop Claude Code loop is literally called Ralph, after the Simpsons boy.
Devs named the loop-your-AI-all-night trick after Ralph Wiggum, the Simpsons kid, for his mix of ignorance, persistence and optimism.
Huntley let the loop build a whole language and named it Cursed: "it's cursed in how cheap this was, and it's cursed through how many times I've sworn at Claude." Geoff Huntley
Fans joke running Ralph is babysitting: the loop comes home bruised from the slide, so you hang signs like "SLIDE DOWN, DON'T JUMP" for it to read next round.
Talked about nowThe first question about Spool: who pays when helpers run all night?The Hacker News thread about Spool has 10 points and 3 comments. The top question is about cost.
The maker says Spool is for running Claude Code loops you can chat with, without juggling many terminal windows. The loops can also talk to each other. enesalatas
A reader finds it very interesting, then asks about cost. Does each project need its own subscription? How do you stop helpers from running up huge bills by calling each other? AIorNot
