Anthropic Splits Remote Agent Control into Dispatch and Remote Control with Reliability Issues

✍️ OpenClawRadar📅 Published: March 22, 2026🔗 Source
Anthropic Splits Remote Agent Control into Dispatch and Remote Control with Reliability Issues
Ad

Anthropic's Split Implementation of Remote Agent Control

Anthropic has taken the core capability from OpenClaw and split it into two separate products aimed at different user bases. This represents a fragmentation of what was previously a unified agent layer in OpenClaw.

Two Separate Products

  • Dispatch: Remote agent control for regular users using Cowork
  • Remote Control: Remote agent control for developers using Claude Code

The concept behind Remote Control is solid: allowing Claude Code to run tasks on your desktop while you monitor and redirect from your phone. For non-technical users, Dispatch makes sense with lower friction and no CLI requirement.

Ad

Reliability Issues

Both implementations currently suffer from significant reliability problems:

  • Mobile connections drop after roughly 10 hours of use
  • Cannot reconnect after disconnection
  • CLI continues to show sessions as "active" even when disconnected
  • No way to determine if the agent is still running or has silently died

Development Context

An independent developer shipped a product called "Dispatch" weeks before Anthropic's announcement, implementing the same functionality. This suggests Anthropic is playing catch-up rather than innovating in this space.

The direction of remote agent control is clearly right, but the current implementation feels fragmented and unreliable. Users who were accustomed to OpenClaw's unified approach now face a split experience with unresolved technical issues.

📖 Read the full source: r/openclaw

Ad

👀 See Also