Claude Code just got computer use in the CLI - here's the architecture detail nobody's explaining

🔥

Most posts about this are just "wow Claude can control your mouse now."

That's not the interesting part.

The interesting part is the fallback hierarchy.

Claude tries MCP servers first. Then Bash. Then Claude in Chrome. Screen control only activates when all three fail to reach the task. That tells you exactly when and how to use it.

The security model is also different from what people assume. Unlike the sandboxed Bash tool, computer use runs on your actual desktop with no filesystem isolation. On-screen prompt injection is a real threat vector, not a hypothetical one.

Two more things worth knowing:

App approvals reset every single session. That is intentional trust architecture, not a UX bug.

Your terminal window is excluded from Claude's screenshots the entire time. It cannot see its own output while controlling your screen.

Hard requirements if you want to try it: macOS only, Pro or Max plan, CLI v2.1.85+, and you must authenticate through claude.ai directly.

Drop any questions below. Happy to go deeper on any part of this.

1 comment