What you’ll know by the end of this check

The three places to manage routines (and which one wins for what)
How to pause a routine without losing its config
Where past run sessions live after deletion

The shortest possible answer

Click a routine in the list and you land on its detail page. Everything lives there: repositories, connectors, prompt, schedule, API tokens, GitHub triggers, past runs.

Five actions you’ll do repeatedly:

Run now — fire immediately without waiting for the next scheduled time
Pause — toggle the schedule off without deleting the routine
Edit — pencil icon, change any of the five configuration pieces
Delete — trash icon, removes the routine (past sessions remain)
Open a run — click any entry in the run history to see what Claude did

The three management surfaces

Surface	What you can do	What you can’t
Web UI (`claude.ai/code/routines`)	Everything. Create, edit, filter, token ops, GitHub triggers, filters.	Nothing.
CLI (`/schedule`)	Create scheduled routines, update, list, run, delete.	Create API or GitHub triggers, manage tokens.
Desktop app	Same as web for remote tasks. Also shows Desktop local tasks in the same grid.	Nothing extra.

Rule of thumb: use the CLI to create-and-go, use the web when you need anything beyond a schedule trigger, use the Desktop app if you want local + remote tasks in one view.

Running runs

Click any run in the history to open it as a full Claude Code session. You can:

See every tool call, every file edit, every command Claude ran
Continue the conversation from where the routine stopped (useful when a run needs one more nudge)
Create a PR directly from the session if the routine didn’t already
Rename, archive, or delete the session from the dropdown

Every run is a real session you can reopen. Your routine isn’t a black box — the transcript is all there.

Pause without losing config

The Repeats toggle on the detail page pauses the schedule without wiping anything. Paused routines keep their prompt, repos, connectors, triggers, and tokens. Flip the toggle back on and they resume.

Use pause when:

You’re on vacation and don’t want overnight runs
The routine’s blowing past the daily cap and you need to diagnose before it does again
You’re iterating on the prompt and don’t want live fires during edits

Delete and what survives

Deleting a routine removes it from the list. Past sessions created by the routine remain in your session list. You can still read them, reference them, and continue them manually. The tokens get revoked. Any GitHub webhooks get detached.

If you want to clean up fully, delete the past sessions separately after deleting the routine.

CLI quick reference

/schedule              create a new scheduled routine (conversational)
/schedule list         list all routines
/schedule update       edit an existing routine
/schedule run          trigger a routine immediately

The CLI is fastest for daily ops — listing, running now, pausing. Jump to the web when you need to change triggers beyond the schedule.

Things to try right now (8 minutes)

Run /schedule list from Claude Code. Confirm your test routine is there.
Open the web UI for the same routine.
Click Run now and watch the new session appear in the history.
Click the run entry. Open it as a session. Read the transcript.
Toggle Repeats off. Confirm the routine is paused.
Toggle it back on.

The canonical version

Full official docs: code.claude.com/docs/en/routines.

Ready to verify this check?

You’ve paused a routine and resumed it. You’ve opened a past run as a session. You know which surface to reach for (CLI vs. web) for which task. Mark it cleared.