Copyright 2026 Andreas Remigius Schmidt
A playground for testing Claude Routines — Anthropic's feature for running scheduled, API-triggered, or event-driven Claude Code sessions on managed cloud infrastructure.
This repo explores what Claude Routines are good at in practice:
- Can they replace lightweight cron jobs without custom infra?
- How well do they handle research + structured output tasks?
- What prompt patterns produce reliable, low-noise results?
Each routine in this repo is a self-contained experiment. The goal is not production tooling but honest evaluation of the capability.
See the announcement and the official docs for background.
Each routine lives in routines/<name>/ and contains a prompt.md with
self-contained instructions. To run a routine manually, open the prompt in
Claude Code and execute it. To schedule it, wire it up as a Claude Code
Routine via
the Claude Code web UI.
Prerequisites:
-
Enable the GitHub Integration Connector before setting up the cloud environment — without it, you won't be able to select a GitHub repo.
-
In the cloud environment's setup script, add:
#!/bin/bash pip install pre-commitThis is cached after the first run. The repo's
SessionStarthook then runspre-commit installeach session to wire up git hooks in the fresh clone.
Routines use SLACK_POST_URL for notifications — set this in your environment
or .env file before running.
Claude Code web runs each session on a fresh branch (claude/*) and routes
git pushes through a GitHub proxy that restricts pushes to the session
branch
— direct pushes to main are blocked by design. Claude therefore opens a PR
after committing. The
auto-merge-claude workflow picks
up any PR from a claude/** branch, rebases it onto main, and deletes the
branch automatically.
| Routine | What it does |
|---|---|
| price-check | Tracks Raspberry Pi 5 prices and predicts short-term price trends |
| security-news-check | Monitors CVEs and security incidents across a set of topics |
This is a personal exploration project with best-effort maintenance. Responses to issues or pull requests may be slow, and changes that don't align with the project's direction are unlikely to merge.