packages/mobile-mcp/.vendored-patches.md
Vendored from: c5d7d27fd (upstream v0.0.61, main branch)
Upstream sync mechanism: git subtree pull (see scripts/sync-from-upstream.sh).
| Patch | Description | Touches |
|---|---|---|
| Rename to @qwen-code/mobile-mcp | npm package name, repository field | package.json |
| Disable upstream telemetry | Fork doesn't phone home to upstream PostHog | src/server.ts |
| Relative coordinate shim | Opt-in 0–1000 normalized coordinates (env MOBILE_MCP_COORDINATE_SPACE) | src/coord-norm.ts, src/server.ts |
| InstallOptions + Android tools | Extended installApp with options; added dumpUiHierarchy, pullFile, pushFile; MCP tools mobile_ui_dump, mobile_adb_pull, mobile_adb_push | src/robot.ts, src/android.ts, src/server.ts |
| getAndroidRobotFromDevice helper | DRY extraction for Android-only tool device validation | src/server.ts |
After git subtree pull, expect conflicts in src/server.ts (our coord hooks + new tools)
and package.json (name/repo). The coord shim (src/coord-norm.ts) is a new file and
won't conflict. Backend files (android.ts, ios.ts, etc.) are only touched for the
InstallOptions signature change — low conflict surface.