From 27c7205d4ed88fc3ef0110c99329268ed2bd52a6 Mon Sep 17 00:00:00 2001 From: "openclaw-docs-sync[bot]" Date: Tue, 28 Apr 2026 00:28:03 +0000 Subject: [PATCH] chore(sync): mirror docs from openclaw/openclaw@c72f8f357b55881cf33c1f4c219a1ceb5a6a3357 --- .openclaw-sync/source.json | 4 +-- docs/platforms/mac/peekaboo.md | 24 ++++++++++++++++ docs/plugins/codex-computer-use.md | 45 ++++++++++++++++++++++++++++++ docs/plugins/codex-harness.md | 5 ++++ 4 files changed, 76 insertions(+), 2 deletions(-) diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json index 5daa4454a..884e3776c 100644 --- a/.openclaw-sync/source.json +++ b/.openclaw-sync/source.json @@ -1,5 +1,5 @@ { "repository": "openclaw/openclaw", - "sha": "56875c4d32038a356f2e6f4e8363edf309dcfca2", - "syncedAt": "2026-04-28T00:22:56.667Z" + "sha": "c72f8f357b55881cf33c1f4c219a1ceb5a6a3357", + "syncedAt": "2026-04-28T00:26:37.361Z" } diff --git a/docs/platforms/mac/peekaboo.md b/docs/platforms/mac/peekaboo.md index 77a0d87c0..c156b3c10 100644 --- a/docs/platforms/mac/peekaboo.md +++ b/docs/platforms/mac/peekaboo.md @@ -4,6 +4,7 @@ read_when: - Hosting PeekabooBridge in OpenClaw.app - Integrating Peekaboo via Swift Package Manager - Changing PeekabooBridge protocol/paths + - Deciding between PeekabooBridge, Codex Computer Use, and cua-driver MCP title: "Peekaboo bridge" --- @@ -17,6 +18,29 @@ macOS app’s TCC permissions. - **Client**: use the `peekaboo` CLI (no separate `openclaw ui ...` surface). - **UI**: visual overlays stay in Peekaboo.app; OpenClaw is a thin broker host. +## Relationship to Computer Use + +OpenClaw has three desktop-control paths, and they intentionally stay separate: + +- **PeekabooBridge host**: OpenClaw.app can host the local PeekabooBridge socket. + The `peekaboo` CLI remains the client and uses OpenClaw.app's macOS + permissions for Peekaboo automation primitives such as screenshots, clicks, + menus, dialogs, Dock actions, and window management. +- **Codex Computer Use**: the bundled `codex` plugin prepares Codex app-server, + verifies that Codex's `computer-use` MCP server is available, and then lets + Codex own native desktop-control tool calls during Codex-mode turns. OpenClaw + does not proxy those actions through PeekabooBridge. +- **Direct `cua-driver` MCP**: OpenClaw can register TryCua's upstream + `cua-driver mcp` server as a normal MCP server. That gives agents the CUA + driver's own schemas and pid/window/element-index workflow without routing + through the Codex marketplace or the PeekabooBridge socket. + +Use Peekaboo when you want the broad macOS automation surface and OpenClaw.app's +permission-aware bridge host. Use Codex Computer Use when a Codex-mode agent +should rely on Codex's native computer-use plugin. Use direct `cua-driver mcp` +when you want the CUA driver exposed to any OpenClaw-managed runtime as a normal +MCP server. + ## Enable the bridge In the macOS app: diff --git a/docs/plugins/codex-computer-use.md b/docs/plugins/codex-computer-use.md index 24df3bc14..7a0c35399 100644 --- a/docs/plugins/codex-computer-use.md +++ b/docs/plugins/codex-computer-use.md @@ -3,6 +3,8 @@ summary: "Set up Codex Computer Use for Codex-mode OpenClaw agents" title: "Codex Computer Use" read_when: - You want Codex-mode OpenClaw agents to use Codex Computer Use + - You are deciding between Codex Computer Use, PeekabooBridge, and direct cua-driver MCP + - You are deciding between Codex Computer Use and a direct cua-driver MCP setup - You are configuring computerUse for the bundled Codex plugin - You are troubleshooting /codex computer-use status or install --- @@ -17,6 +19,49 @@ then lets Codex own the native MCP tool calls during Codex-mode turns. Use this page when OpenClaw is already using the native Codex harness. For the runtime setup itself, see [Codex harness](/plugins/codex-harness). +## OpenClaw.app and Peekaboo + +OpenClaw.app's Peekaboo integration is separate from Codex Computer Use. The +macOS app can host a PeekabooBridge socket so the `peekaboo` CLI can reuse the +app's local Accessibility and Screen Recording grants for Peekaboo's own +automation tools. That bridge does not install or proxy Codex Computer Use, and +Codex Computer Use does not call through the PeekabooBridge socket. + +Use [Peekaboo bridge](/platforms/mac/peekaboo) when you want OpenClaw.app to be +a permission-aware host for Peekaboo CLI automation. Use this page when a +Codex-mode OpenClaw agent should have Codex's native `computer-use` MCP plugin +available before the turn starts. + +## Direct cua-driver MCP + +Codex Computer Use is not the only way to expose desktop control. If you want +OpenClaw-managed runtimes to call TryCua's driver directly, use the upstream +`cua-driver mcp` server through OpenClaw's MCP registry instead of the +Codex-specific marketplace flow. + +After installing `cua-driver`, either ask it for the OpenClaw command: + +```bash +cua-driver mcp-config --client openclaw +``` + +or register the stdio server yourself: + +```bash +openclaw mcp set cua-driver '{"command":"cua-driver","args":["mcp"]}' +``` + +That path keeps the upstream MCP tool surface intact, including the driver +schemas and structured MCP responses. Use it when you want the CUA driver +available as a normal OpenClaw MCP server. Use the Codex Computer Use setup on +this page when Codex app-server should own plugin installation, MCP reloads, +and native tool calls inside Codex-mode turns. + +CUA's driver is macOS-specific and still requires the local macOS permissions +that its app prompts for, such as Accessibility and Screen Recording. OpenClaw +does not install `cua-driver`, grant those permissions, or bypass the upstream +driver's safety model. + ## Quick setup Set `plugins.entries.codex.config.computerUse` when Codex-mode turns must have diff --git a/docs/plugins/codex-harness.md b/docs/plugins/codex-harness.md index 1e1e7cf5b..fd7916d75 100644 --- a/docs/plugins/codex-harness.md +++ b/docs/plugins/codex-harness.md @@ -594,6 +594,11 @@ desktop actions itself. It prepares Codex app-server, verifies that the `computer-use` MCP server is available, and then lets Codex handle the native MCP tool calls during Codex-mode turns. +For direct TryCua driver access outside the Codex marketplace flow, register +`cua-driver mcp` with `openclaw mcp set cua-driver '{"command":"cua-driver","args":["mcp"]}'`. +See [Codex Computer Use](/plugins/codex-computer-use) for the distinction +between Codex-owned Computer Use and direct MCP registration. + Minimal config: ```json5