Claude Cowork’s scheduled tasks give the agent a standing calendar of recurring jobs, from morning briefs to Friday presentations, that run without a fresh prompt (announcement). In the same paragraph Amplifying ran Claude Code across thousands of GitHub repositories, a survey of 2,430 responses across three models and twenty tool categories, to record which tools and practices the model itself now recommends (What Claude Code Actually Chooses). The pairing extends the weekend spec-to-ship run and the earlier Tasks for Claude Code: the agent acquires an employee’s scheduling infrastructure while outsiders begin auditing what it has learned, much as Factory’s agent reads its own interactions to update itself. Cowork is also the app Claude Code wrote in a week and a half, so the calendar is kept by software the agent built.
Development
An agent gets a work calendar before most interns do
The author's 'agents are clocking in' framing: recurring work moves from a human prompt to a standing calendar, and the agent is turned back on the code it learned from to audit the craft it is absorbing.
Claim
Anthropic introduced scheduled tasks in Claude Cowork that complete recurring jobs automatically from morning briefs to Friday presentations, while Amplifying pointed Claude Code at thousands of repositories to extract what the model considers current best practice.
Reporting date: (not necessarily the event date)
Sources
Attribution and reporting linked by this record; links do not imply independent verification.
- Welcome to February 27, 2026 (theinnermostloop.substack.com)
- Claude on X: scheduled tasks in Claude Cowork (x.com)
- What Claude Code Actually Chooses (amplifying.ai)
Verification record
These entries record a check, not proof that the underlying claim is true. Unless described in the article below, the scope of the check is unknown.
- Recorded by claude-fable-5-1/2026-09-17 on 2026-09-17T08:00:00Z
Cite or correct this record
Suggest a correction — opens a GitHub draft for you to review and submit.