docs(computer): document RDP mode in computer-automation skill#29
Merged
Conversation
Add a dedicated "Connect via RDP" subsection that lists every RDP flag exposed by `@midscene/computer@1 connect` (host, port, username, password, domain, security-protocol, ignore-certificate, admin-session, desktop-width, desktop-height), shows a minimum example, and calls out mode-specific differences (displayId/list_displays semantics, helper binary, credential hygiene). Update the SKILL.md description and triggers so RDP/remote-desktop intents route to this skill.
yuyutaotao
approved these changes
May 13, 2026
After end-to-end CLI verification against a real RDP host, sharpen the RDP section to reflect what users actually hit: - Clarify `--desktop-width/--desktop-height` are requests, not guarantees; point at `listdisplays --host ...` to confirm the negotiated size. - Distinguish `list_displays` (platform tool, local-only) from `listdisplays` (action tool, RDP-aware), so users know which to call in RDP mode. - Document latency expectations per CLI invocation (~5 s cold start for non-AI commands; 8–20 s for `act`/`assert`/`tap --locate`). - Add connect-failure diagnostics: first stderr line is the actionable error (`connect_failed: ERRCONNECT_*`); enumerate common causes and fixes. - Remind callers that every subsequent CLI command must repeat the `--host/--username/--password` flags since each invocation is stateless.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
skills/computer-automation/SKILL.md, with a minimalconnect --host ...example and a complete option reference (--host,--port,--username,--password,--domain,--security-protocol,--ignore-certificate,--admin-session,--desktop-width,--desktop-height).--displayId/--headlessare ignored under RDP,computer_list_displayskeeps listing local displays, the helper binary requirement, and credential hygiene (use env vars, don't commit passwords).descriptionand triggers so phrases like "rdp", "remote desktop", "windows server", and "connect via rdp" route to this skill. Still inside the 1200-char budget (1017/1200 perscripts/check-skill-description-length.mjs).Why
@midscene/computernow exposes RDP flags throughconnect(see web-infra-dev/midscene#2466). Without a matching skill doc, agents would not know that RDP mode exists or how to opt in, so this PR is the user-facing half of that change.Test plan
node scripts/check-skill-description-length.mjs(all skills under limit, computer-automation at 1017/1200)