◉CLAUDE LABJP
●CC 2.1.328 — Claude Code 2.1.328 (11/19) fixes saving a scheduled task sometimes wiping your other tasks●SONNET 4.5 — Retires on the Claude API on 11/30, 10 days left. Sweep model IDs in code and saved settings in one pass●USAGE — Users report usage limits running out 3–5x faster since the week of Nov 9●NEW — One Source of Truth for MCP Config Across Claude Code and Gemini CLI●GEMINI API — The Gemini API now has tool retrieval (Preview), loading tool definitions only when needed●CREDIT — Seeing a low Credit balance? First check which billing account it refers to●CC 2.1.328 — Claude Code 2.1.328 (11/19) fixes saving a scheduled task sometimes wiping your other tasks●SONNET 4.5 — Retires on the Claude API on 11/30, 10 days left. Sweep model IDs in code and saved settings in one pass●USAGE — Users report usage limits running out 3–5x faster since the week of Nov 9●NEW — One Source of Truth for MCP Config Across Claude Code and Gemini CLI●GEMINI API — The Gemini API now has tool retrieval (Preview), loading tool definitions only when needed●CREDIT — Seeing a low Credit balance? First check which billing account it refers to
Articles/Cowork
◈ Cowork/2026-11-20Beginner

Copy Your Scheduled Tasks' Prompts and Times Once a Week, So You Can Restore Them If They Vanish

Scheduled tasks can disappear or need rescheduling after an app update or a save that fails to read its file. Here is a weekly habit for keeping three things—prompt, schedule, and connected folders—in your own folder, plus a small script that tells you which copies changed since last week.

Cowork69Scheduled Tasks20BackupBeginner

On a Friday morning, I opened the task list and couldn't find the scheduled task that collects my app reviews. I had updated the desktop app the night before.

It turned out the list had simply been re-sorted, and the task was further down. But for those few seconds my stomach dropped, because I had nothing to rebuild it from. As an indie developer I had grown that prompt line by line over weeks, and I no longer remembered which sentences I had added, or why.

Here is the one thing I'd like to share first: the source of truth for a scheduled task should live in your own folder, not inside the app. Not daily—once a week, three things.

Scheduled tasks live somewhere that keeps changing

The Claude Code changelog has had a run of fixes around saving scheduled tasks in just the last few days:

  • 2.1.328 (Nov 19): fixed saving a scheduled task erasing the project's other saved tasks when the scheduled tasks file can't be read
  • Same release: fixed a task with a typo in that file being deleted the next time the file was saved
  • 2.1.329 (Nov 19 UTC): in new signed-in sessions, most tasks saved by earlier versions need scheduling again

Cowork's scheduled tasks and Claude Code's are not the same screen or the same mechanism. Still, I read this run of changes as a signal—if you assume "it's in the app, so it's safe," one update can put a prompt you've been refining out of reach.

Only three things to copy

  1. The full prompt (the part you can't recreate)
  2. Frequency and time (for example, weekdays at 8:40)
  3. Connected folders and connectors (what it reads, where it writes)

Model choice and small settings can be decided again while looking at the screen. The little lines you added over time—"don't notify in this case," "never delete this row"—are what you can't rebuild from memory.

One file per task

I keep a folder called scheduled-task-copies inside my synced folder, with one Markdown file per task:

# Review collection (weekday mornings)
- Schedule: weekdays 8:40
- Folder: app-ops/reviews
- Connectors: none
- Last copied: 2026-11-20
 
## Prompt
(paste the full prompt from the task screen here)

At first I pasted every prompt into a single long file. It didn't work well—I couldn't tell which task had changed, so I ended up rereading everything. One file per task, named after the task, fixed that.

A small script that shows only what changed

Once a week, the script copies the notes into a dated folder and compares them with the previous week. The point: if a copy disappeared on your side, it may be a hint that a task disappeared in the app too.

from pathlib import Path
from datetime import date
import filecmp
import shutil
import sys
 
BASE = Path(sys.argv[1]) if len(sys.argv) > 1 else Path.home() / "scheduled-task-copies"
SNAP_ROOT = BASE / "_weekly"
 
 
def latest_snapshot():
    if not SNAP_ROOT.exists():
        return None
    dirs = sorted(d for d in SNAP_ROOT.iterdir() if d.is_dir())
    return dirs[-1] if dirs else None
 
 
def main():
    notes = sorted(BASE.glob("*.md"))
    if not notes:
        print(f"No copies found in {BASE}")
        return 1
 
    prev = latest_snapshot()
    today = SNAP_ROOT / date.today().isoformat()
    if prev == today:
        print("Today's snapshot already exists.")
        return 0
 
    today.mkdir(parents=True)
    for note in notes:
        shutil.copy2(note, today / note.name)  # never overwrites or deletes old snapshots
 
    print(f"Copied {len(notes)} notes to {today.name}. Compare this count with the app's list.")
    if prev is None:
        print("First snapshot. Differences will show from next week.")
        return 0
 
    old = {p.name for p in prev.glob("*.md")}
    new = {p.name for p in notes}
    for name in sorted(new - old):
        print(f"added: {name}")
    for name in sorted(old - new):
        print(f"missing: {name}  <- check whether it's gone in the app too")
    for name in sorted(old & new):
        if not filecmp.cmp(prev / name, today / name, shallow=False):
            print(f"changed: {name}")
    print(f"compared with: {prev.name}")
    return 0
 
 
if __name__ == "__main__":
    sys.exit(main())

Why it's written this way: snapshots are append-only, because a comparison tool that deletes old copies defeats its purpose. shallow=False compares contents, not timestamps, since synced folders can touch timestamps just by opening a file. And it prints the count every time because the script can't see inside the app—the final check is matching that number by eye.

If you don't use a terminal, put the script in the folder and ask Cowork to "run this script and show me the result."

If you think a task vanished

  1. Check whether it's just hidden. Sorting or filters may have moved it; finished one-off tasks may be hidden from the default list.
  2. Update the app. Fixes to saving are landing release by release.
  3. Rebuild from your copy. Paste the prompt as is—don't rewrite it from memory.
  4. Update "Last copied." The rebuilt task becomes next week's baseline.

Closing

Since I started keeping copies, I hesitate less before adding a line to a prompt. Knowing I can restore it makes small experiments feel cheap.

Start with the single task you'd least like to lose, and paste its prompt into one file. The rest can wait until next Friday.

Share

Thank You for Reading

Claude Lab is ad-free, supported entirely by members like you. We publish practical guides daily with implementation code, benchmarks, and production-ready patterns. If you've found it useful, we'd love to have you on board.

  • ✦Copy-paste ready implementation code
  • ✦New advanced guides published daily
  • ✦$5/mo or $10 for lifetime access
View Membership →

If you found this article helpful, a small tip ($1.50) would mean a lot to us. Your support helps keep this site ad-free and covers server and hosting costs.

Related Articles

◈ Cowork2026-10-26
I Linted 36 Unattended-Run Prompts: All 7 'Use This Tool' Hits Turned Out to Be Bans
One permission dialog is enough to stall an unattended task, because nobody is there to click it. This note covers a lint script that counts prompt lines that tell the task to use such a tool, why a banned-word grep gave seven false alarms, and how matching on word stems fixed it.
◈ Cowork2026-10-22
Half My Scheduled-Task Logs Were Unreadable, So I Added One Mark Line Instead of Widening the Regex
Only about half of 1,076 daily log entries yielded a result. Widening the regex recovered 35 and raised false alarms, so I wrote a fixed one-line mark per run and a morning check script.
◈ Cowork2026-10-21
Why I Stopped Borrowing a Stale Repo and Started Cloning Fresh After a Scheduled Task Couldn't Write to Shared /tmp
A scheduled task stopped because it could not create its clone directory under /tmp. Here is how I traced it, the borrowable clone that was about 9.6 hours behind, the cost of cloning fresh every run, and a script that picks a working directory.