← All Borrowed Recipes

Recipe notebook icon

Borrowed Recipe

A morning docs watcher that runs while you sleep

⁠ · ~5 min read

Your docs pages changed overnight: Claude already read them. It checks a dozen pages every morning and tells you only what moved, so a new model or price change doesn’t slip past you for days.

Big thanks to Pesimmoq, whose tidy setup makes this one easy to borrow, with a no-code version too.

🧾 What’s cooking

  • Why: by their own account, they missed a model launch for five days. Their "changed" alert went unread.
  • The dish: a Claude Code routine, a saved prompt plus a repo, run on a schedule in Anthropic’s cloud.
  • As they describe it, a script saves only what changed since yesterday on 12 official pages. The routine reads just that, marks each page "affected", "not affected" or "check", and posts a summary to a repo log and Slack.
  • If a change touches their published guides (a new model, a price, a deprecation), it writes one draft article. The draft ends with an empty "What I verified" section for a person to fill in. It never publishes.
  • Secret ingredient, in their words: "Python finds the diff; the model only judges and writes."

🍳 Difficulty · ⏱️ Prep time

No-code Builder
Difficulty 🟢 Beginner 🟡 Comfortable with GitHub
Prep About 15 minutes About an hour

🛒 Ingredients

👩‍🍳 Method A: no code

Each scheduled run starts as its own session, and the help page doesn’t say whether a run remembers what the previous run saw (Claude Help: scheduled tasks in Cowork). So pick pages that date every entry and ask about recent dates only.

  1. Pick changelogs, release notes, status pages, or pricing pages with a "last updated" date.
  2. In Cowork (or the new combined Claude experience), run the prompt below once and check the answer (Claude Help: getting started with Cowork).
  3. In Cowork, type /schedule, or open Scheduled → New task → Create with Claude or Set up manually.
  4. In the new experience, just say how often, review what Claude proposes, and click Schedule.
  5. Choose hourly, daily, weekly, weekdays, or manually. Manual setup also asks for an approval mode and, optionally, a model.
Every Monday at 9 AM, visit these pages: <URL 1>, <URL 2>.
List only entries dated in the last 7 days, one sentence and a link each.
Mark "matters to me" if it mentions <pricing, a model I use, a deprecation>.
Nothing new? Say "no changes". No dates on a page? Say so. Don’t guess.

👩‍🍳 Method B: builder

Settings are from Anthropic’s docs; the repo layout is Pesimmoq’s.

  1. Make a repo: a page list, a diff script (Claude Code can write it), and a folder of last copies.
  2. Pesimmoq diffs the .md versions of the pages on platform.claude.com, which skips the page clutter.
  3. The docs say the prompt must be self-contained and explicit about what to do and what success looks like (Claude Code docs: routines). Pesimmoq notes it is read from scratch every run.
  4. Their steps: pull, run the script, read the differences, summarize, commit, notify, draft if it matters.
  5. Create it on the Routines page of Claude Code on the web, the Desktop app’s Routines page (choose Cloud), or /schedule in the CLI. Add the repo, an environment, a schedule, and only needed connectors (Claude Code docs: routines).
  6. The Default environment reaches only an allowlist (Claude’s own docs sites included). Other sites need Custom network access with those domains listed (Claude Code docs: cloud environment network access).
  7. Beyond hourly, daily, weekdays or weekly, /schedule update in the CLI sets a custom cron schedule (Claude Code docs: routines).

😋 Taste test

  • No-code: each page shows new entries or "no changes". In Scheduled, edit, pause, resume, delete, or run on demand. Tasks run remotely, so your computer can be asleep (unless the task needs local files or apps) (Claude Help: scheduled tasks in Cowork).
  • Builder: click Run now and read the transcript. A green status only means the session started and exited cleanly, not that the job succeeded (Claude Code docs: routines).

🔥 Watch the stove

  • Plans: routines need Pro, Max, Team or Enterprise (Claude Code docs: routines). Cowork scheduled tasks need any paid plan (Claude Help: scheduled tasks in Cowork). See Claude’s plan pricing page.
  • Runs use your subscription usage. At your limit, extra runs are rejected until the window resets, unless usage credits are on (Claude Code docs: routines).
  • Routines are a research preview, so behavior and limits may change (Claude Code docs: routines).
  • At most hourly. Runs set on the hour can start minutes late, so try 9:07 (Claude Code docs: routines).
  • Included connectors can write without asking, and it all appears as you. Remove the ones it doesn’t need (Claude Code docs: routines).
  • If GitHub disconnects, the routine skips runs for up to 72 hours, then turns off (Claude Code docs: routines).
  • Pushes go to claude/ branches by default; Pesimmoq’s prompt pushes to main on purpose. GitHub branch protection decides what a run can push to (Claude Code docs: routines).
  • What broke for Pesimmoq (their report, not checked by us): the Claude GitHub App had to be installed on their GitHub organization for a private org repo; Slack hit the wrong workspace (the prompt now has the channel ID); the checkout was sometimes stale (it now pulls first).
  • Keep a person in the loop: borrow the "drafts, never publishes" rule. Fetched pages are content, not orders.
  • Need local files or logged-in apps? Cloud routines can’t see your machine. Desktop scheduled tasks run locally, only while the app is open and the computer is awake (Claude Code docs: Desktop scheduled tasks).

📎 Where this came from