# AutoJs6: a maintained fork of Auto.js for Android accessibility automation

> AutoJs6 continues the abandoned Auto.js project, running JavaScript on Android through the accessibility service. It is a solid fit for device-side scripting, and a poor fit for anyone expecting a documented, versioned API surface.

**SuperMonster003/AutoJs6** — 安卓平台 JavaScript 自动化工具 (Auto.js 二次开发项目)

- Repository: https://github.com/SuperMonster003/AutoJs6
- Website: https://docs.autojs6.com
- Stars: 6,424 · Forks: 1,778
- Language: Java
- License: MPL-2.0
- Published: 2026-09-22 · Updated: 2026-09-22 · Language: en
- Canonical page: https://hysenlabs.com/projects/supermonster003-autojs6

## What AutoJs6 replaces, and who it is actually for

Auto.js was first published by hyb1996 on 2017/01/27 and stopped being maintained on 2020/03/13, with its last version named 4.1.1 Alpha2 and build number 461. AutoJs6 is a second-development fork of that final codebase, started on 2021/12/01, and it stays open source and free. So the problem it solves is narrow and concrete: the original Android accessibility automation tool went dark, and someone kept it alive.

The audience follows from that. If you write JavaScript that taps, swipes and reads the screen of an Android device through the accessibility service, AutoJs6 is the continuation of the tool you already know. The README also lists sibling efforts with their own timelines: Auto.js M by TonyJiangWJ, started 2019/11/21 and still listed without an end date, and AutoX by kkevsekk1, started 2020/07/24 and ended on 2025/01/07. The README's own table, not any external survey, is the source for those dates. Anyone choosing between them is choosing between separate maintainers, not between feature checklists.

## Rhino, the accessibility service, and where the JavaScript runs

The stack is visible from the repository layout and the README badges. The primary language is Java, the script engine is Mozilla Rhino pinned at 2.0.0-SNAPSHOT, and the build is Gradle based: build.gradle.kts, settings.gradle.kts, gradle.properties, gradlew, plus build-logic/, app/, libs/, modules/ and plugin-api/ at the top level. There is a version.properties file, which is where a Gradle build of this shape usually keeps the version string.

The data flow is the part worth understanding before you write anything. Your script is JavaScript, interpreted by Rhino inside the app process. The app holds an Android accessibility service, which is the mechanism that lets it observe the UI tree of other apps and dispatch gestures. Nothing in the README describes a remote control channel or a desktop-side runtime; the script and the device are the same machine. That has a direct consequence for how you debug: there is no out-of-process stepping story documented in the README, so you work from the device.

The plugin-api/ directory is the interesting architectural signal. It implies an extension boundary for adding capability without forking the whole app, though the README does not document what a plugin may and may not touch. Treat that directory as a real surface whose contract you will have to read from source.

## Building AutoJs6 from source with Gradle

The README does not give a step-by-step install guide, and there is no published package to install. What it does give is the toolchain: Android Studio 2023.3 or newer, or IntelliJ IDEA 2023.3 or newer, and the repository ships a Gradle wrapper. So the honest first step is to clone the repository and let the wrapper resolve the build.

```bash
git clone https://github.com/SuperMonster003/AutoJs6.git
cd AutoJs6
./gradlew
```

On Windows the wrapper is gradlew.bat instead. Once the wrapper has resolved the build, open the project in Android Studio or IntelliJ IDEA and build the app module, then sideload the resulting APK to your test device. Before you run anything, open the app, enable its accessibility service in Android settings, and only then start a script.

The README does not print a canonical script example, so the first thing to verify is simply that the app launches, the accessibility service is enabled, and the editor accepts a script. The README does not document the scripting API, so check the docs site at docs.autojs6.com before assuming any method name.

## The README will not tell you how to package or roll back

Two gaps stand out. First, packaging: people search for how to package AutoJs6 scripts into a standalone APK, and the README does not cover it. The repository has app/ and modules/ and plugin-api/, which suggests the machinery exists, but the README does not document the path from a working script to a distributable artifact.

Second, rollback. The README does not document how to revert to a previous release or what happens to existing scripts when you upgrade. The release history shows the gap in practice: v6.6.3 landed on 2025-05-26, v6.6.4 on 2025-05-30, and then v6.7.0 on 2026-03-14, roughly nine months later. A jump like that is normal for a project maintained by one person, but it means you should pin the APK version you validated rather than assume the next release is drop-in. Nothing in the README states a compatibility policy, so do not assume one.

A third limitation is structural. The accessibility service is the whole mechanism, and Android has been tightening background execution and accessibility reporting for years. The README does not document which Android versions are supported or tested, so a script that works on one device image may fail on another for reasons that have nothing to do with your code.

## AutoJs6 against Auto.js M and AutoX

The README's own project table makes the comparison concrete. AutoX, by kkevsekk1, began 2020/07/24 and is listed with an end date of 2025/01/07, so it is no longer being developed. Auto.js M, by TonyJiangWJ, began 2019/11/21 and carries no end date in the table. AutoJs6 began 2021/12/01 and its last push was on 2026-03-16, with v6.7.0 released on 2026-03-14.

The difference in approach is lineage and engine. AutoJs6 is a fork of hyb1996's final Auto.js codebase, which is why the README frames it as second development rather than a rewrite. It uses Rhino 2.0.0-SNAPSHOT as the JavaScript engine. If you have an existing Auto.js script, that lineage is the reason it is likely to run. If you are starting fresh and want a project with more than one active maintainer, none of these three is that project, and the README does not claim otherwise.

## Licence, maintenance cost, and what a fork obliges you to check

AutoJs6 is MPL-2.0. The practical implication of a file-level copyleft licence like this one is that modifications to covered files carry obligations when you distribute, while you can combine them with differently licensed code in separate files. That is a description of the licence family, not legal advice; if you plan to ship a modified build, read the LICENSE file in the repository and get your own answer.

Maintenance cost is the harder question. The last push was on 2026-03-16, which is more than six months before today, so this is not a project you can describe as continuously updated. The release cadence supports the same reading: three releases across roughly ten months. Budget for the possibility that a fix you need arrives on the maintainer's schedule, and keep the Gradle toolchain pinned, since the README specifies Android Studio 2023.3+ and IntelliJ IDEA 2023.3+, and a newer IDE may or may not build the same tree without changes.

## Conclusion

Adopt AutoJs6 if you need to drive Android UI from JavaScript on a device you control, and you accept reading the source or the docs site when the README stops short. Do not adopt it if you need a stable, versioned API contract or a documented rollback path, because the README does not provide either. Before committing, verify that your target Android version is covered by the current release and that the accessibility service behaves on your device model, since the README documents neither.

## FAQ

### Is AutoJs6 the same as the original Auto.js?

No. Auto.js was published by hyb1996 on 2017/01/27 and stopped being maintained on 2020/03/13 at version 4.1.1 Alpha2. AutoJs6 is a second-development fork of that final codebase, started on 2021/12/01, and it remains open source and free.

### How do I install AutoJs6?

The README does not give install steps and there is no package to install. It lists Android Studio 2023.3+ or IntelliJ IDEA 2023.3+ as the toolchain, and the repository ships a Gradle wrapper, so you build the app from source and sideload it.

### What JavaScript engine does AutoJs6 use?

The README badges Rhino at 2.0.0-SNAPSHOT. Your script runs as JavaScript interpreted by Rhino inside the app process on the device, alongside the Android accessibility service that observes the UI and dispatches gestures.

## Sources

- [License: MPL-2.0](https://github.com/SuperMonster003/AutoJs6/blob/master/LICENSE)
- [Project website](https://docs.autojs6.com)
- [README](https://github.com/SuperMonster003/AutoJs6/blob/master/README.md)
- [Releases](https://github.com/SuperMonster003/AutoJs6/releases)
- [SuperMonster003/AutoJs6 on GitHub](https://github.com/SuperMonster003/AutoJs6)

---

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