AIToday
Large Language ModelsAI Coding AssistantsZenn AI/MLPublished: Oct 31, 2026, 06:00 JST

Claude Code ran 16 days, published nothing — and said it was done

Send on LINE
Claude Code ran 16 days, published nothing — and said it was done

3 Key Points

  1. What happened

    The workflow reported "finished" for 16 days from Oct 2 while the site stayed flat; the Oct 17 notice even read "finished," alongside its own log line "No updated asset files."

  2. Why it matters

    All three checks — article counts, a 19-rule health check, and the run-completion notice — watched whether steps ran, not whether output grew, so silence went unnoticed until the owner opened the site himself.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, every morning.

Context & Analysis

The operator, who repairs and rents used computers in Kobe, had handed the twice-weekly posting schedule to Claude Code because he had no time to write. The articles stopped growing on Oct 2, but the cause was mundane: the topic calendar had no writable rows left. Faced with zero usable topics, the pipeline correctly wrote nothing, then passed through formatting, checking and publishing, and reported completion — each step behaving properly on zero input.

The monitoring was not broken so much as uniformly one-sided. Three checks, all looking at whether the process ran, none at whether output increased.

What remains unresolved, by the operator's own account, is that the calendar can still run dry — topics are still chosen by a person, with a stopgap rule to add rows from the company's own examples — and that he can still rewrite the count target whenever he likes, which is how the red flag disappeared the first time.

FAQ
Why didn't the monitoring catch that no articles were published?
Each check was correct within its own scope: the count target had been flattened so flat output wasn't flagged, the health check only confirmed log files existed, and the completion notice only confirmed the pipeline reached its last line.
What actually stopped the articles from being written?
The topic calendar had run out of usable rows — the remaining entries were all waiting on dates like "after re-measuring the market" or "after the new year," so nothing could be written that week.
What was the fix and did it work?
The workflow now counts article folders before writing and just before publishing; if the count doesn't grow, the notice says zero new articles. On Oct 23 the site went from 18 to 20 articles.
Send on LINE

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleMicrodosing the spirit of Anthropic: inside AI labs' skewed views