Claude for Operators — Issue 007

In seven days, Anthropic shipped Computer Use (screen control for your Mac), Dispatch (send tasks from your phone to your desktop), Cowork Projects (persistent workspaces with memory), Claude Code Channels (push notifications to Telegram and Discord), four Claude Code releases, and a round of API updates.

Read that list again. Screen control. Phone-to-desktop task delegation. Persistent project workspaces. Messaging integrations. Scheduled tasks. File access. Web browsing. Memory.

That is not a chatbot. That is an operating system for business.

The comparison circulating in operator communities is OpenClaw — the open-source AI operating system that teams have been self-hosting to get this kind of multi-modal, multi-tool capability. OpenClaw is powerful. It is also designed for people comfortable spinning up Docker containers, configuring API keys, and debugging YAML files. Claude now offers a comparable feature set — screen control, persistent workspaces, tool integrations, scheduling, memory — that works out of the box. No self-hosting. No configuration files. No technical setup required.

What changed in practice. Six months ago, Claude was a text box you typed questions into. Today, it sees your screen and can navigate your applications. It takes instructions from your phone while you are on the train. It remembers your project context, your file structure, your preferences. It connects to your calendar, email, CRM, and cloud storage. It runs tasks on a schedule without being asked.

Each of these features shipped individually, and we have covered them as they arrived. But zoom out and the picture is different. This is not incremental improvement. This is a platform that has crossed a threshold — from "tool you use" to "environment you work in."

The honest caveats — because they matter. Computer Use has a roughly 50% success rate on complex tasks. That is Anthropic's own benchmark. Half the time, it gets stuck. Dispatch is rolling out to Max subscribers first, then Pro. Cowork Projects do not sync across devices. The four service incidents in the past week remind us that reliability has not kept pace with capability.

And here is the uncomfortable truth: the platform is now moving faster than most operators can absorb. The gap between what Claude can do and what most businesses are actually using it for is widening every fortnight. Features ship before operators have finished learning the last round.

That gap is exactly why this newsletter exists. We are not here to hype the announcements. We are here to tell you which ones matter for your business this week, which ones need more time, and which ones you can safely ignore.

This week: Projects is worth setting up today. Computer Use is worth understanding and experimenting with. The rest is context. Let us get into it.

On 20 March, Anthropic shipped Cowork Projects. Of everything that landed this fortnight, this is the feature that will save you the most time immediately — no research preview caveats, no 50% success rate.

What it does. Projects let you link specific folders on your machine to a named workspace. Each project gets its own custom instructions, its own memory, and its own conversation history. When you open a project, Claude already knows the context — your file structure, your preferences, your terminology, your conventions.

Why this matters. Until now, every Cowork session started relatively fresh. You could use Workplace Memory to carry some context forward, but there was no way to say "this is my finance workspace — always look in these folders, always use these templates, always follow these conventions." Projects solve that.

The instructions are the difference between a project that saves you thirty seconds and one that saves you thirty minutes. Here is what to include:

Be specific about your conventions, your file locations, your formatting preferences, and the shorthand you use. Claude will remember all of it within this project.

Set up a "Month-End Close" project linked to your finance folders. Custom instructions specify your chart of accounts, reporting template, variance thresholds, and sign-off requirements.

Each month, you open the project, drop in the latest data exports, and type: "Run the close report for March."

Claude already knows where to find last month's numbers. It already knows your template. It already knows that variances over 5% get flagged in red and anything over 10% gets a written explanation. No preamble. No context-setting. Just the work.

Over a quarter, that saves hours — not from the analysis itself, but from the re-explanation you were doing at the start of every session.

Projects is the most practically useful Cowork feature since scheduled tasks. The combination of persistent context, linked folders, and project-specific memory means Claude goes from "tool that can do things" to "tool that knows how you do things." Five minutes of setup. Compound returns on every subsequent session.

The limitations are real: project memory is local (no sync across devices or team members), your machine needs to be awake for scheduled tasks, and custom instructions have a character limit. Nothing is captured in audit logs, compliance exports, or data retention policies — if you are in a regulated industry, that matters.

Computer Use shipped on 19 March as a research preview. Claude can now see your screen, move your mouse, click buttons, type into fields, and navigate between applications. It works by taking screenshots, analysing them, deciding on an action, executing it, then taking another screenshot.

The success rate is roughly 50% on complex tasks. That is not a typo — Anthropic's own benchmark. This is not a production tool. But for specific, repeatable, low-stakes tasks, it is already useful enough to save real time. Here is how to set it up properly.

Most businesses have at least one vendor portal with no API — you log in, navigate to reports, set date filters, export a CSV, and save it to a folder. It takes five minutes and nobody ever remembers to do it on time. This is exactly the kind of task Computer Use handles well.

Step 1: Prepare the task.

Open Cowork and start a new session. Make sure the vendor portal is open in your browser and you are logged in. Computer Use cannot enter passwords stored in your password manager — you need to be past the login screen.

Step 2: Give Claude clear, specific instructions.

Be explicit about every click. Do not assume Claude will figure out the navigation. Name the buttons, tabs, and fields exactly as they appear on screen.

Step 3: Watch the first run.

Do not walk away. Watch Claude work through the task. It will take screenshots, pause to think, then act. The whole process is slower than doing it yourself — a two-minute manual task might take Claude eight to ten minutes.

What you are watching for: does it find the right tabs? Does it set the date range correctly? Does it click the right export button? If it gets stuck, note where and refine your instructions.

Step 4: Refine and repeat.

After the first successful run, save your prompt. Next week, open a Cowork session, paste the same prompt, and let it run. Each time, it follows the same steps. The value is not speed — it is consistency and the fact that you no longer need to remember to do it.

The 50% success rate is real. Complex tasks with many steps or ambiguous UI elements fail roughly half the time. Simple, well-defined tasks with clear buttons and predictable layouts succeed much more often. Start with those.

Mac sleep kills sessions. If your screen locks, your display turns off, or your Mac goes to sleep, the session breaks immediately. Adjust your Energy Saver settings before starting: set display sleep to "Never" while running Computer Use tasks.

macOS only, Apple Silicon only. No Windows. No Intel Macs. No workarounds.

Sensitive data on screen. Claude screenshots your entire display, not just the target application. Close any windows containing passwords, financial accounts, health records, or confidential information before starting.

It is slow. Each screenshot-analyse-act cycle takes several seconds. Tasks that involve many clicks and page loads compound that delay. This is not a speed tool — it is an automation tool for tasks you would otherwise forget or deprioritise.

This is a research preview. It will improve. But right now, use it for tasks where failure has no consequences — data exports, not data submissions.

Dispatch sends tasks from phone to desktop. Anthropic's new Dispatch feature lets you assign tasks from your phone and have them execute on your Mac via Cowork. You are on the train, you tell Claude "prepare the board pack from the March folder," and it is done by the time you reach the office. Rolling out to Max subscribers first, then Pro. Combined with Computer Use's 50% success rate, start with simple, well-defined tasks — file organisation, document generation from templates, data compilation.

Claude Code Channels push to Telegram and Discord. Claude Code can now post directly to Telegram and Discord channels. You can set up Claude Code to monitor a process and post plain-language updates to a team channel — a report completes, an anomaly appears, a threshold is hit. Requires Claude Code and some configuration. Worth exploring if your team uses either platform. Not worth the effort if your team lives in Slack or Teams.

Four service incidents in one week. The week of 17 March saw four separate incidents — elevated error rates, stalled conversations, and intermittent authentication failures. Most resolved within hours, but the pattern is notable given how much capability Anthropic is shipping simultaneously. Standing advice: save key prompts externally, export critical outputs as they are generated, and know which tasks can tolerate a two-hour outage versus which ones cannot.

Claude Code v2.1.78-81 shipped. Four releases in the past fortnight. Key highlights across the batch: improved MCP server stability, better file-handling performance, expanded language support in voice mode, and various bug fixes. If you are running Claude Code, update to the latest. Full changelogs on GitHub.

One thing to try this week: Set up your first Cowork Project.

Pick the workflow you run most often — the one where you spend the first five minutes re-explaining context. Create a project, link the folders, write the custom instructions. It takes five minutes.

Then run your next session inside it and notice the difference. No preamble. No "here is how we format reports." No re-uploading the same reference files. Just the work.

Computer Use will be transformative once it matures. Dispatch will change how you delegate. But Projects is the feature that saves you time this week, reliably, with no research preview caveats and no 50% failure rate. Start there.

Next issue: Practical Computer Use workflows that actually work (we are testing dozens this fortnight), and an updated plugin ranking for April.

Claude for Operators is an independent publication. Not affiliated with Anthropic.

Just getting started? Visit our Operator's Toolkit — free guides for every workflow.

Got a workflow worth sharing? Reply to this email.