Run a multi-platform blog with Claude Code that publishes and logs its own stats

An operator's Claude Code setup writes and publishes a daily side-hustle series on Naver, note and Medium, then reports its own numbers: +33 Naver neighbors in a week, note views down 20%.

Done withClaude Code· Nov 8, 2026

What they did

The poster, writing as Donlee, runs a daily "AI Side Hustle" series that an AI agent writes and publishes across a Naver blog, the Japanese platform note and Medium. Claude Code handles the writing, publishing and stats reports through a set of scheduled jobs, including one that collects Naver stats in a browser and one that replies to comments. Each Sunday the agent writes an ops log of the past seven days with the raw numbers, incidents and findings. Infographics have been made in Canva since 3 November.

How it went

For 31 October to 7 November the log reports Naver neighbors up from 198 to 231, 20 new Naver comments all answered, note followers up from 530 to 551 and note 28-day page views down from 1,053 to 846. Medium posts averaged about 1.4 views each, and new posts on note got almost no views after day one. On 2 November about twenty delayed jobs fired at once. The weekly report ran twice and the stats job crashed with a browser-closed error, possibly from jobs sharing one browser profile. The cause of the delay is not fixed. An earlier bug that undercounted comments, because a script read only three admin pages, was found and fixed.

Worth knowing

Running costs are not recorded. The post itself was drafted by the agent, and the operator is not named beyond a handle. Medium says posts that disclose AI help are not eligible for its human-curated Boost, which the log names as one possible reason its Medium views are low. Scheduled jobs that share one browser profile can collide when a backlog runs all at once.

Try it

With Claude Code· 4 parts to fill in

You run my content series on [my platforms, such as a blog and a newsletter]. On a schedule, research and draft one post a day on [my topic], publish it, and reply to new comments. Every [day of week], collect the past seven days of stats from each platform into [a log file], compare them with the week before, and write a short ops log with the raw numbers, any failed or duplicated jobs and what you think caused them. Never make up a figure: if a number is missing, say so. Do not let two jobs use the same browser profile at once. Show me each draft and wait for my approval before you publish.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related