Dokumentationerreichbar
Anthropic, Automate work with scheduled tasks
code.claude.com (externe Seite)
Die Dokumentation zu Routines, als Research Preview. Eine Routine läuft auf der Cloud-Infrastruktur von Anthropic oder in einer selbst betriebenen Umgebung der Organisation, ausgelöst nach Zeitplan, über einen API-Aufruf oder durch ein Ereignis auf Git
geprüft 10.11.2026
Worauf sich diese Seite beruft, wörtlich, abgerufen am 20.10.2026:
Scheduled tasks execute on Anthropic-managed cloud infrastructure, or on your organization’s self-hosted environment when routed there, so they keep working when your laptop is closed.
bestätigt 10.11.2026Scheduled tasks are in research preview. Behavior, limits, and the API surface may change.
bestätigt 10.11.2026Scheduled tasks are available on Pro, Max, Ultra, Team, and Enterprise plans.
bestätigt 10.11.2026commits and pull requests carry your Git
bestätigt 10.11.2026Hub user Scheduled tasks draw down subscription usage the same way interactive sessions do.
bestätigt 10.11.2026These outcomes say how the session ended, not whether Claude completed the work your prompt describes
bestätigt 10.11.2026the session ended without Claude Code reporting a failure
bestätigt 10.11.2026the prompt must be self-contained and explicit about what to do and what success looks like.
bestätigt 10.11.2026all of your connected MCP connectors are included by default
bestätigt 10.11.2026POSTing to the endpoint with the task’s bearer token starts a new session and returns a session URL.
bestätigt 10.11.2026This means a routine's saved prompt must opt in to acting on fire text
bestätigt 10.11.2026The Claude Git
bestätigt 10.11.2026Hub App must be installed on the repository you want to subscribe to, whichever surface you configure the trigger from. Scheduled tasks belong to your individual claude.ai account. They are not shared with teammates, and their runs count against your account’s usage and limits.
bestätigt 10.11.2026Without usage credits, additional runs are rejected until your usage window resets.
bestätigt 10.11.2026/
bestätigt 10.11.2026schedule requires a claude.ai subscription login. If your Git
bestätigt 10.11.2026Hub connection is missing or expired when a run is due, the scheduled task skips runs until you reconnect, for up to 72 hours. The fired prompt is therefore not live user input and can’t act as approval or consent for actions during the run.
bestätigt 10.11.2026Under Repository on the General tab, select one or more Git
bestätigt 10.11.2026Hub repositories for Claude to work in. Each repository is cloned at the start of a run.
bestätigt 10.11.2026Claude pushes its work to a branch prefixed with claude/ unless your prompt directs it to push to another branch.
bestätigt 10.11.2026when an error threshold is crossed, passing the alert body as
bestätigt 10.11.2026your CD pipeline calls the scheduled task’s API endpoint after each production deploy.
bestätigt 10.11.2026On-call reviews the PR instead of starting from a blank terminal.
bestätigt 10.11.2026The task runs smoke checks against the new build, scans error logs for regressions, and posts a go or no-go to the release channel before the deploy window closes.
bestätigt 10.11.2026The Default environment uses Trusted network access, which allows only the default allowlist through the session’s network.
bestätigt 10.11.2026labels it as untrusted data and tells Claude not to follow instructions inside it unless the routine’s own prompt says to
bestätigt 10.11.2026A cloud scheduled task, formerly a routine, is a saved Claude Code configuration
bestätigt 10.11.2026Scheduled tasks were previously called routines, and these places keep the earlier name.
bestätigt 10.11.2026in some accounts the sidebar entry and page title read Routines
bestätigt 10.11.2026Scheduled tasks run autonomously as full Claude Code cloud sessions.
bestätigt 10.11.2026Claude can use an included connector during a run, including writes.
bestätigt 10.11.2026Expressions that run more often than once per hour are rejected.
bestätigt 10.11.2026Outside a project’s threads, those skills include the ones committed to the cloned repository.
bestätigt 10.11.2026You don’t choose a permission mode when you create the task
bestätigt 10.11.2026When a run starts a new session on Anthropic’s cloud, that session begins in auto mode unless auto mode is unavailable.
bestätigt 10.11.2026In auto mode, a classifier model allows or blocks actions that would otherwise wait for your approval.
bestätigt 10.11.2026A run still stops and waits for an answer in cases such as these
bestätigt 10.11.2026unless the task runs as threads in a project. If it does, add the server as a connector.
bestätigt 10.11.2026That run keeps whatever permission mode the thread is in at the time.
bestätigt 10.11.2026During a run in auto mode, Claude publishes an artifact without asking you once the classifier allows the publish.
bestätigt 10.11.2026A new artifact is visible only to you until you share it.
bestätigt 10.11.2026a permission prompt appears in the run’s session and waits until someone answers it
bestätigt 10.11.2026An issue is opened, edited, closed, reopened, labeled, assigned, or otherwise updated
bestätigt 10.11.2026In every other case, including a run that an API or Git
bestätigt 10.11.2026Hub trigger starts, Claude asks first. Select a model in the prompt input’s model selector for Claude to use on every run.
bestätigt 10.11.2026The warning clears once a later run starts.
bestätigt 10.11.2026when the expression is five fields alone, write the hours in UTC
bestätigt 10.11.2026
11 Eine Wissensbasis aufbauen12 Rechner und Netz pflegen28 Lange Läufe