The OpenClaw macOS node has a new trick: it can now take a screenshot of your display on demand. PR #67954, contributed by BunsDev, adds a screen.snapshot command to the macOS node's IPC bridge — giving paired agents direct visual access to what's on screen.
What screen.snapshot Does
When a macOS device is paired to an OpenClaw gateway, agents can invoke screen.snapshot to capture the contents of a connected monitor. The command is implemented in Swift using Apple's ScreenCaptureKit framework, the same technology powering macOS's built-in screen recording. Captured frames are encoded (JPEG or PNG), base64-encoded, and returned over the IPC bridge to the gateway where the agent can inspect or act on them.
The command accepts a handful of parameters:
maxWidth— resize the capture to fit within a maximum pixel width, reducing payload size for large displaysformat—jpeg(default, compressed) orpng(lossless, larger)- Display selector — target a specific monitor on multi-display setups
Use Cases
The addition unlocks a range of visual automation patterns:
Visual context for agents — instead of describing what's on screen in a chat message, you can send a screenshot directly. Ask the agent "what's wrong with this error dialog?" and it has the full visual context.
Automated UI verification — an agent running a deployment pipeline can snapshot the screen to confirm that a build artifact launched correctly or that a dashboard is showing expected values.
Remote monitoring — check what's displayed on a paired Mac without physically accessing it, useful for headless or shared workstations.
Pairing with the browser tool — combine screen snapshots with OpenClaw's built-in browser automation to build workflows that mix native macOS UI context with web-level interactions.
Security Considerations
The Aisle Security analysis flagged three medium-severity issues: OS error strings from ScreenCaptureKit being forwarded verbatim to remote callers (CWE-209), the screen.snapshot command proceeding on malformed params due to a silent decode fallback (CWE-20), and the potential for oversized PNG captures to cause excessive memory use (CWE-400).
These were noted and documented during review. The PR was merged with the expectation that targeted hardening follows in a subsequent iteration. In the meantime, users should ensure their gateway's device authentication is properly configured — the screen.snapshot command is only accessible to clients authorized to invoke node commands, so a properly locked-down gateway contains the exposure.
How to Use It
You'll need a paired macOS node running the latest OpenClaw macOS app. Once paired, the screen.snapshot tool becomes available in agent sessions connected to that node. The OpenClaw nodes documentation covers the pairing flow.
The feature is available on the current main branch and will ship as part of the next numbered release. It rounds out the macOS node's growing set of device-level capabilities — alongside camera access, clipboard integration, and local app control — making paired Mac setups considerably more powerful as agent execution environments.