Timed my agent for a day. it was actually running about a quarter of that, rest was waiting on me to hit approve
Summary
The author reports on timing their AI agent's activity, finding it active only about 2.5 hours out of an 8-hour day due to waiting on approval prompts, and discusses using MiniMax Code for phone-based approvals to manage coding tasks while away.
Similar Articles
Why is your coding agent idle for the eight hours you are asleep?
The author describes a workflow for running an AI coding agent overnight with a single goal, constraints, and a mandatory morning report, to maximize idle compute time.
An agent just coded for 10 days with nobody watching. Qwen 3.8 max
Alibaba's Qwen agent autonomously coded for over 10 days in an empty repo, filing issues, writing code, running tests, fixing failures, and merging. It still required some feedback, but demonstrates a self-correcting autonomous loop.
Do AI agents spend more time waiting for humans than actually working?
A reflection on how AI coding agents often stall while waiting for human approval, highlighting that human availability can be a bigger bottleneck than model capability.
running ~16 agents for a one person business while employed full time: what actually broke and what actually worked
A solo founder running 16 AI agents orchestrated via Paperclip shares what broke and worked, including hallucinated feature promises mitigated by a QA agent, and code-level enforcement replacing prompt rules.
Running a 24/7 AI agent dev team: I route each role to a different LLM (Claude/Kimi/MiniMax/GPT) to dodge a ~$2k/mo API bill. Setup + what actually breaks.
The author describes a setup where different AI models are assigned to specific roles (planning, coding, review) to reduce API costs for a 24/7 autonomous engineering team, and shares common failure points like model wandering and hallucinated ownership.