There are now three distinct ways to run Claude on your codebase: Claude Code, Dispatch, and Routines. They all execute AI-driven tasks — but they solve different problems, run in different places, and fit different moments in your workflow.

This guide breaks down when to reach for each one.

Quick Comparison

When to Use Claude Code

Claude Code is the right choice when you’re sitting at your computer and actively working. You prompt it, it executes across your codebase (with full access to git, shell, and your file system), and you review the results in real time.

Use it for:

• Debugging — paste an error, let Claude trace through the code and propose a fix
• Refactoring — rename patterns, extract functions, restructure modules
• Code review — walk through a diff with Claude and get feedback before pushing
• Exploratory development — prototype a feature interactively, adjusting as you go

The key trait: you’re at the keyboard, steering the work. Claude Code is a pair programmer, not an autonomous agent. It has the broadest availability of the three — every paid plan and the API.

When to Use Dispatch

Dispatch fills the gap between “I have an idea” and “I’m not at my laptop.” You send a task from the Claude mobile app, and it routes to Claude Code (or Cowork) running on your desktop. When the work is done — or when it needs your approval — you get a push notification.

Use it for:

• Commute ideas — “Add input validation to the signup form” sent from your phone
• Quick fixes on the go — “Fix the broken import in utils/auth.ts” while you’re grabbing coffee
• Review prep — “Summarize the open PRs in the main repo” before a meeting

Dispatch maintains a persistent thread between mobile and desktop, so context carries over. It launched as a research preview on March 17, 2026, and requires Pro or Max — it’s not available on Team or Enterprise plans. Your desktop app needs to be running for Dispatch to execute tasks.

When to Use Routines

Routines are for work that should happen without you thinking about it. You configure a prompt, connect a repo, and set a trigger — a cron schedule, an API call, or a GitHub webhook. Routines run on Anthropic’s cloud infrastructure, so your laptop can be off.

Use them for:

• Nightly test runs — run the full suite every night, get a summary in the morning
• Weekly dependency updates — check for outdated packages and open a PR every Monday
• PR review on push — automatically review every pull request when it’s opened
• Changelog generation — summarize commits into release notes on a schedule

Routines are currently in research preview. They’re the most “set it and forget it” option — no interactivity, no laptop required, just reliable automated work.

Can You Combine Them?

Yes, and that’s where things get powerful. A few examples:

1. Routines + Code: A Routine runs nightly tests and flags failures. Next morning, you open Claude Code to debug and fix them interactively.
2. Dispatch + Code: You send a task from your phone via Dispatch. Later, you sit down and continue the thread in Claude Code to refine the result.
3. Routines + Dispatch: A Routine opens a PR for dependency updates. You review the notification on your phone and approve it via Dispatch.

Think of them as layers: Routines handle the automated baseline, Dispatch bridges the gap when you’re mobile, and Code is your hands-on tool for deep work.

Decision Flowchart

Is this a recurring or automated task?
  └─ YES → Use Routines (schedule it, forget it)
  └─ NO
      ├─ Are you at your desk?
      │   └─ YES → Use Claude Code (interactive, full control)
      └─ Are you away from your laptop?
          └─ YES → Use Dispatch (phone → desktop, async)

That’s really all there is to it. Match the tool to the moment.

Related Links

• How to Use Claude Code
• What Is Claude Dispatch?
• Claude Code Routines Guide
• Claude Code Desktop Redesign Guide