docs(cua-driver-rs): mark screenshot tool as removed-on-all-platforms in PARITY.md - #1920
docs(cua-driver-rs): mark screenshot tool as removed-on-all-platforms in PARITY.md#1920f-trycua wants to merge 1 commit into
Conversation
… in PARITY.md The standalone `screenshot` MCP tool was intentionally removed from all three Rust platforms (macOS, Windows, Linux): PR #1692 removed the registration in favor of `get_window_state` (`capture_mode:"vision"`) as the single canonical full-frame screenshot path (with `zoom` for region captures), and PR #1694 deleted the dead ScreenshotTool/ScreenshotCompatTool structs. PARITY.md was never updated and still described a Windows-only ScreenshotTool as "VERIFIED", listed `screenshot` among the registered tools, and claimed a Rust full-display `call screenshot` default. That stale doc made Linux look like it had a screenshot-tool parity gap, when in fact `Unknown tool: screenshot` is the intended, parity-consistent behavior on every platform. - Rewrite the `screenshot` section to document the removal + canonical replacement, and keep the old behavior as a historical note. - Drop `screenshot` from the list-tools roster and the example output. - Remove the `call screenshot (no window_id)` row from the known-gaps table. - Fix the same stale claim in the Linux skill doc (LINUX.md): screenshot is not a standalone tool; capture is via get_window_state (which embeds a screenshot) and zoom. Docs-only; no code or tool-registration changes. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Linux visual regression artifactsMatrix jobs now run independently. Download visual artifacts from this workflow run.
|
Summary
Docs-only fix. The standalone
screenshotMCP tool was intentionally removed from all three Rust platforms (macOS, Windows, Linux), butPARITY.mdwas never updated — so it still read as thoughscreenshotwas a registered, "VERIFIED" tool. That stale doc made Linux look like it had ascreenshot-tool parity gap (cua-driver call screenshot '{}'→Unknown tool: screenshot), when in fact that response is the intended, parity-consistent behavior on every platform.The actual history
892edd47) removed thescreenshottool registration;get_window_statewithcapture_mode:"vision"became the single canonical full-frame screenshot path, andzoomcovers region captures.c4c84710) deleted the now-deadScreenshotTool/ScreenshotCompatToolstructs on macOS and Windows.The Linux registry already documents this in-code (
crates/platform-linux/src/tools/impl_.rsbuild_registry: "screenshotremoved - see the matching comment in platform-windows... Canonical screenshot path isget_window_statewithcapture_mode:\"vision\""), and Windows has the matching comment. The underlying capture fns (screenshot_window_bytes,screenshot_display_bytes, waylandscreenshot_dispatch) still exist becauseget_window_state/zoomuse them internally.Changes (PARITY.md)
## MCP tool: screenshotsection to document the removal, the canonical replacement (get_window_statecapture_mode:"vision"+zoom), and kept the old "VERIFIED" Windows behavior as a historical note.screenshotfrom the list-tools roster and the examplelist-toolsoutput.call screenshot (no window_id) → ✅ full-display defaultrow from the known-gaps table.Changes (Skills/cua-driver/LINUX.md)
The Linux skill doc carried the same stale claim (it's what misled a Linux test-campaign agent into filing a phantom "screenshot tool missing" gap). Fixed the three references:
screenshotis not a standalone tool on Linux; capture is viaget_window_state(which embeds a screenshot) andzoom.Non-goals
No code or tool-registration changes. Specifically not adding a
screenshottool to Linux — doing so would make Linux the only platform exposing it, the opposite of parity, and would contradict the deliberate #1692/#1694 decision.🤖 Generated with Claude Code