I Said the Gap Would Close. It Just Did.

Two weeks ago, I published an honest account of what it actually takes to set up OpenClaw: your own AI assistant running 24/7 on your hardware, available on Slack, with persistent memory and real autonomy. I spent a full day fighting CORS errors, token types, and Docker containers. And at the end of it, I wrote this:

"Polished, consumer-ready versions of personal AI assistants are coming, probably this year. There is a real question of whether the gap between self-hosted OpenClaw and Claude's native apps will stay as wide as it is today."

I didn't expect the answer to arrive in two weeks.

What Just Changed

Anthropic shipped three features for Claude Desktop this week that together change things considerably for anyone who doesn't want to lose a weekend to a home server.

Claude Computer. Claude can now control your mouse. Not just generate text, but actually navigate, click, and interact with your screen. You keep full control over what it can access and every action requires your approval. Within that boundary, it can handle tasks that until recently required either a custom automation setup or someone building it for you.

Scheduled Tasks. You can now tell Claude Desktop to do something on a recurring schedule. No code. No server. No n8n workflow. You describe the task, set the frequency, and Claude does it.

Dispatch. This connects your phone to Claude Desktop so you can trigger tasks and get results wherever you are, without sitting at your computer. More on this below.

Together, these three things bring most people much closer to what I have running on my home server, without the setup.

What This Looks Like in Practice

Here are tasks that are now within reach for anyone with a Claude subscription, no technical background required.

Your weekly news briefing. Every Friday morning, Claude visits the sources you care about, summarises the relevant stories, and presents them to you. You pick what's interesting. If you write a newsletter, you've just handled the research phase. If you don't, you've replaced 30 minutes of tab-switching with a clean briefing waiting for you.

Your Monday morning kickoff. Connect Claude to your Google Calendar (the integration is now available) and create a Scheduled Task: every Monday at 9am, Claude reviews your week, spots the key commitments, and tells you how to sequence your day. Not generic advice. Your actual calendar.

The restaurant menu, every week. Your favourite spots change their menu weekly. Claude can check them on Thursday evening, pull the options, and have them ready when you're wondering what to cook or where to book for Friday. And if you want a dinner suggestion for tonight, Claude can make one based on what you've told it you like before. This last part works better with OpenClaw, which keeps memory across sessions more reliably, but Claude Desktop's memory does carry some context forward.

Market watch for your business. If you want to keep an eye on what competitors are shipping or what tools have appeared in your space, Claude can do a weekly sweep and send you a summary. With the right context attached, you're not getting generic news. You're getting something relevant to what you're actually building.

Learning, one day at a time. If you're learning a language or working through a technical topic, Scheduled Tasks turn Claude into a daily prompt. A word every morning. A concept from your reading list every evening. It runs on its own once you set it up.

Skills and Connectors: The Two Things That Make It an Agent

This is the part most people miss when they first hear about Claude Desktop, and it's worth separating clearly because the two concepts do different things.

Connectors give Claude access to the tools you already use. Gmail, Google Calendar, Notion, Slack, Figma, HubSpot, Jira, Linear, Canva, Miro, and dozens more. With Gmail connected, Claude isn't guessing at your inbox: it's reading it. With Google Calendar, it knows your actual week. Without Connectors, Claude is working blind. With them, it's working from your real data.

Skills give Claude a role. Instead of a general-purpose assistant, you get one that's been configured to specialise in something: market research, brand guidelines, internal communications, content creation for a specific platform. Skills are essentially expertise profiles that you can browse, install, and switch between. If you want Claude to do competitive analysis every Monday, you don't just give it internet access — you give it a market research Skill and then give it internet access. The output is a different thing entirely.

Together, these two layers are what turn a capable chat model into something that actually resembles an agent: one that knows what you need it to know, has access to what it needs to reach, and can act on your behalf without you having to explain everything from scratch every time.

Your Phone as the Remote Control

This is where Dispatch comes in.

Dispatch connects your phone to Claude Desktop so that your phone sends the instruction and Claude executes it on your computer, navigating, clicking, completing tasks, in one continuous thread. Your computer sits in the background and Claude is ready to work. You don't need to be at your desk.

Everything described above — the news briefing, the calendar kickoff, the restaurant menu — can be triggered and reviewed from your phone. The setup is simple: give Claude access to your files, let it keep your computer awake, connect it to Chrome, and enable your integrations. After that, your phone is the interface and your computer does the work.

Honest About What It Still Isn't

This is still not the same as what I have running with OpenClaw.

Claude Desktop has memory, but it's shallower than a self-hosted setup. It doesn't live inside Slack or WhatsApp. It won't remember a conversation from three weeks ago the way a persistent assistant would. The scheduled tasks are useful, but they're not the same as an assistant that knows your ongoing projects, carries context across months, and builds a real picture of how you work over time.

What this is: the most accessible version of that vision that's existed so far, available today, for anyone with a Claude subscription.

The Map, As It Stands

If you're wondering where to start:

Claude Desktop with Scheduled Tasks, Skills, Connectors and Dispatch is where most people should begin. No configuration required, genuinely useful for recurring tasks, and it runs on a subscription you may already have. Start here.

OpenClaw on a VPS is for people who want persistent memory, messaging app integration, and more control over their setup. It takes a few hours to configure properly, but the pre-built VPS images have improved a lot. Worth it if you want the fuller experience.

Custom agents with n8n or your own code is for developers and teams with specific requirements that off-the-shelf tools don't cover. Maximum flexibility, maximum effort.

The Honest Conclusion

Two weeks ago I said the wave was coming whether you built the surfboard yourself or not. This week's releases are the clearest sign yet that it's arriving on schedule.

It's not a complete personal AI assistant. The memory has limits, the presence isn't continuous, and Scheduled Tasks can't match a fully autonomous setup. But for the first time, "how do I get an AI agent actually working for me?" has an answer that doesn't require a home server, a Docker container, or a free afternoon of troubleshooting.

Pick one thing you do manually every Monday or Friday. Set up a Scheduled Task for it this week. See what comes back.