Skip to content

docs(cua-driver-rs): mark screenshot tool as removed-on-all-platforms in PARITY.md - #1920

Draft
f-trycua wants to merge 1 commit into
mainfrom
docs/screenshot-tool-removed-parity
Draft

docs(cua-driver-rs): mark screenshot tool as removed-on-all-platforms in PARITY.md#1920
f-trycua wants to merge 1 commit into
mainfrom
docs/screenshot-tool-removed-parity

Conversation

@f-trycua

Copy link
Copy Markdown
Collaborator

Summary

Docs-only fix. The standalone screenshot MCP tool was intentionally removed from all three Rust platforms (macOS, Windows, Linux), but PARITY.md was never updated — so it still read as though screenshot was a registered, "VERIFIED" tool. That stale doc made Linux look like it had a screenshot-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

The Linux registry already documents this in-code (crates/platform-linux/src/tools/impl_.rs build_registry: "screenshot removed - see the matching comment in platform-windows... Canonical screenshot path is get_window_state with capture_mode:\"vision\""), and Windows has the matching comment. The underlying capture fns (screenshot_window_bytes, screenshot_display_bytes, wayland screenshot_dispatch) still exist because get_window_state / zoom use them internally.

Changes (PARITY.md)

  • Rewrote the ## MCP tool: screenshot section to document the removal, the canonical replacement (get_window_state capture_mode:"vision" + zoom), and kept the old "VERIFIED" Windows behavior as a historical note.
  • Dropped screenshot from the list-tools roster and the example list-tools output.
  • Removed the misleading call screenshot (no window_id) → ✅ full-display default row 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: screenshot is not a standalone tool on Linux; capture is via get_window_state (which embeds a screenshot) and zoom.

Non-goals

No code or tool-registration changes. Specifically not adding a screenshot tool 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

… 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>
@vercel

vercel Bot commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated (UTC)
docs Ignored Ignored Jun 17, 2026 8:38pm

Request Review

@coderabbitai

coderabbitai Bot commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 9a2d9aec-4014-4684-9d93-078a9b3fba7a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/screenshot-tool-removed-parity

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions

Copy link
Copy Markdown
Contributor

Linux visual regression artifacts

Matrix jobs now run independently. Download visual artifacts from this workflow run.
Each background-GUI job uploads a .gif of the interaction plus two annotated PNGs (<app>.png raw, <app>-atspi.png with AT-SPI element boxes); the cua-driver-linux-som-overlays artifact adds <app>-som.png cua Set-of-Marks overlays:

  • cua-driver-linux-cursor-click-gif
  • cua-driver-linux-background-terminal-gif
  • cua-driver-linux-parallel-drag-xserver
  • cua-driver-linux-background-gui-chromium
  • cua-driver-linux-background-gui-tk
  • cua-driver-linux-background-gui-gtk3-gedit
  • cua-driver-linux-background-gui-gtk3-mousepad
  • cua-driver-linux-background-gui-gtk3-scite
  • cua-driver-linux-background-gui-gtk4-characters
  • cua-driver-linux-background-gui-qt5-manuskript
  • cua-driver-linux-background-gui-qt5-klog
  • cua-driver-linux-background-gui-qt5-openambit
  • cua-driver-linux-background-gui-qt6-kate
  • cua-driver-linux-background-gui-qt6-kcalc
  • cua-driver-linux-background-gui-qt6-okular
  • cua-driver-linux-background-gui-qt6-qownnotes
  • cua-driver-linux-background-gui-electron-zettlr
  • cua-driver-linux-background-gui-electron-joplin
  • cua-driver-linux-background-gui-electron-logseq
  • cua-driver-linux-som-overlays

Open workflow run and download artifacts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant