Cowork Keeps Crashing? Try a Local Desktop Agent Instead

Cowork runs your desktop environment inside a virtual machine. That means every interaction goes through a virtualization layer - your inputs get translated, the screen gets streamed, and the agent operates on a sandboxed copy of your workspace. When the VM crashes, which happens more often than it should, your entire session is gone.

This architecture creates problems that are fundamental, not fixable with patches. VM snapshots consume memory. Screen streaming adds latency. The sandboxed environment cannot access your local files, installed apps, or authenticated sessions without complex tunneling.

Why Local Agents Are More Stable

A local desktop agent runs as a native macOS process. There is no VM. There is no screen streaming. The agent uses accessibility APIs to interact directly with your applications. When you ask it to open Figma and export assets, it opens the actual Figma app on your actual machine.

Crashes in the agent process do not take down your applications. Your work stays open. The agent restarts and picks up where it left off because your desktop state never changed.

The Performance Difference

VM-based agents add 200-500ms of latency to every interaction. Over a session with hundreds of actions, that adds up to minutes of waiting. Local agents operate at native speed because they are making direct API calls to the operating system.

File access is instant because the files are local. App launches are fast because the apps are already installed. Authentication works because you are already logged in to everything on your machine.

When VMs Make Sense

Remote desktop environments have valid use cases - testing in isolated environments, running agents on servers, multi-OS support. But if you are running the agent on your own Mac to automate your own workflows, the VM layer is overhead with no benefit.

Fazm is an open source macOS AI agent. Open source on GitHub.