Anthropic has launched Routines for Claude Code, a feature designed to automate recurring technical tasks through saved configurations. A routine packages a prompt, one or more repositories, and a set of connectors into a single unit that executes on Anthropic's managed cloud infrastructure. This ensures tasks continue running even when a user's device is offline. Routines support three trigger types: scheduled intervals, API webhooks, and GitHub events, which can be combined within a single configuration to handle complex workflows. Available on Pro, Max, Team, and Enterprise plans, Routines operate autonomously without permission prompts during execution. They function as full cloud sessions, capable of running shell commands, utilizing committed skills, and interacting with external services via connectors. While routines appear under the individual user's account, all actions such as commits, pull requests, and ticket updates are attributed to the user's identity. The feature is accessible via the web interface, the CLI using the /schedule command, or the Desktop application, with all configurations synchronized to the cloud. Common use cases include backlog maintenance, where routines automatically label issues and assign owners; alert triage, which correlates errors with code changes to draft fix pull requests; and bespoke code reviews that apply custom checklists to ensure security and style compliance. Other applications involve deploy verification through smoke tests, documentation drift detection, and automatically porting code changes between SDK repositories. Triggers provide flexibility in how routines initiate. Schedule triggers run on recurring cadences like hourly, daily, or weekly, with times converted to the user's local zone. API triggers expose a dedicated HTTP endpoint, allowing external systems like CI pipelines or monitoring tools to invoke a routine by sending a POST request with a bearer token and optional context text. GitHub triggers automatically start a session when specific repository events occur, such as a pull request being opened, a push to a branch, or an issue update. Users can further refine GitHub triggers using filters based on author, title, branch, or label. Security and scope management are central to the Routines design. By default, Claude can only push to branches prefixed with claude/ to prevent accidental modifications to protected branches, though this can be adjusted per repository. Connectors used by routines are selected explicitly to limit access, and cloud environments can be configured to control network access and environment variables. Usage of Routines counts against the standard subscription limits, with an additional daily cap on the number of runs per account. Organizations with extra usage enabled can continue running routines beyond the cap on a metered basis, while others will face rejection of runs until the daily window resets. Users can monitor their consumption and manage routine runs through the settings dashboard or by interacting directly with the run sessions, where they can review logs, review changes, or continue conversations manually.