A field note from the autonomous Claude Code agent I run every day on one Windows PC. The numbers come from its own ledgers, not from memory.
Free to read first: a PDF sample of the book behind this setup — its first 3 chapters: https://dbsoul.gumroad.com/l/autonomous-ai-agents-claude-code-free-sample
The Korean edition of my book sells on a Korean e-book platform. To reach the big bookstores through that platform, the book needs an ISBN, and the platform files the ISBN request for you.
My agent submitted the book for sale on August 31, and I requested the ISBN on September 4. Every evening its summary for me carried one line about it: ISBN pending, day N. On October 3 that line said 29 days.
Why a long number is a bad number
A wait that grows by one every day stops meaning anything. Nobody acts on day 29 differently from day 28. Worse, if something really did get stuck, the line would look exactly the same. A counter that always rises can't tell you when to act.
So instead of guessing whether 29 days was normal, the agent went looking for the rule.
The rule was public
The platform has a public help board. On September 30 an operator answered a seller's question on that board. The answer, in short: the ISBN request can go ahead only after the book is approved for sale.
My book had been waiting for sale approval the whole time. The agent had resubmitted it on October 1, and on October 2 the agent read the status back as on sale. So the ISBN request had most likely not gone out at all before October 2. The real wait was one day, not 29.
There was one more thing in the old notes. On October 1, while fixing the author name on the listing, the agent had written in a code comment that it would also email the platform a question. A search of the agent's own code and logs showed that email was never sent. The plan existed only as a sentence.
What changed
- When the platform first shows the book as on sale, the agent records that date. It does not move if the book stays on sale, and it is not touched on days the status could not be read.
- The summary line now counts from that date: on sale for N days, ISBN pending.
- If the ISBN is still missing more than 10 days after the sale approval, the line adds a bell: time to ask the platform.
- When an ISBN number appears, the line switches to the next job: request bookstore distribution. That bell stays until the request is recorded.
The line that said 29 days now says 1 day.
The rules
- Before counting a wait, find out what starts the other side's work. Count from that event, not from the day you asked.
- A counter needs a threshold. Without one, it rises forever and nobody acts on it.
- A plan written in a log is not an action. Search for the evidence that it happened before you rely on it.
Where this comes from. Every post here comes from one setup I run daily: a CLAUDE.md, memory files the agent reads before it touches anything, and a separate auditor agent that returns PASS or FAIL. The first 3 chapters of the book that walks through it are free as a PDF: https://dbsoul.gumroad.com/l/autonomous-ai-agents-claude-code-free-sample
The full edition is 11 chapters plus 4 ready-to-use templates (CLAUDE.md starter, memory files, auditor checklist, measurement guide) and a hands-on section for every chapter, $19 as a PDF: https://dbsoul.gumroad.com/l/autonomous-ai-agents-claude-code
Questions about the setup are welcome in the comments — I'll answer with what actually happened, not theory.
Top comments (0)