Failing Loud on Stale Inputs: A Freshness Contract for Unattended Pipelines
How to stop a scheduled, unattended pipeline from silently shipping degraded work when its upstream data is empty or stale. We implement a freshness contract in bash that asserts recency, non-emptiness, and provenance, plus two real pitfalls I hit running Cowork scheduled tasks.
When Your Cowork × GitHub MCP Triage Quietly Drifts Each Run — Field Notes on Idempotency and Label Boundaries
Cowork + GitHub MCP issue triage looks perfect on the first run, then quietly breaks when left unattended: duplicate comments, reclassification churn, rate exhaustion. Field notes on idempotent prompts, label-boundary self-audits, and request budgets that keep weekly triage stable.
My Unattended Task Was Overwriting the Previous Day's Log — the Container's date Was Returning UTC
A Cowork scheduled task that wrote date-stamped logs was silently overwriting the prior day's file. The culprit was the container's date returning UTC. Here is how I isolated it and the permanent fix: pin the timezone, append instead of overwrite, and detect the failure.
Stopping an Unattended Writer From Publishing the Same Article Twice
When a Cowork scheduled task generates articles every day, the real danger isn't a crash — it's quietly publishing a piece that overlaps with one from a few days ago. Here is a gate that compares slug similarity and the day's log before publishing, built from a near-miss I caught this morning.
Why Cowork's bash Says 'No Such File' When Finder Shows It Right There
Connect a cloud-synced folder to Cowork and bash sees empty placeholders while cat fails. Here is how on-demand materialization actually works, and the design patterns that keep your automations from silently dropping data.
Noticing From the Outside When a Scheduled Job Quietly Did Nothing
exit 0, but zero output. How to catch a silent no-op not from the job's own log but from an external heartbeat ledger and ground truth, written from running several sites on a nightly schedule as an indie developer.
Running Cowork Scheduled Tasks in Practice — From a Morning Digest to Unattended Weekly Reports
How to set up recurring runs, reminders, and automated reports with Claude Cowork's scheduled tasks — covering cron basics, prompt design that survives unattended execution, and how to schedule multiple tasks so they stay reliable.
Folding AdMob and Crashlytics into One Morning Check via Cowork Scheduled Tasks — Two-Week Notes
I had been checking AdMob fill rates and Crashlytics surges in two separate dashboards each morning. I folded them into a single Cowork scheduled task. Here are my two-week notes, with the numbers and the friction I ran into.
Honest 6-Month Review of Claude Cowork — What Actually Worked for an Indie Developer
A candid 6-month review of Claude Cowork from an indie developer's perspective. Covers scheduled tasks, skills, and the memory system — what exceeded expectations, what was genuinely painful, and the hard-won lessons that changed how I use AI automation.
Auto-Organizing Dropbox with Cowork — File Classification, Duplicate Removal, and Naming Conventions
When your Dropbox starts feeling chaotic, let Cowork handle it. Learn how to build an automated system for file classification, duplicate detection, and bulk renaming — and schedule it to run weekly.
Cowork × Python Data Analysis Automation: Build a Weekly Report Pipeline with pandas and Matplotlib
Learn how to combine Cowork's scheduled tasks with Python to fully automate your data analysis reports. From pandas aggregation to Matplotlib charts and Google Sheets integration — a complete, production-ready implementation guide.
Claude Cowork Scheduled Tasks — Recurring Runs, Reminders, and Auto-Reports
How to set up recurring execution, one-time reminders, and automatic reports with Claude Cowork's scheduled tasks. From cron syntax to dry runs, timing spread, and idempotent prompts, with the lessons that only show up in real operation.