# MonsterNone/tmall-miao: a desktop-driven 618 task runner for Android and HarmonyOS phones

> The project automates Taobao 618 coin and red-packet tasks by driving a connected phone from a Windows, Mac or Linux computer over ADB or HDC. It is a seasonal tool with a narrow window, an unfinished JD feature list, and no declared licence.

**MonsterNone/tmall-miao** — 喵币助手：618天猫（淘宝）、京东任务一键完成。电脑版，支持Android和HarmonyOS Next

- Repository: https://github.com/MonsterNone/tmall-miao
- Stars: 4,025 · Forks: 485
- Language: Python
- License: not declared
- Published: 2026-09-28 · Updated: 2026-09-28 · Language: en
- Canonical page: https://hysenlabs.com/projects/monsternone-tmall-miao

## What the 618 task runner actually automates, and for whom

Taobao's 618 campaign hands out 淘金币 and red-packet energy through a stack of small in-app tasks: daily check-ins, browsing rounds, share prompts. Doing them by hand on one phone takes minutes a day for weeks. MonsterNone/tmall-miao is a Python program that sits on a desktop, talks to a phone over USB or wireless debugging, and walks those screens for you.

The intended user is not a general consumer. The README lists Python 3.8+, a debug bridge (HDC for HarmonyOS, ADB for Android), the matching automation library, and developer mode enabled on the handset. That is a developer or power-user setup. The project also points at a companion site, tasku.top, described as a 淘宝淘金币互助网站, so the audience is people already coordinating 618 coin tasks with others.

The scope is deliberately narrow and seasonal. The 2026 618 checklist marks 淘宝淘金币任务 and 淘宝红包能量任务 as supported, and leaves 京东推红包任务 and 京东红包打卡任务 unchecked. Despite the repository name, the shipped work is Taobao-side.

## How the phone gets driven: uiautomator2, hmdriver2 and a runtime device choice

There is no server and no cloud component. main.py runs on the computer, asks which device family you are on, and then hands control to one of two automation libraries pinned in requirements.txt: hmdriver2~=1.4.4 for HarmonyOS and uiautomator2~=3.5.0 for Android. The README frames this as 运行时设备类型选择, a runtime selection rather than two separate builds.

Both libraries work the same way in principle: an agent runs on the phone, the desktop side sends UI queries and touch or text commands over the debug channel, and the script reacts to whatever the app renders. That is why the prerequisites are a debug bridge and developer mode rather than an API key. It also explains the note at the top of the README that the older AutoJS version was retired because it was too easy to detect. Moving the logic off the phone changes what the automation looks like to the app, though the README does not claim the current approach is undetectable.

The repository layout is small: main.py, a modules/ directory, build.spec, version.json, requirements.txt. The README does not document the internal module boundaries, so treat modules/ as the place task logic lives rather than as a published interface.

## Installing the 618 task runner and running your first pass

The README gives two paths. The packaged route is Windows X64 only: download from Releases and run it from cmd or by double-clicking, with adb and hdc already bundled. The source route is the one documented in detail, and it is what follows.

Start by installing Python. The README recommends 3.10 and links the 3.10.11 installer. Then install both automation libraries at once, since the device type is chosen at runtime:

```bash
pip3 install -r requirements.txt
```

For an Android handset, the README adds a separate device-side initialization step after ADB is installed and on PATH:

```bash
python -m uiautomator2 init
```

HarmonyOS users install HDC and configure its environment variable instead, following Huawei's guide. Either way the phone needs developer mode. On Android that means tapping 版本号 seven times, then enabling USB debugging; on HarmonyOS, tapping 软件版本 five times and enabling USB or wireless debugging after a restart.

Confirm the computer can see the device before touching the script. Android:

```bash
adb devices
```

HarmonyOS:

```bash
hdc list targets
```

For a wireless HarmonyOS connection the README gives `hdc tconn 手机无线调试显示的ip:端口号`. Then run the entry point:

```bash
python main.py
```

The script prompts for 鸿蒙 or 安卓, and proceeds once you pick. Expect the phone screen to start moving on its own; the README advises running it manually because the project is still described as 开发调试中, with a one-click installer only listed as a future possibility.

## Where this breaks: unfinished JD tasks, desktop dependence and a missing licence

The most concrete limitation is the feature list. Two of the four 2026 618 items are unchecked: 京东推红包任务 and 京东红包打卡任务. If your workload is JD rather than Taobao, the repository name will mislead you. The README also does not document rollback, retry behaviour, or what happens when a task screen changes mid-run.

The second constraint is architectural. The README states plainly that a computer (Win/Mac) is required to run it, 由于系统特性. There is no phone-only mode. That rules out anyone who wants to run this on the handset itself, which is exactly what the discontinued AutoJS version did.

Third, the licence is not declared. The repository metadata shows no license file and no SPDX identifier. For a tool that you might hand to a colleague or bundle into an internal image, that is a real gap: you cannot tell what redistribution is permitted. Treat that as an open question for whoever owns compliance on your side, not as a detail to skip.

Finally, the project is seasonal by design. The last push was on 2026-06-04, matching the 20260618-G release. Between campaigns there is little reason for activity, and the README's own warning that it is still being debugged means you should not assume a stable interface across releases.

## How it differs from Appium and from the retired AutoJS approach

The closest general-purpose alternative is Appium, which also drives a phone from a host machine over a debug bridge. The difference is scope and packaging. Appium is a test framework: you write your own test suite, manage drivers and capabilities, and maintain the page objects. MonsterNone/tmall-miao ships the task logic already written and asks only for a device type at startup. If you need to automate something other than 618 coin tasks, Appium is the right layer; if you want the 618 tasks and nothing else, the prebuilt logic is the whole point.

The other comparison is internal to the project. The README says the AutoJS version was stopped because it was too easy to detect, and the current design moves execution to the desktop. That is a meaningful change in approach: on-device scripting runs inside the same environment as the app, while a host-side driver issues commands through the debug channel. The README does not state that the new approach avoids detection, only that the old one was abandoned for that reason, so read the change as a response to a problem rather than a solved one.

## Maintenance, upgrade cost and what the missing licence means

Activity tracks the campaign calendar. The last push was on 2026-06-04, and the three recent releases (20260618-E, -F, -G) all landed within a week of each other in late May and early June 2026. That pattern suggests bursts of fixes during the 618 window rather than steady development. Plan for the tool to be quiet for months and then to need attention when Taobao changes its task screens.

Upgrades are cheap on the source route: pull the repository, reinstall requirements.txt, and check version.json against the release you are running. The pinned ranges (hmdriver2~=1.4.4, uiautomator2~=3.5.0) mean a fresh install can pick up newer patch versions, so a working setup can break after an unrelated pip run. If you need reproducibility, pin the exact versions in your own environment.

On licensing: the repository shows no declared licence. That is not a legal opinion, and it is not something this article can resolve. It is simply a fact you should confirm before redistributing the tool or shipping it inside anything you hand to other people.

## Conclusion

Adopt it if you already run a Windows or Mac machine next to a phone, you are comfortable with adb devices and hdc list targets, and you only need the two Taobao task families listed as done. Skip it if you wanted the JD push-red-packet or check-in tasks, if you need a phone-only workflow (the README states a computer is required), or if you cannot accept an undeclared licence in your tooling. Before running anything, check that HMDriver2 and uiautomator2 are the versions pinned in requirements.txt, that your device appears in adb devices or hdc list targets, and that the release you downloaded matches the version.json in the repository you cloned.

## FAQ

### Does MonsterNone/tmall-miao run on Windows, macOS or Linux?

The README says a computer (Win/Mac) is required because of system characteristics, and the packaged one-click build is listed as Windows X64 only. The source route runs Python 3.8+ with the debug bridge and automation libraries installed, so the operating system matters less than having ADB or HDC available on PATH.

### Which tasks does MonsterNone/tmall-miao support in the 2026 618 campaign?

The 2026 618 checklist marks 淘宝淘金币任务 and 淘宝红包能量任务 as supported. 京东推红包任务 and 京东红包打卡任务 are listed but unchecked, so the JD-side work is not done.

### What do I need installed before running MonsterNone/tmall-miao?

Python 3.8+ (3.10 is recommended), the two libraries in requirements.txt (hmdriver2 and uiautomator2), and either HDC for HarmonyOS or ADB for Android, with developer mode and USB or wireless debugging enabled on the phone. Android users also run python -m uiautomator2 init once.

### Is MonsterNone/tmall-miao still being developed?

The last push was on 2026-06-04, matching the 20260618-G release. The README describes the project as still being debugged and says a one-click installer may come later, so treat releases as campaign-driven rather than continuous.

## Sources

- [Issues](https://github.com/MonsterNone/tmall-miao/issues)
- [MonsterNone/tmall-miao on GitHub](https://github.com/MonsterNone/tmall-miao)
- [README](https://github.com/MonsterNone/tmall-miao/blob/next/README.md)
- [Releases](https://github.com/MonsterNone/tmall-miao/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/monsternone-tmall-miao