Scale computer-use 2.0 with open-source drivers, cross-OS sandboxes, and benchmarks for training, evaluation, and data generation.
Rust agentai-agentapplecomputer-usecomputer-use-agentcontainerizationcuadesktop-automationhacktoberfestlumemacosmanusoperatorswiftvirtualizationvirtualization-frameworkwindowswindows-sandbox
fix(cua-driver-rs): post-install + Skill hints route through mcp-config (not the broken `claude mcp add -- … --flag` line) (#1681)
Francesco Bonaccief7e2b605c4f
diff --git a/libs/cua-driver/rust/Skills/cua-driver/README.md b/libs/cua-driver/rust/Skills/cua-driver/README.mdindex 4e741495a9..07bd363fac 100644--- a/libs/cua-driver/rust/Skills/cua-driver/README.md+++ b/libs/cua-driver/rust/Skills/cua-driver/README.md@@ -143,12 +143,15 @@ trycua.com in Edge". You can also invoke it explicitly:## Claude Code MCP compatibility mode-For normal skill-driven use, prefer the CLI or the standard MCP server. If you want Claude Code's vision/computer-use-style flow to ground on CuaDriver screenshots, register the compatibility server:+For normal skill-driven use, prefer the CLI or the standard MCP server. If you want Claude Code's vision/computer-use-style flow to ground on CuaDriver screenshots, register the compatibility server. The cleanest path is to let `cua-driver` print the right command for your shell:```bash-claude mcp add --transport stdio cua-computer-use -- cua-driver mcp --claude-code-computer-use-compat+cua-driver mcp-config --client claude+# then paste + run the printed `claude mcp add-json …` line```+Under the hood this registers a `cua-computer-use` stdio server that runs `cua-driver mcp --claude-code-computer-use-compat`. The `add-json` form sidesteps a PowerShell arg-parsing quirk that mangles long flags following `--`.+This mode exposes the normal CuaDriver tools and changes only `screenshot`. The compatibility screenshot requires `pid` and `window_id`, captures that window only, and establishes a window-local pixel coordinate frame. It does not call Anthropic APIs or expose Anthropic's native computer-use API tool.Use MCP for this Claude Code vision/computer-use-style path. CLI screenshots still work as CuaDriver calls, but they do not expose the `mcp__cua-computer-use__screenshot` tool name that Claude Code appears to use as the image-grounding cue.diff --git a/libs/cua-driver/rust/Skills/cua-driver/SKILL.md b/libs/cua-driver/rust/Skills/cua-driver/SKILL.mdindex 3144129b8e..d99fde21b7 100644--- a/libs/cua-driver/rust/Skills/cua-driver/SKILL.md+++ b/libs/cua-driver/rust/Skills/cua-driver/SKILL.md@@ -75,7 +75,7 @@ server path above. If the user explicitly wants Claude Code'svision/computer-use-style flow, they can register:```bash-claude mcp add --transport stdio cua-computer-use -- cua-driver mcp --claude-code-computer-use-compat+cua-driver mcp-config --client claude # then paste + run the printed line```Observation: Claude Code vision flows appear to treat a screenshotdiff --git a/libs/cua-driver/scripts/install.sh b/libs/cua-driver/scripts/install.shindex b80cd03b8d..f2bb817a2c 100755--- a/libs/cua-driver/scripts/install.sh+++ b/libs/cua-driver/scripts/install.sh@@ -432,17 +432,17 @@ Next steps:B. As an MCP server — run the one matching your client. Each is alsoavailable via 'cua-driver mcp-config --client <name>':- • Claude Code:+ • Claude Code (computer-use compatibility mode — recommended):+ cua-driver mcp-config --client claude+ Copy-paste the printed command into your shell — it uses+ \`claude mcp add-json\` so the long flag survives PowerShell's+ arg parser. This grounds Claude Code's vision/computer-use-style+ flow on CuaDriver window screenshots — keeps the normal CuaDriver+ tools, changes only the screenshot tool.++ Plain Claude Code (no computer-use compat):claude mcp add --transport stdio cua-driver -- $BIN_LINK mcp- Claude Code computer-use compatibility mode:- claude mcp add --transport stdio cua-computer-use -- $BIN_LINK mcp --claude-code-computer-use-compat- Use this when you want Claude Code's vision/computer-use-style flow- to ground on CuaDriver window screenshots. It keeps the normal- CuaDriver tools and changes only the screenshot tool.- Use MCP for this path; CLI screenshots do not expose the- mcp__cua-computer-use__screenshot tool name cue.-• Codex (OpenAI):codex mcp add cua-driver -- $BIN_LINK mcpdiff --git a/libs/cua-driver/scripts/post-install-hints.txt b/libs/cua-driver/scripts/post-install-hints.txtindex 71517c5f45..4ea16018f2 100644--- a/libs/cua-driver/scripts/post-install-hints.txt+++ b/libs/cua-driver/scripts/post-install-hints.txt@@ -14,10 +14,13 @@ Next steps:available via '{{BINARY}} mcp-config --client <name>':• Claude Code (computer-use compatibility mode):- claude mcp add --transport stdio cua-computer-use -- {{BINARY}} mcp --claude-code-computer-use-compat- This grounds Claude Code's vision/computer-use-style flow on- CuaDriver window screenshots. It keeps the normal CuaDriver tools- and changes only the screenshot tool.+ {{BINARY}} mcp-config --client claude+ Copy-paste the printed command into your shell — it uses+ `claude mcp add-json` (not bare `--`) so the long flag travels+ through PowerShell's arg parser intact. This mode grounds Claude+ Code's vision/computer-use-style flow on CuaDriver window+ screenshots — it keeps the normal CuaDriver tools and changes+ only the screenshot tool.• Codex (OpenAI):codex mcp add cua-driver -- {{BINARY}} mcp