Adds the optional --message flag (custom failure message) to the assert
command docs for ios, android, web, computer, and harmony automation
skills, matching the CLI/MCP support added in web-infra-dev/midscene#2604
(issue #2351).
Add an "Improve Precision (Deep Locate / Deep Think)" section to the five
device skills (browser, android, ios, computer, harmony) so agents know how
to recover from location drift / offset and improve act planning.
These global CLI flags are now supported by the device CLIs (and MCP) — see
web-infra-dev/midscene#2446. Deep locate requires a visual-language model.
The previous "bridge precheck" curl claimed to check whether the
extension was listening on 127.0.0.1:3766. That's the wrong direction:
in bridge mode the CLI starts the server on 3766, and the extension is
the client that connects in. The check therefore always failed before
the CLI was started and gave a false negative for a perfectly working
setup.
- Remove the bridge precheck from the precheck section and explain why
bridge has no usable precheck, plus what log lines to watch instead.
- Document the CLI-as-server handshake direction in the Bridge mode
important notes, including what the "Listening" indicator actually
means in the extension UI.
- Add the active-tab caveat: chrome://, chrome-extension://, and the
Chrome Web Store cannot be operated by the extension and surface as
"Cannot access a chrome:// URL".
- Clarify connect/connect --url behavior in bridge mode (operates on
current tab, does not open a new tab).
- Broaden the "Chrome" wording to "Chrome or any Chromium-based browser
that supports Chrome extensions (Edge, Arc, Dia, ...)".
The CLI shape that lands in @midscene/*@1.9.0 was reshaped from a
single `--images JSON` flag into paired `--image` / `--image-name`
flags so agents don't need to assemble JSON in their shells (see
web-infra-dev/midscene#2523). Update the assert examples in each
platform SKILL.md (android / ios / harmony / browser / computer) to
the released flag shape and add a multi-image example showing how
repeated `--image` and `--image-name` pair by position.
The version pin is unchanged — the API redesign rides on the same
unreleased 1.9.0 cut as the original `--images` work.
The platform CLIs (@midscene/android, @midscene/ios, @midscene/harmony,
@midscene/web, @midscene/computer) gained multimodal `--images` and
`--convertHttpImage2Base64` flags on the `assert` subcommand. Add a short
example block to each platform SKILL.md right after the basic
`assert --prompt` examples, mirroring the existing `tap --locate` image
guidance. Each example notes the @1.9.0+ version requirement so agents
following the skill against older releases get a clear pointer instead
of a silent "Unknown option" failure.
The vitest-midscene-e2e skill is left untouched because it explicitly
funnels users through `aiAct` rather than `aiAssert`.
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.
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.
Instead of immediately falling back to Puppeteer mode when both CDP and
Bridge prechecks fail, try opening Chrome first using a platform-appropriate
shell command, wait briefly, then re-run the precheck before falling back.
Leyang