ScreenHand + Anthropic's New Claude Tasks & Cron: Scheduled Desktop Automation

What Anthropic Just Released

Anthropic launched two new features for Claude:

• Tasks — Track multi-step work, organize sub-tasks, and manage progress. Think of it as a project manager built into Claude.
• Cron — Schedule prompts to run at specific times. CronCreate("0 9 * * 1-5", "Do X") runs your prompt every weekday at 9 AM.

These are powerful for code-level work. But Claude still can't see your screen, click buttons, or control desktop apps. That's where ScreenHand comes in.

How ScreenHand Completes the Picture

ScreenHand is an open-source MCP server that gives AI agents direct access to your desktop through native OS APIs. It provides 70+ tools for screenshots, UI control, keyboard/mouse input, Chrome browser automation, and cross-app workflows.

When you combine Claude's scheduling with ScreenHand's desktop control, you get something neither can do alone: AI that controls your computer on a schedule.

Three Integration Patterns

1. Scheduled UI Automation (Cron → Job)

The most common pattern. Claude's cron fires a prompt at a set time, which creates and runs a ScreenHand job.

// Claude Cron triggers every weekday at 9 AM
CronCreate("0 9 * * 1-5", "Post today's update to Instagram")

// The prompt creates a ScreenHand job
mcp__desktop__job_create({
  task: "Open Instagram, upload image, write caption, post",
  steps: [
    { action: "navigate", url: "https://instagram.com" },
    { action: "click", target: "New post" },
    { action: "type_text", text: "Today's update..." },
    { action: "click", target: "Share" }
  ]
})

Use cases: Social media posting, daily report generation, scheduled data exports, recurring form submissions.

2. Code + Visual QA Pipeline (Task → Job)

A coding task completes, then ScreenHand visually verifies the result.

// Step 1: Code task builds the feature
TaskCreate("Build new landing page section")

// Step 2: When done, ScreenHand verifies visually
mcp__desktop__job_create({
  task: "Open localhost:3000, screenshot the page, verify layout"
})

Use cases: Automated visual QA after deploys, UI regression checks, screenshot-based testing.

3. UI Monitoring → Code Fix (Job → Task)

ScreenHand spots something in the UI and triggers a coding task to fix it.

// ScreenHand checks the dashboard
mcp__desktop__job_create({
  task: "Open admin dashboard, check for error alerts"
})

// If errors found, create a fix task
TaskCreate("Fix the 500 error on /api/users endpoint")

Use cases: Production monitoring, error detection, automated bug filing.

Why This Matters

The key insight: Claude's features are the brain, ScreenHand is the hands. Claude decides what to do and when. ScreenHand physically does it on your desktop.

The Persistence Advantage

Claude's cron jobs and tasks are session-bound — they disappear when the session ends (with a 3-day maximum for cron). ScreenHand jobs are different:

• Persist across restarts — Kill the process, reboot your machine, the job is still there
• Resumable — If a job fails at step 5 of 10, it resumes from step 5
• Structured steps — Each step is a concrete action (click, type, navigate), not a free-form description

This means you can use Claude's cron as the short-term trigger and ScreenHand's job system as the durable execution layer. Cron kicks things off, ScreenHand carries it through even if the Claude session dies.

Getting Started

ScreenHand works with Claude right now. Here's how to set it up:

# 1. Install ScreenHand
git clone https://github.com/manushi4/screenhand.git
cd screenhand && npm install
npm run build:native

# 2. Connect to Claude Code
# Add to .mcp.json:
{
  "mcpServers": {
    "screenhand": {
      "command": "npx",
      "args": ["tsx", "/path/to/screenhand/mcp-desktop.ts"]
    }
  }
}

# 3. Start automating
# Just ask Claude: "Post to Instagram every morning at 9 AM"

Once connected, Claude can use ScreenHand's 70+ tools to control your desktop. Add cron scheduling and you have hands-free, recurring desktop automation.

Frequently Asked Questions