◉CLAUDE LABJP
●CLI — Claude Code v2.1.259 landed on September 2. It is a dense release focused on org-wide configuration, unattended runs, and permissions — the most practically useful one this week●MCP — A new managedMcpServers setting lets an organization push HTTP/SSE MCP servers to every user. At the same time allowedMcpServers narrowed in scope, so an allowlist no longer filters managed servers out●HEADLESS — The new --permission-prompts none flag denies anything that would prompt, while the active permission mode, auto included, keeps making its own calls. Useful for anything you run unattended●SECURITY — Bash Read() deny rules had gaps: files passed as option values such as --ignore-revs-file=.env, and compounds like cd DIR && cat FILE, slipped past them. Both are now covered●SLACK — Claude Tag no longer judges messages one at a time. It reads the whole channel, along with its memory and your standing instructions, and is roughly 30% better at staying out of conversations●LEARN — Claude Academy is open. It is a free learning hub built on the 4D AI Fluency Framework that Anthropic uses to onboard its own team, with completion tracked in your Claude profile●CLI — Claude Code v2.1.259 landed on September 2. It is a dense release focused on org-wide configuration, unattended runs, and permissions — the most practically useful one this week●MCP — A new managedMcpServers setting lets an organization push HTTP/SSE MCP servers to every user. At the same time allowedMcpServers narrowed in scope, so an allowlist no longer filters managed servers out●HEADLESS — The new --permission-prompts none flag denies anything that would prompt, while the active permission mode, auto included, keeps making its own calls. Useful for anything you run unattended●SECURITY — Bash Read() deny rules had gaps: files passed as option values such as --ignore-revs-file=.env, and compounds like cd DIR && cat FILE, slipped past them. Both are now covered●SLACK — Claude Tag no longer judges messages one at a time. It reads the whole channel, along with its memory and your standing instructions, and is roughly 30% better at staying out of conversations●LEARN — Claude Academy is open. It is a free learning hub built on the 4D AI Fluency Framework that Anthropic uses to onboard its own team, with completion tracked in your Claude profile
← Back to Blog

How Cowork Transformed My Daily Workflow for Managing 4 Sites

CoworkClaude CodeAutomationIndie DevExperienceOperations

I run four knowledge base sites by myself. Claude Lab, Antigravity Lab, Gemini Lab, and Rork Lab — each covering AI tools in both Japanese and English.

"Updating four sites every single day, alone" probably sounds overwhelming. Honestly, if you'd told me this six months ago, I would have said it's impossible. But thanks to Cowork and Claude Code, it's now my reality.

Before: The Limits of Manual Updates

My old article workflow looked something like this:

  1. Brainstorm a topic (30 minutes)
  2. Research (1 hour)
  3. Write the Japanese version (2 hours)
  4. Write the English version (1.5 hours)
  5. Format MDX frontmatter (15 minutes)
  6. Run generate-content.mjs to rebuild JSON (5 minutes)
  7. Git commit and push (10 minutes)
  8. Verify the Cloudflare build (10 minutes)

About 5 hours per article. Across 4 sites, that's 20 hours for just one article per site. In practice, I could only manage 2–3 articles per week total.

Discovering Cowork

When "Cowork mode" appeared in the Claude desktop app, I initially thought it was just a convenient file management tool.

I set up a single scheduled task as a test — and was stunned. At the scheduled time, it automatically cloned the repository, searched the web for the latest news, generated an article, and pushed to Git. All without a single manual step.

The next morning, I checked the GitHub commit log like checking email, and there it was — a brand new article added overnight. That moment changed everything.

My Current Automation Setup

I now have over 20 scheduled tasks running:

Content auto-updates (4x weekdays / 3x weekends × 4 sites) — Every 6 hours, each site gets a new article. Topics are sourced from web searches for the latest trends, cross-checked against existing articles to avoid duplicates. Each run produces a JA + EN pair.

Weekly blog generation (every Friday × 4 sites) — Automated technical blog posts for each site's theme. Posts like this one are still written by hand, but the technical ones run on autopilot.

Daily premium article generation — Paid content is also generated daily for each site, staggered at 3-hour intervals to prevent conflicts.

Weekly SEO keyword updates — Every Monday, the system searches the web for trending keywords and updates reference data, which feeds into the next article generation cycle.

The Numbers

After about three weeks, here's what changed:

| | Before | After | |---|---|---| | Articles per week | 8–12 | 40+ | | Manual time per article | ~5 hours | Near zero (review only) | | Total articles (4 sites) | ~200 | 600+ | | Language coverage | Mostly Japanese | All articles JA + EN | | Premium articles | A few per month | 120+ |

To be clear, I don't publish auto-generated articles without review. But there's a world of difference between "writing from scratch" and "reviewing a generated draft."

Lessons from Failures

It hasn't all been smooth.

Disk space crisis — The VM's disk filled up completely, killing Bash. The culprit was each scheduled task running npm install from scratch. Solved by switching to --prefer-offline with npm cache.

Task collisions — Multiple tasks running simultaneously caused Git push conflicts. Fixed by staggering each site's execution by one hour and always running git pull --rebase before pushing.

Duplicate topics — The same theme sometimes appeared across multiple sites. Added a step in the skill files to check existing article slugs and avoid overlap.

What Cowork Really Changed

Beyond the technical efficiency gains, the biggest shift was in how I spend my time.

Before, article writing consumed most of my day. Now, I can focus on quality review, site design improvements, new feature development, and my primary work in app development and art creation.

For indie developers, time is the most precious resource. Cowork gives a significant chunk of it back.

What's Next

With over 600 articles across four sites, the collection is still growing. My next milestone is 200 articles per site (800 total), plus reaching the traffic thresholds needed for AdSense.

As Cowork and Claude Code continue to evolve, I hope Dolice Labs can grow alongside them.

If you're an indie developer or solo site operator struggling with the burden of regular content updates, I'd encourage you to give Cowork a try. You might be surprised at just how much it can automate for you.