Skip to content
Call wiki

Can a scheduled Claude task remember what it found yesterday, or does every run start blank?

Last updated 2026-08-25 · Confidence: documented — Anthropic’s Cowork help center and Claude Code docs, read that day; the Cowork project-memory and counter-file claims are inferred.

Keep the state in a file the task reads first and rewrites last — a markdown checklist in the working folder, a Google Doc via a connector, or a committed file in the repo. Every scheduler starts each run as a fresh session, so the file is the memory.

Every run is a new session

Section titled “Every run is a new session”
  • Cowork: “each scheduled task runs as its own Cowork session”, remotely, using connectors and “the files saved to your Claude account”; it “can’t be tied to a folder on your computer” — a task needing local files “will only run locally”.
  • Claude Code cloud routines clone each repository “on every run” from the default branch; the environment cache keeps only what the setup script writes, and mid-session installs “don’t carry over to other sessions”.
  • Desktop local tasks start “a fresh session” too, but run in a working folder you pick, “against whatever state your working directory is in” — so a file written on Monday is there on Tuesday.

Where the state file can live

Section titled “Where the state file can live”
  • Local Desktop task: any file in the working folder (an Obsidian vault works); the run can also “create commits”, so the state gets a history. Auto memory loads every session but Claude decides what to save — preferences, not a ledger (see Memory vs files).
  • Cloud routine: commit the state file to a claude/ branch the prompt reads back, or write a Google Doc through a connector (see Writing to Docs).
  • Cowork: a Google Doc or Drive file through a connector; each run reads it live (see Doc freshness). Cowork projects add project-scoped memory — “Claude can remember context from tasks you’ve run in a project and apply it to future tasks” — but the article never says a scheduled run reads it, or that it holds structured state reliably.

The gate pattern

Section titled “The gate pattern”

A daily prompt that accumulates and acts only when complete: open the ledger; check Slack, email and notes for each missing item under written rules; date what arrived; if all present, act and close the entry; else, near the deadline, report what is still missing. Alejo proposed this shape; the ledger file is what lets it survive the fresh session. Before trusting a scheduler with it, run a two-day counter task (“read counter.txt, add 1, write it back”).

Sources

Section titled “Sources”