클로드 코드 루틴(Routines) 출시

Skip to main content Claude Code Docs home page English Search... ⌘ K Ask AI Search... Navigation Claude Code on the web Automate work with routines Getting started Build with Claude Code Deployment Administration Configuration Reference Agent SDK What's New Resources Getting started Overview Quickstart Changelog Core concepts How Claude Code works Extend Claude Code Explore the .claude directory Explore the context window Use Claude Code Store instructions and memories Permission modes Common workflows Best practices Platforms and integrations Overview Remote Control Claude Code on the web Get started Reference Routines Plan in the cloud Claude Code on desktop Chrome extension (beta) Computer use (preview) Visual Studio Code JetBrains IDEs Code review & CI/CD Claude Code in Slack On this page Example use cases Create a routine Create from the web Create from the CLI Create from the Desktop app Configure triggers Add a schedule trigger Add an API trigger Trigger a routine API reference Add a GitHub trigger Supported events Filter pull requests How sessions map to events Manage routines View and interact with runs Edit and control routines Repositories and branch permissions Connectors Environments Usage and limits Related resources Routines are in research preview. Behavior, limits, and the API surface may change. A routine is a saved Claude Code configuration: a prompt, one or more repositories, and a set of connectors , packaged once and run automatically. Routines execute on Anthropic-managed cloud infrastructure, so they keep working when your laptop is closed. Each routine can have one or more triggers attached to it: Scheduled : run on a recurring cadence like hourly, nightly, or weekly API : trigger on demand by sending an HTTP POST to a per-routine endpoint with a bearer token GitHub : run automatically in response to repository events such as pull requests, pushes, issues, or workflow runs A single routine can combine triggers. For example, a PR review routine can run nightly, trigger from a deploy script, and also react to every new PR. Routines are available on Pro, Max, Team, and Enterprise plans with Claude Code on the web enabled. Create and manage them at claude.ai/code/routines , or from the CLI with /schedule . This page covers creating a routine, configuring each trigger type, managing runs, and how usage limits apply. ​ Example use cases Each example pairs a trigger type with the kind of work routines are suited to: unattended, repeatable, and tied to a clear outcome. Backlog maintenance. A schedule trigger runs every weeknight against your issue tracker via a connector. The routine reads issues opened since the last run, applies labels, assigns owners based on the area of code referenced, and posts a summary to Slack so the team starts the day with a groomed queue. Alert triage. Your monitoring tool calls the routine’s API endpoint when an error threshold is crossed, passing the alert body as text . The routine pulls the stack trace, correlates it with recent commits in the repository, and opens a draft pull request with a proposed fix and a link back to the alert. On-call reviews the PR instead of starting from a blank terminal. Bespoke code review. A GitHub trigger runs on pull_request.opened . The routine applies your team’s own review checklist, leaves inline comments for security, performance, and style issues, and adds a summary comment so human reviewers can focus on design instead of mechanical checks. Deploy verification. Your CD pipeline calls the routine’s API endpoint after each production deploy. The routine 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. Docs drift. A schedule trigger runs weekly. The routine scans merged PRs since the last run, flags documentation that references changed APIs, and opens update PRs against the docs repository for an editor to review. Library port. A GitHub trigger runs on pull_request.closed filtered to merged PRs in one SDK repository. The routine ports the change to a parallel SDK in another language and opens a matching PR, keeping the two libraries in step without a human re-implementing each change. The sections below walk through creating a routine and configuring each of these trigger types. ​ Create a routine Create a routine from the web, the Desktop app, or the CLI. All three surfaces write to the same cloud account, so a routine you create in the CLI shows up at claude.ai/code/routines immediately. In the Desktop app, click New task and choose New remote task ; choosing New local task instead creates a local Desktop scheduled task , which runs on your machine and is not a routine. The creation form sets up the routine’s prompt, repositories, environment, connectors, and triggers. Routines run autonomously as full Claude Code cloud sessions: there is no permission-mode picker and no approval prompts during a run. The session can run shell commands, use skills committed to the cloned repository, and call any connectors you include. What a routine can reach is determined by the repositories you select and their branch-push setting, the environment’s network access and variables, and the connectors you include. Scope each of those to what the routine actually needs. Routines belong to your individual claude.ai account. They are not shared with teammates, and they count against your account’s daily run allowance. Anything a routine does through your connected GitHub identity or connectors appears as you: commits and pull requests carry your GitHub user, and Slack messages, Linear tickets, or other connector actions use your linked accounts for those services. ​ Create from the web 1 Open the creation form Visit claude.ai/code/routines and click New routine . 2 Name the routine and write the prompt Give the routine a descriptive name and write the prompt Claude runs each time. The prompt is the most important part: the routine runs autonomously, so the prompt must be self-contained and explicit about what to do and what success looks like. The prompt input includes a model selector. Claude uses the selected model on every run. 3 Select repositories Add one or more GitHub repositories for Claude to work in. Each repository is cloned at the start of a run, starting from the default branch. Claude creates claude/ -prefixed branches for its changes. To allow pushes to any branch, enable Allow unrestricted branch pushes for that repository. 4 Select an environment Pick a cloud environment for the routine. Environments control what the cloud session has access to: Network access : set the level of internet access available during each run Environment variables : provide API keys, tokens, or other secrets Claude can use Setup script : run install commands before each session starts, like installing dependencies or configuring tools A Default environment is provided. To use a custom environment, create one before creating the routine. 5 Select a trigger Under Select a trigger , choose how the routine starts. You can pick one trigger type or combine several. Schedule GitHub event API Pick a preset frequency: hourly, daily, weekdays, or weekly. See Add a schedule trigger for timezone handling, stagger, and custom cron intervals. Select the repository, the event to react to, and optional filters. See Add a GitHub trigger for the full list of supported events and filter fields. Select API here, then save the routine. The URL and token are generated after the routine is saved, since they depend on the routine ID. See Add an API trigger to copy the URL and generate a token. 6 Review connectors All of your connected MCP connectors are included by default. Remove any that the routine doesn’t need. Connectors give Claude access to external services like Slack, Linear, or Google Drive during each run. 7 Create the routine Click Create . The routine appears in the list and runs the nex