My Automated Tech News Digest with Claude Cowork Schedules

There are tasks we keep pushing back. Not because they're hard, but because they're repetitive and time-consuming. Daily tech news is one of them: checking Hacker News, scrolling through TLDR, browsing Ruby Weekly, skimming Reddit threads... That easily adds up to 30–45 minutes every morning before you've even opened your editor.

Since late February 2026, Claude Cowork offers a feature that solves this once and for all:
scheduled tasks.

What is Claude Cowork?

Claude Cowork is one of the three primary modes of the Claude desktop app (alongside Chat and Code). While Chat is your conversational AI and Code handles programming tasks, Cowork is Claude in execution mode: it reads files, creates documents, browses the web, and integrates with third-party apps — all autonomously, directly on your computer.

The key difference from a regular Claude chat? Chat gives you answers. Cowork gives you files saved directly to your computer. No copy-pasting from a chat window, no manual saving. The output lands in your folder, ready to open.

Cowork runs in a dedicated virtual machine, isolated from your main OS, and asks for explicit permission before taking significant actions. It's powerful, but not reckless.

Scheduled Tasks: The Feature That Changes Everything

On February 25, 2026, Anthropic announced scheduled tasks for Cowork. The concept is elegantly simple:

Write a prompt once. Pick a cadence. Claude runs it automatically.

No code. No APIs. No cron jobs. No n8n workflow to maintain (I say this as someone who loves n8n, but still).

Each scheduled task spins up its own Cowork session with access to every tool, plugin, and MCP server you've connected. You describe the outcome, set the timing, and walk away.

How to set it up

There are two ways to create a scheduled task:

1. Type /schedule inside any Cowork task — Claude walks you through it interactively, asking clarifying questions before generating the task definition.
2. Click "Scheduled" in the left sidebar — and fill in the form manually: name, description, prompt instructions, frequency, model, working folder.

Once created, the task appears in your Scheduled tasks page. You can pause it, delete it, or trigger it on demand at any time.

⚠️ One important caveat: scheduled tasks only run while your computer is awake and the Claude Desktop app is open. If your Mac is asleep at 9AM, Cowork will skip the run and execute it automatically once the app is back open — with a notification to let you know.

My Setup: A Daily Tech News Digest at 9AM

As a senior Rails engineer, I need to stay on top of a fairly wide range of topics: AI moves fast, the Ruby ecosystem keeps evolving, infrastructure trends shift, and self-hosting communities surface gems you won't find on mainstream tech media.

So I created a scheduled task that runs every day at 9AM with this prompt:

Get daily news from tech (AI, Claude, OpenAI, Ruby, Ruby on Rails, self-hosted, tech, ESO) from popular websites (Hacker News, TLDR, Ruby Weekly, Reddit, Selfh.st, Changelog, Dev.to, Ruby Flow, Boring Rails, Journal du Geek, Les Numériques, Korben).

For each source, extract the most relevant articles or discussions from the last 24 hours.
Group results by topic. Summarize each item in 2–3 sentences. Include the URL. Flag anything particularly noteworthy.

Output a clean Markdown digest saved to my daily-news folder.

The result? Every morning when I sit down with my coffee, a fresh news-2026-03-16.md is waiting in my folder. No tab juggling. No context switching. Pure signal.

Why This Beats My Previous Setup

Before this, I had an n8n workflow doing something similar: 16 RSS feeds → OpenAI summarization → Gotify push notification, every day at 7AM. It worked, but it had real limitations:

• RSS feeds don't cover everything (Reddit, Dev.to discussions, HN comment threads)
• The summaries were flat — no grouping by topic, no relevance ranking
• Maintaining the workflow meant touching YAML and debugging node configs

With Cowork, Claude actually browses those sources the way a human would. It reads the actual content, understands context, and produces a structured digest tailored to what I actually care about. The prompt is plain English. The maintenance overhead is zero.

The Sources I Picked (and Why)

Here's a breakdown of my source list and what each brings to the digest:

The mix covers both English and French-language tech media, both community-driven and editorial sources, and spans from high-level AI news down to niche Rails patterns.

Ideas to Take It Further

Scheduled tasks open up a lot of possibilities beyond simple digests. A few things I'm planning to experiment with:

• Weekly Rails changelog: summarize commits and releases from Rails, Hotwire, Turbo, and Stimulus repos
• AI release tracker: flag any new model releases or API changes from Anthropic, OpenAI, and Mistral
• Self-hosting discoveries: surface new tools from Selfh.st and GitHub trending that fit my homelab stack (Proxmox, Docker, LXC)
• Friday retrospective: compile a weekly summary of all daily digests into a single Markdown file

Availability

Scheduled tasks in Claude Cowork are available on all paid plans: Pro, Max, Team, and Enterprise. It's currently in research preview, which means some limitations apply:

• No memory across sessions (each run starts fresh)
• Desktop only — no browser version, no mobile
• The Claude Desktop app must be open for tasks to execute

For Team and Enterprise plans, admins control Cowork access through a toggle in the admin panel.

Final Thoughts

Scheduled tasks in Claude Cowork feel like the feature that makes agentic AI actually stick in a daily workflow. Not as a demo. Not as a curiosity. As a genuine productivity tool that does the boring-but-important work while you focus on what matters.

For developers especially, the ability to describe a recurring task in plain English — without writing a script, configuring a cron job, or maintaining a workflow tool — is a genuine quality-of-life improvement.

Set it up once. Let it run. Open your editor. Your morning briefing is already waiting.