Claude Code Routines and Computer Use: What Anthropic's April Update Means for Your Team

TL;DR

On April 14, 2026, Anthropic shipped the biggest practical update to Claude Code since launch — and most of it isn't about code. They introduced Routines (saved Claude Code workflows that run automatically on Anthropic's cloud, even when your laptop is off), a redesigned desktop application, and Computer Use inside Claude Cowork (Claude can now actually open your files, click around your apps, and do the work on a live screen). The short version for non-technical teams: the tool you could already describe work to now runs that work on its own — on a schedule, in the background, across the same apps your team uses. Here's what that means in practice.

What Actually Changed

Three things landed in one release. All three move Claude from “an assistant you open” toward “a teammate that runs.”

1. Routines. A Routine is a saved configuration: a prompt (what you want done), the repositories or documents it needs, and the connectors it uses (your CRM, Slack, Drive, etc.), packaged once and then run automatically. Critically, Routines execute on Anthropic's cloud infrastructure — not on your laptop. That means they keep running whether or not you're at your desk. A Routine that reviews new support tickets every hour does not stop when you go home.

2. Redesigned Claude Code desktop app. Claude Code used to live in a terminal window, which is an instant wall for most non-technical people. The new desktop app has an integrated terminal, a faster diff viewer (so you can see what changed), an in-app file editor, and an expanded preview area. Non-technical people can now actually watch Claude do the work and intervene when they need to — without learning what a shell is.

3. Computer Use in Claude Cowork and Claude Code. If you're on the Pro or Max plan, you can now give Claude permission to actually drive a computer — open files, run apps, point, click, and navigate to what's on screen. Previously, Claude told you what to do; now Claude can do it. For workflows that live inside applications rather than in text, this is the difference between advice and outcomes.

Why This Matters More Than It Sounds

Most business workflows don't live in a single app. They live in the space between apps — and that's exactly where automation used to break.

Think about what a typical operations task actually looks like. Pull a report from the CRM, cross-reference it with a Google Sheet, summarize the gaps in a Slack message, flag the escalations in Linear, and email the top three to the account owner. No single tool does all of that. Traditional automation (Zapier, Make, custom scripts) can glue two or three steps, but it breaks the moment a human judgment call is needed in the middle — and every real workflow has at least one.

Routines plus Computer Use remove that constraint. Claude can read the messy email, make the judgment call about whether it's an escalation, open the right app, update the right field, and write the right follow-up — all on a schedule, all without someone opening a laptop to press go. The parts of work that used to require a person in the loop because the decision was too nuanced for a script can now be handled by the same model your team already talks to in Cowork.

This is the thing to understand: the barrier to automating business work has never really been technical difficulty. It has been the fact that real workflows are too judgment-heavy for rule-based automation and too scattered across apps for a single tool to own. Both of those walls moved this week.

Concrete Examples of What This Unlocks

The same Routine patterns keep coming up across the teams we work with. Here's what they look like in practice.

Morning inbox triage. A Routine runs at 7:00 every weekday. It reads overnight emails, identifies customer escalations using context from your CRM, drafts a reply for each, and drops a ranked list into a Slack channel with the drafts ready to approve. The account manager walks in to a prioritized morning instead of a 140-email wall.

Weekly pipeline report. A Routine runs every Monday at 06:00. It pulls pipeline data from the CRM, cross-references it against last week's forecast, identifies every deal that slipped or advanced, writes a one-page narrative summary, and posts it to the leadership channel. What used to be a RevOps person's Monday morning is now something that's already done when they arrive.

Proposal assembly. A Routine triggered by a new record in your CRM pulls the client's discovery notes, generates a tailored proposal using your template, opens your document editor via Computer Use, formats it the way your brand requires, and drops the final file in the client folder — with a Slack ping to the account owner for review. The two-hour task becomes a ten-minute review.

Customer health monitoring. A Routine runs nightly across your customer base, reads support tickets, product usage data, and recent communications, scores churn risk for each account, and flags the top five for a human to look at in the morning. You stop discovering churn risk at QBR time.

These aren't hypothetical. Every one of them is a pattern that was technically possible before this week but practically out of reach for non-technical teams. Now they're buildable in an afternoon.

What Non-Technical Teams Should Actually Do This Week

Don't try to automate everything. Pick one recurring task that eats a specific block of your week, and turn it into a Routine.

The mistake most teams make when a capability like this ships is trying to automate too much at once. The Routines that stick are the ones that replace a specific, annoying, recurring task — something that shows up on your calendar every week or every morning and that you resent doing. Start there.

The workflow to use:

1. Name the task. “Every Friday at 15:00 I spend 90 minutes pulling weekly numbers and writing the status update.” Be specific. A vague task produces a vague Routine.
2. Write it out as instructions. Pretend you're onboarding a new colleague. What would you tell them to do, in order? This becomes your Routine prompt.
3. Connect the apps it needs. If the task reads from your CRM and writes to Slack, those are the connectors. If it also needs to open a dashboard, that's where Computer Use comes in.
4. Run it once manually, watching what it does. Intervene when it goes off — which it will, the first time. Correct the instructions.
5. Put it on a schedule. Once it does the task cleanly twice in a row, schedule it. That's the moment you get the weekly 90 minutes back.

From first attempt to working Routine, teams we've watched typically take 2–4 hours. The 90 minutes per week it returns pays that back in the first month — and every subsequent week is pure savings.

What to Watch Out For

More capability means more ways to get it wrong. A few things to be aware of.

Computer Use can click anything it sees. That includes buttons you didn't mean for it to touch. Run any Computer Use workflow against a test account first, and keep production-critical actions (sending money, deleting records, publishing to customers) behind a human approval step. The model is careful, but “careful” is not the same as “understands the consequences of your ERP system.”

Routines run when you're not watching. That's the point — but it means you need to check in on them. Build a weekly review into whatever Routine you set up: a summary of what it did, what it flagged, and what it skipped. If something drifts, you'll catch it in week two rather than month three.

The connectors you give it matter. A Routine is only as capable as the apps you've hooked up. If you don't connect your CRM, it can't read from it. Start with the two or three apps where most of the task lives, not the full stack.

It's not magic on messy data. If your CRM is a mess, Routines that read from the CRM will produce messy outputs. The old rule still holds: garbage in, garbage out. Clean the inputs that matter before you automate the task that reads them.

Why We're Paying Attention to This Specifically

Because it moves the line between “things a business person can do with Claude” and “things you need a developer for.”

Every one of the workshops we run with customer teams hits the same wall at some point. A non-technical person builds something genuinely useful in Claude during the session, we all celebrate, and then two weeks later they admit they've stopped using it — because remembering to open Claude, paste the inputs, and run the thing was too much friction for a recurring task. The tool worked. The habit didn't.

Routines fix the habit problem. You don't have to remember to run it. The thing runs on its own. For the first time, a non-technical person can build something that keeps delivering value next month without any ongoing effort from them.

Combined with the redesigned desktop app (so people can actually see what's happening without a terminal) and Computer Use (so Claude can reach into the apps where the work actually lives), this is the update that takes Claude from “a very capable assistant that requires your attention” to “a teammate that works while you're doing something else.”

That is the kind of shift that doesn't show up in benchmarks but does show up in how much your team actually gets done.

How to Get Started

If you're on a Pro or Max plan, everything above is already available in your account. If you're not, the Pro plan is where you get access to Computer Use and Routines.

Two paths from here:

If you have a team that already uses Claude: pick one recurring task on someone's calendar and spend an afternoon turning it into a Routine. Use the five-step workflow above. Report back to the team with what it does and what it saved. That's the fastest way to make the new capability concrete for everyone.

If your team is still at the “we've heard of Claude” stage: this is a fine reason to stop reading and start. The gap between the teams that are building with tools like this and the teams that are still evaluating them is widening every week, and every release like this one widens it further.

The Deployed Kickstart is designed to get a non-technical team from zero to their first working Routine in a single day — including the part where everyone on the team leaves with something running. The Partner program is where we stay with teams as they build the second, third, and tenth Routine across the organization.

FAQ

What is a Claude Code Routine? A saved, automatable Claude Code configuration — a prompt, the repositories or documents it needs, and the connectors it uses, packaged once and scheduled to run on Anthropic's cloud infrastructure. Routines keep running even when your own laptop is off, which makes them suitable for recurring business tasks like morning inbox triage, weekly reporting, or nightly customer health monitoring.

Do I need to be technical to use Routines? No. The redesigned Claude Code desktop app (also launched April 14, 2026) was built specifically so that non-technical people can see what's happening without using a terminal. The skill that matters is being able to describe the task clearly — the same skill that makes you good at onboarding a new colleague.

What is Computer Use in Claude Cowork? Computer Use is a capability that lets Claude actually drive a computer — open files, run apps, click, type, and navigate to what's on screen — rather than just telling you what to do. It's available on Pro and Max plans in Claude Cowork and Claude Code as of April 2026, and it's the piece that lets Claude work inside applications that don't have an API.

Is Computer Use safe to use on production systems? Treat it the way you'd treat any new team member on their first day. Run it against test accounts first. Keep high-consequence actions (sending money, deleting records, publishing to customers) behind a human approval step. And build a review cadence for anything that runs on a schedule, so you catch drift early.

What's the difference between a Routine and a Zapier workflow? Zapier chains fixed steps based on rules. A Routine runs a Claude Code prompt, which means each run can make judgment calls, read messy inputs, handle exceptions, and adapt to context in ways that rule-based automation cannot. The practical difference: Routines can handle tasks that Zapier automations break on.

How quickly can a non-technical person build their first Routine? Most teams get a working Routine running in 2–4 hours on their first attempt, assuming the task they pick is specific and they already have the relevant apps connected. The time drops sharply on the second and third Routine, because the skill is knowing how to describe the task — and that skill transfers.

What should my first Routine be? The task you resent doing every week. Not the biggest, most strategic workflow — the small, recurring, annoying one that shows up on your calendar and eats 60–90 minutes. Automating that gives you a working example, a visible time saving, and the confidence to automate something bigger next.