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.
I let an agent pick its own task every morning for 23 days. 41 runs, 19 reached production, 22 died. The 22 are the reason it works.
An experiment running an AI agent for 23 days to autonomously select and execute tasks via GitHub Actions, with automated checks resulting in a 54% failure rate that enhances efficiency by minimizing manual audits.
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.
Six Months of Writing Code Exclusively with Agents
The author reflects on six months of writing code exclusively with AI agents, discussing the shift from manual coding to agent-assisted development and its implications for productivity and workflow.