mobridge-mcp 0.12.2 → 0.12.4

package/integrity.json

@@ -1,4 +1,4 @@
 {
-  "buildId": "b704084-20261111144850",
-  "bundleSha256": "18462deb2ccc5e554561c36e95c56306e321fb113d2fce01e61e897b260a4665"
+  "buildId": "ec1ab2c-20261112032752",
+  "bundleSha256": "205f5846c6e89a5a03b6e5cd73b062a0ec11ee0f44d0a4341edb59013b724bf0"
 }

package/loader.cjs

@@ -14,7 +14,7 @@ const os = require("node:os");
 const path = require("node:path");
 const crypto = require("node:crypto");
 
-const BUILD_ID = "b704084-20261111144850"; // pack-npx stamps the real build id
+const BUILD_ID = "ec1ab2c-20261112032752"; // pack-npx stamps the real build id
 const ROOT = __dirname; // package root (loader.cjs sits here)
 const DIST = path.join(ROOT, "dist");
 const BUNDLE = path.join(DIST, "main.obf.cjs");
@@ -62,6 +62,18 @@ function cachedJscPath() {
   return { dir, file: path.join(dir, "main.jsc") };
 }
 
+// Each release compiles an ~8 MB .jsc into its own directory; nothing removed the older ones. Runs only right after a fresh compile.
+function pruneStaleBytecode(keepDir) {
+  try {
+    const parent = path.dirname(keepDir);
+    for (const name of fs.readdirSync(parent)) {
+      const dir = path.join(parent, name);
+      // A day of grace: another installed version used in parallel keeps its cache instead of the two deleting each other's.
+      if (dir !== keepDir && Date.now() - fs.statSync(dir).mtimeMs > 86_400_000) fs.rmSync(dir, { recursive: true, force: true });
+    }
+  } catch { /* best effort: a stale cache is only wasted disk */ }
+}
+
 function loadViaBytecode() {
   let bytenode;
   try { bytenode = require("bytenode"); } catch { return false; } // no bytenode -> fallback JS
@@ -70,6 +82,7 @@ function loadViaBytecode() {
     if (!fs.existsSync(file)) {
       fs.mkdirSync(dir, { recursive: true });
       bytenode.compileFile({ filename: BUNDLE, output: file }); // compiled against the user's own Node
+      pruneStaleBytecode(dir);
     }
     injectNodePath();
     require(file);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mobridge-mcp",
-  "version": "0.12.2",
+  "version": "0.12.4",
   "description": "MoBridge MCP — a stdio MCP server exposing on-device Android UIs as fast semantic read / observe / find / act / verify tools plus screenshots. Ships an installer that wires it into Claude Code, Claude Desktop, Cursor and Codex.",
   "keywords": [
     "mcp",

package/skills/VERSIONS.json

@@ -1,7 +1,7 @@
 {
   "mobridge-adb": {
-    "version": "1.0.1",
-    "digest": "17d400b50d0f7f7f"
+    "version": "1.0.3",
+    "digest": "d0bc1031340fbf67"
   },
   "mobridge-app-control": {
     "version": "1.1.0",

package/skills/mobridge-adb/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: mobridge-adb
 description: Use when you would reach for adb - logs, files, intents, settings, keys, power, ports, shell - use MoBridge instead
-version: 1.0.1
+version: 1.0.3
 ---
 
 # MoBridge instead of adb
@@ -34,9 +34,10 @@ screen with `observe` instead.
 | You would run | Run this instead | Notes |
 |---|---|---|
 | `adb logcat -d` | `mobridge logcat --tag SuperAdsSDK:D --max-lines 200` | structured lines; `--grep`, `--level`, `--package`, `--since <cursor>` |
-| `adb logcat` (live) | `mobridge logcat --follow 20000` | keeps reading for 20 s; longer: `mobridge adb -- logcat` |
+| `adb logcat` (live) | `mobridge logcat --follow 20000` | keeps reading for 20 s; longer: `mobridge adb -- logcat`; output over 2 MB stops with `OUTPUT_TOO_LARGE`, so filter or use `--max-lines` |
 | `adb logcat -c` | `mobridge logcat --clear` | |
 | `adb push / pull` | `mobridge file push ./a.txt /sdcard/Download/a.txt` / `mobridge file pull /sdcard/Download/a.txt --out ./a.txt` | single files verified by SHA-256 |
+| `adb push` big file, flaky cable | `mobridge file push ./big.bin /sdcard/Download/big.bin --resume --progress` | up to 4 GB; if interrupted, run the same command again: the kept part is verified by hash and only the rest is sent |
 | `adb push -r dir` | `mobridge file push ./dir /sdcard/Download/dir --recursive` | verified by names and sizes |
 | `adb shell ls / stat / rm` | `mobridge file ls /sdcard/Download`, `file stat <p>`, `file rm <p> [--recursive]` | |
 | `adb shell run-as pkg cat` | `mobridge file pull <p> --run-as <pkg>` | debuggable apps only |
@@ -50,7 +51,8 @@ screen with `observe` instead.
 | wake, sleep, rotate, stay awake, reboot | `mobridge device wake`, `device rotate 1`, `device stay-awake true`, `device reboot` | rotate and stay-awake persist |
 | `adb tcpip`, `adb usb`, `wait-for-device` | `mobridge device tcpip --port 5555`, `device usb`, `device wait` | |
 | `adb forward / reverse` | `mobridge forward add tcp:9000 tcp:8080`, `forward list`, `forward remove tcp:9000` | remove only touches mappings made here |
-| `adb shell <anything>` | `mobridge shell <command>` | raw; exit code, stdout and stderr come back |
+| `adb shell <anything>` | `mobridge shell <command>` | raw; exit code, stdout and stderr come back; `--raw` prints only the command's own stdout/stderr and exits with its code |
+| poll until text shows / is gone | `mobridge wait --text "Done" [--gone] --timeout 8000`, `wait --window-class Launcher` | `--match CONTAINS`; no sleep loops |
 | `adb <anything>` | `mobridge adb -- <args>` | flags after `--` go to adb untouched |
 | foreground activity (`dumpsys activity`) | `mobridge observe` or `capture`: the result has the app and activity | no adb call needed |
 
@@ -72,6 +74,9 @@ Reference with every flag and result field: `references/commands.md`.
 - `rotate` and `stay-awake` also persist: undo them (`device rotate auto`, `device stay-awake false`).
 - Tapping an ad or a WebView has no node to click: use `mobridge gesture '{"kind":"TAP","x":540,"y":1200}'` with coordinates from a fresh `capture` (old coordinates go stale quickly). Never tap the ad itself; follow `mobridge-surfaces`.
 - When a step only needs "sent" (a second BACK, a tap whose effect you read later), say so: `mobridge key BACK --verify DISPATCH_ONLY` returns in ~200 ms instead of ~740 ms; in a plan add `"verify":"DISPATCH_ONLY"`.
+- `adb push` inside `mobridge shell` fails like real adb (it is a client command): use `mobridge file push` (verified, no size limit worry) or `mobridge adb -- push`. A big push does not block `observe`/`capture`.
+- A bare serial works for `-d` (`-d R58M...`); with several devices `disconnect` needs `-d <id>` or `--all`.
+- Ad windows: `observe` may return `closeTarget {x,y,label}` when the SDK exposes one labelled Close/Skip node; act on it with `screen act at --capture <id> --x --y`. No `closeTarget` means look at a `capture`.
 - Quote the whole command when it holds `|`, `;` or `>`: `mobridge shell -d <id> -- "ls /sdcard | head"`. Put `-d`, `--json` and `--timeout` before `--`: everything after it goes to the phone untouched.
 
 ## Over MCP