66 KiB
Languages
The current README.md supports the following languages:
- 简体中文 [zh-Hans]
- 繁體中文 (香港) [zh-Hant-HK]
- 繁體中文 (台灣) [zh-Hant-TW]
- English [en] # current
- Français [fr]
- Español [es]
- 日本語 [ja]
- 한국어 [ko]
- Русский [ru]
- العربية [ar]
Introduction
Auto.js is a JavaScript automation tool software for the Android platform that supports Accessibility Service.
Auto.js was first released by hyb1996 on 2017/01/27 and ceased maintenance on 2020/03/13, with the final version name being 4.1.1 Alpha2 and build number 461.
AutoJs6 is based on the final project of Auto.js, undergoing secondary development on 2021/12/01 and continues to be open-source and free.
The table below lists some Auto.js-related projects (sorted by development date):
| Project | App Name | Main Developers | Development Start Date | Development End Date | Active Maintenance (Year) |
|---|---|---|---|---|---|
| Auto.js | Auto.js | hyb1996 | 2017/01/27 |
2020/03/13 |
3.13 |
| Auto.js Pro 7 | Auto.js | hyb1996 | 2019/03/13 |
2019/07/08 |
0.32 |
| Auto.js Pro 8 | AutoJsPro | hyb1996 | 2019/10/13 |
2021/07/24 |
1.78 |
| Auto.js | Auto.js M | TonyJiangWJ | 2019/11/21 |
- | < 6.32 > |
| AutoX | Autox.js | kkevsekk1 | 2020/07/24 |
[ 2025/01/07 ] |
4.46 |
| Auto.js Pro 9 | AutoJsPro | hyb1996 | 2021/03/28 |
2023/02/09 |
1.87 |
| AutoJs6 | AutoJs6 | SuperMonster003 | 2021/12/01 |
- | < 4.28 > |
| autojs4 | Auto.js | blackcd318 | 2021/12/15 |
2023/07/31 |
1.62 |
| AutoX | Autox.js v6 | wilinz / aiselp | 2022/05/26 |
[ 2025/01/07 ] |
2.62 |
| openautojs | OpenAuto.js | openautojs | 2023/02/17 |
2023/04/16 |
0.16 |
| AutoJs4 | AutoJs4 | SuperMonster003 | 2023/04/11 |
- | < 2.93 > |
| AutoX | Autox.js v7 | aiselp | 2024/04/21 |
- | < 1.90 > |
| Autoxjs_v6_ozobi | Autox.js v6_ozobi | ozobiozobi | 2024/10/01 |
- | < 1.45 > |
| AutoX | Autox.js v6 | autox-community | 2025/03/30 |
- | < 0.96 > |
The dates in the table are estimated and may differ from actual dates.
Auto.js Pro 7/8/9 in the table are paid versions, and the rest are free open-source versions.
In the table, data in the Development End Date column that contains square brackets ([]) indicates that the open-source project is temporarily inaccessible.
In the table, data in the Active Maintenance column that contains angle brackets (<>) is calculated up to Mar 14, 2026.
Functions
- Can be used as a JavaScript IDE (code completion/variable renaming/code formatting)
- Supports automation based on Accessibility Service
- Supports floating button quick actions (script recording and running/view package name and activity/layout analysis)
- Supports Selector API and provides control traversal/information retrieval/control operations (similar to UiAutomator)
- Supports layout interface analysis (similar to Android Studio's LayoutInspector)
- Supports recording functionality and playback of recorded actions
- Supports screen capture/save screenshots/color search in images/image matching
- Supports E4X (ECMAScript for XML) for interface writing
- Supports packaging script files or projects into APK files
- Supports expanded functionality using Root privileges (screen click/slide/record/Shell)
- Supports use as a Tasker plugin
- Supports connection with VSCode for desktop development (requires AutoJs6-VSCode-Extension plugin)
Environment
Manual
- Application Documentation
- User Manual (to be written)
- Troubleshooting
- Project Compilation and Build
- Script Development Assistance
Major Changes
Compared to the final open-source version 4.1.1 Alpha2 of Auto.js, the main upgrades or changes in AutoJs6 are:
- Supports obtaining ADB privileges through Shizuku and using system API
- Supports building WebSocket instances to perform network requests based on the WebSocket protocol
- New modules [ base64 / crypto / sqlite / i18n / notice / ocr / opencc / qrcode / shizuku / ... ]
- Multilingual support [ Spanish / French / Russian / Arabic / Japanese / Korean / English / Simplified Chinese / Traditional Chinese / ... ]
- Theme color adaptation [ Grouping / Location / Search / History / Automatic Adaptation of Brightness and Contrast / ... ]
- Night mode adaptation [ Settings page / Documentation page / Layout analysis page / Floating window / ... ]
- VSCode plugin supports both client (LAN) and server (LAN/ADB) connection methods
- Rhino engine upgraded from v1.7.7.2 to v2.0.0-SNAPSHOT (Updated on Dec 25, 2025)
- Unicode code point escape support for supplementary plane characters
'\u{1D160}'; /* stands for "𝅘𝅥𝅮", traditional method: '\uD834\uDD60'. */ - Supports Object.values()
Object.values({name: 'Max', age: 4}); // ['max', 4] - Supports Array.prototype.includes()
[10, 20, NaN].includes(20); // true - Supports BigInt
typeof 567n === 'bigint'; // true - Supports template strings
`Lucky number: ${(Math.random() * 100).toFixed(0)}` - View more new features of the Rhino engine here
- View Rhino engine compatibility list
- Unicode code point escape support for supplementary plane characters
Release History
v6.7.0
2026/03/14
FeaturePlugin Center feature, supporting plugin install/uninstall/update and related operations (entry: home drawer button/home tab)FeatureVersion History feature, supporting viewing/restoring history versions of editable files (entry: home drawer button/file manager menu/code editor menu)FeatureTrash feature, supporting viewing/restoring deleted files/folders (entry: home drawer button)FeaturePaddle OCR (PP-OCRv5) plugin, for optical character recognitionFeaturecvt module, for data unit conversion (see Project Docs > Unit Conversion)Featurefmt module, for data formatting (see Project Docs > Formatting)Featurezip module, for file compression and extraction operations (Ref to Auto.js Pro) (see Project Docs > Zip)Featuremediainfo module, for viewing detailed information of media files (see Project Docs > Media Info)Featurecvt.bytes method, for byte data unit conversion (see Project Docs > Unit Conversion)Featurefmt.bytes method, for byte data formatting (see Project Docs > Formatting)Features13n.bytes method, for standardizing byte data (see Project Docs > Standardization)Featureapp.isDualInstalled method, for detecting whether a dual-installed app is installed (requires Shizuku or Root permission)issue #450Featuredevice.getSharedDeviceId method, for obtaining a unified shared device ID across appsissue #455Featuredevice.setPointerLocation and other Toggleable series methods, for setting or getting the pointer location system settingissue #381Featuredialogs.build method now supports textAllCaps/(positive/negative/neutral)TextAllCaps option parameters, for controlling whether button texts are all uppercaseFeatureimages.loadAsync method, for asynchronously fetching network image resourcesissue #327Featureui.getNavigationBarHeight method/navigationBarHeight property (getter), for getting navigation bar heightissue #456Featureui.getVisible(Status/Navigation)BarHeight method/visible(Status/Navigation)BarHeight property (getter), for quickly getting visible height of the status bar or navigation barissue #456Featurehttp.put/del(ete)/head methods, for sending network requests with different HTTP methodsFeaturehttp.getAsync/postAsync/requestAsync and related methods, for asynchronously sending network requestsissue #423Featurebody objects returned by http module request-related methods now include stream/saveToFile/close and related methodsissue #452Featurehttp module request-related methods now support cache control option parameters (cacheBody/bodyCacheThresholdBytes)Featurehttp module request-related methods now support insecure option parameters (isInsecure/insecure), for ignoring certificate-related exceptionsissue #417Featurehttp module request-related methods now support the options.client option, for configuring OkHttpClient.Builder (such as followRedirects)issue #454Featureauto.state property (getter) and shizuku.state property (getter), for obtaining accessibility service status and Shizuku service statusFeatureruntime.(set/is)JavaPrimitiveWrap methods, for setting or getting Java primitive wrapping strategyissue #435Featureautojs.(restart/exit) methods, for restarting or exiting the AutoJs6 app, and supporting automatic script execution on app restart with the specified argumentsissue #460FeatureUiObject#isShifted method, for detecting control position changesissue #469FeatureUiObject#snapshot method, for capturing the current state of a controlissue #469Featureengines.myEngine().getStartTime() method, for getting the script engine startup timestampissue #449Featurecrash global method, for testing the crash report pageFeaturestructuredClone global method, for deep-cloning JavaScript objects (see MDN)FeatureEquivalent series selectors (UiSelector#id/text/...) and contains series selectors (UiSelector#xxxContains) now support regular expression parametersFeatureRegular expression parameters of selectors now support flags (i, m, s, u)FeatureRegular expressions now support lookbehind assertion syntaxissue #464FeatureFile manager now includes "Move to" and "Copy to" menu items, supporting operation abort and progress status displayFeatureCode editor now includes the "Multi-function Keyboard" - "Symbol Settings" menu item, supporting symbol editing and symbol creation/import/export by profile levelFeatureHome drawer now includes the "Pointer Location" toolFeatureHome drawer now includes the "All Files Access" switchFeatureHome drawer now includes the "Show UI from Background" switch (for [Xiaomi/Vivo] devices)FeatureSettings page now includes the "Java Primitive Wrap" optionissue #435FeatureSettings page now includes the "Scheduled Task Engine" option, supporting AlarmManager/WorkManager/JobSchedulerissue #457issue #434issue #449issue #388issue #378issue #163issue #53issue #21FeatureSettings page now includes the "App Launcher Icon" option, supporting adaptive icons/transparent background iconsissue #405FeatureSettings page now includes the "Restart Strategy" option, for configuring whether the home drawer restart button uses the fast restart strategyFeatureSettings page now includes the "Screen Capture Permission Request Delay" option, for preventing the permission request window from blocking the screenFeatureLauncher shortcuts in the Settings page now include the "Plugins" option, for jumping to the Plugin Center page via a shortcutFeaturePackaged apps now support auto-start on boot, with a switch added on the configuration pageFeaturePackaged apps now support app shortcuts (log page/settings page)FeaturePackaged app configuration page now includes undo/redo/save buttonsFeaturePackaged app configuration page now includes a profile mechanism, supporting profile creation/modification/deletion/import/exportissue #483FeatureScrapers tool (run-scrapers.mjs), for automatically updating structured data in Gradle build scripts/common README data/README template data and moreFeatureGradle Wrapper switcher tool (gradle-wrapper-switcher), for switching local Gradle major versions (such as Gradle 8.x and Gradle 9.x)FixIncorrect parameter count and type restrictions for the notice methodissue #462FixIssue where the ui.R property (getter) could not be used properlyFixIssue where exceptions raised in ui.post callback parameters could fail silentlyFixIssue where global methods such as isJavaClass/isJavaPackage were invalidFixIssue where the timeout parameter of timers.keepAlive did not workFixIssue where floaty.window/rawWindow methods could not accept string parametersissue #467FixIssue where floaty.rawWindow could display some controls incorrectly due to an incorrect context being passedFixIssue where util.isString method was invalidFixIssue where util.class[Name]/getClass[Name] could return incorrect resultsFixIssue where util.java.array could not properly use type parameters such as BooleanFixIssue where objects returned by threads.disposable() could be unexpectedly boxed when accessing stored dataissue #435FixIssue where style options of the floating log window could not reset properly when console.build was called multiple timesFixIssue where (title/content)BackgroundColor options of console.build could override transparency or tint optionsissue #458FixIssue where console/toast and related methods could lose trailing zeros when displaying Java Double valuesFixIssue where console/toast and related methods could not display BigInt valuesFixIssue where the toast method could cause memory leaks due to holding a strong reference to the Toast instanceFixIssue where some global objects could lose JavaScript prototype properties and methodsFixIssue where the this object could point incorrectly when JavaScript expressions were used as attribute values in XML syntaxFixIssue where the linkify option parameter of dialogs.build did not workFixIssue where dialogs.build could break original data in object parametersFixIncorrect internal frame rate calculation in the setMaxFps method of the canvas element controlFixIncorrect width calculation when images.concat performed vertical concatenationFixIssue where canceling authorization in images.requestScreenCapture could crash the appFixIssue where screenshots obtained by images.captureScreen could have incorrect orientation or black border paddingissue #337FixIssue where 1 could be incorrectly parsed as a percentage when some images-related methods used region parametersFixIssue where the oneShot flag could fail when exceptions occurred in some images-related methodsissue #372FixIssue where some images-related methods could cause memory leaksissue #372FixIssue where images.save and ImageWrapper#saveTo could not properly write files when the input path did not existFixIssue where ImageWrapper#recycle failed to recycle image resourcesFixIssue where some overloaded ocr methods might not work properlyFixIssue where results obtained by ocr.detect might not match ocr.modeissue #468FixIssue where accessibility events registered by auto.registerEvent could be mistakenly cleared by other scriptsissue #466issue #343FixIssue where UiObject#child could throw ArrayIndexOutOfBoundsException on Android 10issue #416FixIssue where built-in module method calls could run into inconsistent Rhino context problemsFixIssue where creating a large number of floating windows in scripts could leave residual windows after script exitFixIssue where project.json configuration parameters might not be parsed properly when running a projectFixIssue where the excludedDirs parameter in project.json could cause configuration parsing failure during project packagingissue #428FixIssue where packaging might not work properly on Android 7.xFixIssue where original key names could be modified when saving script project configuration filesFixIssue where very large build version codes or build times in script project configuration files could crash the appFixIssue where frequent fetching or rebuilding of ImageReader could crash the app due to no available frame in the bufferFixIssue where the input event observer InputEventObserver could cause noticeable app startup lagFixIssue where Shizuku user service processes did not terminate properly and accumulatedissue #474FixIssue where packaged apps could not properly use Paddle OCR and Rapid OCR featuresFixIssue where key values in packaged app configuration file project.json could be modified unexpectedlyFixIssue where checkbox icons could flicker when scrolling the "Required Permissions" list on the packaged app configuration pageFixIssue where statistics on the Release History page could be displayed incompletely on some systems due to font differencesFixIssue where MLKit Google OCR could not initialize properly on some devices (tentative fix)issue #8FixIssue where file manager function buttons could not properly receive click events on some devices (tentative fix)issue #465FixIssue where blank lines in the code editor displayed box glyphs on some devices (tentative fix)FixIssue where the soft keyboard could block text content in the code editorFixIssue where code content could still be edited in read-only mode in the code editorFixIssue where tapping the title area or some menu items in read-only mode in the code editor could crash the appFixIssue where loading large files in the code editor could crash the app (tentative fix)FixAbnormal initialization of function button states when the code editor automatically opened a new fileFixIssue where putting the app in background while editing a file in the code editor could crash the appFixIssue where tapping the fx button in the code editor on Android 15+ could not show the quick panel for module functions (tentative fix)FixIssue where ErrorDialogActivity could fail to start properly or disappear automatically in a short timeissue #479issue #471issue #414issue #340FixIncorrect accepted parameter types for the Canvas constructorissue #402FixIssue where copying detailed information on the crash report page did not workFixIssue where custom back navigation logic stopped working on Android 16+, causing abnormal back behaviorFixIssue where the app could crash when pressing the back button or switching tabs after displaying file manager search resultsFixIssue where the UI did not refresh automatically after deleting project folders in the file managerFixIssue where the app could crash when task panel list items changed frequentlyFixIssue where navigation bar foreground color could behave abnormally with night mode when using "three-button" gesture navigationFixIssue where the APK file type information dialog might fail to obtain app name and SDK informationFixIssue where in client mode, disconnecting and reconnecting shortly after connecting could lead to handshake timeout and make reconnection difficultFixIssue where in client mode, actions such as screen rotation or language switching that recreated the Activity always caused AutoJs6 to reconnectFixIssue where in server mode, actions such as screen rotation or language switching that recreated the Activity caused the VSCode console to stop outputting logsissue #385FixIssue where connecting to the VSCode plugin in multiple ways at the same time could multiply the number of printed logsFixIssue where code generation on the layout analysis page could fail for collection controls (tentative fix)issue #328FixIssue where the "Use 'Volume Down' Key to Control Recording" switch on the Settings page did not workissue #480FixIssue where coordinate values in code files generated by script recording might not match actual screen pixel valuesissue #480FixIssue where the first recorded action (such as tap or swipe) in code files generated by script recording was always ignoredFixIssue where background file operations from the floating button "Run Script" dialog could crash the appFixIssue where the floating button state could reset when re-entering the home page after the home Activity lifecycle endedFixIssue where the Xiaomi device "Display over other apps" switch could jump to the wrong settings pageFixIssue where after aborting update download, network packets could still continue downloading in the background (tentative fix)FixIssue where the Rebuild Project task could not complete properly when isCleanup[Paddle/Rapid]Ocr option was enabled in build toolsImprovementPluginized Paddle OCR (PP-OCRv3) related featuresissue #334issue #331issue #325ImprovementEnhanced compatibility of runtime.loadJar method (by LYS86)pr #475ImprovementImproved compatibility of ui.getStatusBarHeight method/statusBarHeight property (getter) to a certain extentImprovementconsole.log and related methods now support displaying detailed information when printing global objects (images, app, ocr, etc.)Improvementdialogs.build method now supports native MaterialDialog.Builder option parametersImprovementdialogs.build method now supports loose string matching for animation/linkify option parametersImprovementImproved stability and consistency of screen orientation and width/height data obtained by device.rotation/rotation/width/height methodsImprovementImproved execution efficiency and compatibility of app.launchDual/startDualActivity and related methodsImprovementandroid.graphics.Paint#setColor now properly parses color parameters such as ColorInt/ColorHex/ColorNameImprovementException messages for argument types of built-in module-related methods now include type summary informationImprovementBuilt-in modules (dayjs/cheerio/dayjs/i18n) now use global lazy loading instead of script execution modeImprovementWhen printing huge data through console-related methods, some content is properly omitted according to upper limits to reduce print timeImprovementInitial countdown value of the console floating window increased from 6 seconds to 9 secondsImprovementInternal implementation of the console floating window is now lock-free and queue-based, improving parameter setting efficiency and success rateImprovementBackground color behavior-related APIs (alpha/tint/base color) of the console floating window now better align with Android design conventionsissue #458ImprovementOptimized menu collapse timing when tapping menu items after expanding the floating button in the file managerImprovementFile manager/task panel now supports showing file/task count statisticsImprovementWhen saving files fails in the code editor, they are automatically saved as drafts and support Save As to a new fileImprovementImproved smoothness to a certain extent when loading large files in the code editorImprovementCode editor "Find/Replace" now supports state persistence and real-time display of search count informationImprovementWhen prompting to save in the code editor, it now ensures saving succeeds before exiting the editor to reduce save failure rateImprovementState of the code editor save button now better matches user expectationsImprovementCode editor now supports long-press functionality for keys such as "-", "=", "(", "[", "{", "<"ImprovementPackaged app build process dialog now includes an "Abort" buttonImprovementImproved display behavior of the packaged app build process dialog and added elapsed time statisticsImprovementWhen installing packaged apps with new configuration, related configuration of the old app will be overwrittenImprovementPackaged app configuration page now checks required permissions by default (WAKE_LOCK/INTERNET/WRITE_EXTERNAL_STORAGE/...)issue #397ImprovementPackaged app configuration page now supports reading/configuring more options (show logs on launch/show splash screen on launch/splash slug text/...)ImprovementPackaged app settings page now includes a foreground service switchissue #406ImprovementKey name conflict detection added when saving script project configuration files to prevent ambiguous keysImprovementCrash report page now supports pinch-to-zoom font resizing and adds common function buttonsImprovementApp launcher icons now support adaptive icon featuresissue #405ImprovementRhino engine now falls back to raw reflection types when generic signature parsing fails, improving reflective method availability on lower Android versionsImprovementDivider lines added to switch-type items in the home drawer; tapping the title text area now shows detail dialogs and supports quick jump to system settings when neededImprovementWhen starting or restarting AutoJs6, tapping the title text area of "Client Mode" in the home drawer now supports aborting an ongoing connection attemptImprovementClient mode now supports connecting via IPv6 addresses and domain namesImprovementClient mode now supports detection prompts for special-purpose IPv4 addresses (loopback/broadcast/multicast/reserved/...)ImprovementClient mode now supports connection status display and management (correct address/abort connection)ImprovementServer mode now supports showing the number of connected clientsImprovementReading notification permission now supports automatic reconnect mechanism (requestRebind) to improve stability of notification-listening related featuresImprovementFloating button now improves safety when launching Activities from background to avoid app crashesImprovementFloating button "More" dialog now uses asynchronous data loading for smoother displayImprovementFloating button "Run Script" dialog now includes a "Home" menu itemImprovementFloating button "Run Script" dialog now supports minimization and state restoration, and does its best to keep the window resident or restore it automaticallyImprovementScript recording and playback now support Shizuku permission (playback smoothness may be somewhat affected)issue #320ImprovementTheme color settings page now uses a fast positioning method when locating theme colors to improve efficiencyImprovementReplaced deprecated LocalBroadcastManager with LiveData and SharedFlowImprovementGradle build scripts now improve extraction efficiency for 7z filesImprovementGradle build scripts now support obtaining detailed Android Studio IDE version (such as "2025.1.4.7")ImprovementGradle build scripts now support automatically generating data required by VersionCodesList class to reduce script startup delayImprovementUse Version Catalogs to centrally manage Gradle dependency and plugin versionsImprovementModularized Gradle build scripts, moved shared build logic into build-logic, and abstracted it as convention pluginsImprovementUse Gradle convention plugins to simplify loading logic of local AAR librariesImprovementRemoved the "android.enableJetifier=true" Gradle option to adapt to Gradle 9ImprovementUse Toolchain instead of sourceCompatibility/targetCompatibility to reduce build environment differencesImprovementSome dependency or local library version adjustmentsCHANGELOG.md
v6.6.4
2025/05/31
HintAPI change: ui.(status/navigation)BarAppearanceLight[By] -> ui.(status/navigation)BarIconLight[By]Featureutil.dpToPx/spToPx/pxToDp/pxToSp methods for pixel unit conversionFixSubtitles may be displayed incompletely when rotating the screen to landscape orientationFixSome page content may be obscured by the side navigation bar when rotating to landscapeFixIncomplete status bar background tint area on some pages in Android 15issue #398FixCode editor might write files with low-confidence encoding causing decoding errors (attempted fix)ImprovementImproved layout adaptability on the App and Developer pages and removed unnecessary layout categoriesImprovementREADME.md build section added multiple methods to help locate the target settings pageissue #404ImprovementSome dependency or local library version adjustmentsCHANGELOG.md
v6.6.3
2025/05/27
FeatureRelease history feature: view multi-language release changelogs and statisticsFeaturetimers.keepAlive method (now global) for keeping the script aliveFeatureEvent listeners such as engines.on('start/stop/error', callback) for global engine eventsFeatureimages.detectMultiColors method for multi-point color verificationissue #374Featureimages.matchFeatures / detectAndComputeFeatures methods: full-resolution image matching (Ref to Auto.js Pro)issue #366Featureimages.compressToBytes method to compress an image and generate a byte arrayFeatureimages.downsample method for pixel down-sampling and creating a new ImageWrapperFeatureui.keepScreenOn method to keep the device screen on while a UI page is focusedFeatureui.root property (getter) to obtain the "window content root container" node of the UI layoutFeaturewebview element now supports JsBridge-based web page layouts (Ref to Auto.js Pro) [see Sample Code > Layout > Interactive HTML / Vue2 + Vant (SFC)]issue #281FeatureLayout Inspector supports hiding controls (by TonyJiangWJ)pr #371issue #355FixOnline docs in the Home > Docs tab and Docs activity may be covered by the system navigation barFixClicking Toolbar buttons on some pages could accidentally trigger the title click eventFixBlank lines in the code editor showed box glyphs on some devices (tentative fix)FixColor-picker dialog in the theme-color settings page could stack infinitelyFixVolume-up key failed to stop all scripts when the accessibility service was disabledFixIME overlay issue when editing custom broadcast content in the Scheduled Tasks pageFixControls inside webview elements could not activate the soft keyboard properlyFixAPK file info dialog might fail to obtain app name and SDK infoFixFile-manager sample code might fail to auto-load child directory contents when entering a project folderFixTop content of UI mode on Android 15 was covered by the status barFixStatus-bar background color on some Android 15 pages could not follow the theme color dynamicallyFixdialogs module could not use the customView propertyissue #364FixExpression parameter of dialogs.input might not return the execution resultFixUsing JavaAdapter led to a ClassLoader stack overflowissue #376Fixconsole.setContentTextColor caused log text color to lose its default valueissue #346Fixconsole.setContentBackgroundColor could not accept color-name argumentsissue #384Fiximages.compress implementation corrected: now changes encoding quality instead of pixel down-samplingFiximages.resize method did not work properlyFixengines.all could trigger ConcurrentModificationExceptionissue #394FixIncorrect date formats in some languages within README.mdFixGradle build could fail due to invalid library archive lengthissue #389ImprovementAdded gradient separators to the Layout Inspector menu for lightweight groupingImprovementproject.json now supports a permissions option for script projects (by wirsnow)pr #391issue #362ImprovementAutomatically read and check declared permissions of installed apps when packaging a single fileissue #362ImprovementExpanded theme-color adaptation scope; supports more widget typesImprovementAdaptive drawer width on the Home page for landscape / ultra-wide screensImprovementAdded horizontal and small-screen layouts for About App & Developer pagesImprovementSettings-page dialogs now offer a "Use default value" menu optionImprovementFloating Action Button in File Manager auto-hides when tapping elsewhereImprovementCode formatter now supports operators such as??,?.,??=ImprovementCode editor supports reading and writing files encoded in GB18030 / UTF-16 (LE/BE) / Shift_JIS, etcImprovementCode editor supports displaying detailed file information (path/encoding/line break format/total bytes and characters, etc.)issue #395ImprovementAdded operation-error prompts for intent actions (edit / view / install / send / play, etc.)Improvementwebview element's url attribute supports relative pathsImprovementImageWrapper#saveTo path parameter supports relative pathsImprovementimages.save supports PNG file-size compression when using the quality parameterissue #367ImprovementClearing ignored update records and client-mode connection addresses is now supportedImprovementVersion-update information supports multi-language display (in sync with current UI language)ImprovementAsynchronous loading significantly improves File Manager list scrolling smoothnessImprovementImproved content and formatting of script exception messages in the consoleImprovementSample code now supports resetting a folder to its initial contentsImprovementIncreased efficiency when checking APK signature informationImprovementOptimized dialog display efficiency and information presentation for APK/media file type infoImprovementGradle build script now better adapts to newer versionsdiscussion #369ImprovementSome dependency or local library version adjustmentsCHANGELOG.md
For more release history, refer to
Project Compilation and Build
For debugging or developing the AutoJs6 open-source project, you can use Android Studio (a product of Google) or IntelliJ IDEA (a product of Jetbrains).
This section introduces the compilation and build methods of the AutoJs6 open-source project using Android Studio as an example. IntelliJ IDEA is similar.
Android Studio Preparation
Download Android Studio Panda 2 | 2025.3.2 version (choose one as needed):
- android-studio-panda2-windows.exe (1.28 GiB)
- android-studio-panda2-windows.zip (1.29 GiB)
- android-studio-panda2-linux.tar.gz (1.32 GiB)
Note: The release date for the above version is Mar 3, 2026. To download other versions, or if the above link is invalid, you can visit the Android Studio release archive page.
Install or extract the above file, then run the Android Studio software (e.g., "D:\android-studio\bin\studio64.exe").
Android SDK Preparation
Note: If the Android SDK is already installed on the computer system, this section can be skipped.
Open the Android SDK (Android Software Development Kit) settings page (any of the following ways):
Help | Find action # Input "Android SDK"
[ or ]
File | Settings # Search "Android SDK"
[ or ]
File | Settings | Language & Frameworks | Android SDK
[ or ]
File | Settings | Appearance & Behavior | System Settings | Android SDK
If the Android SDK Location field is blank, click the Edit button on the right and click Next multiple times in the pop-up window.
Note: During the process, one or more relevant agreements may need to be accepted to continue.
Once the related resources are downloaded and installed, click the Finish button.
The Android SDK Location field above will auto-populate with the path, completing the SDK preparation work.
Android SDK Tools Preparation
AutoJs6 requires certain SDK tools (like NDK and CMake).
Note: If all required Android SDK Tools for AutoJs6 are already installed on the computer system, this section can be skipped.
Open the SDK Tools settings page (any of the following ways):
Help | Find action # Input "SDK Tools"
[ or ]
File | Settings # Search "SDK Tools"
[ or ]
File | Settings | Language & Frameworks | Android SDK | SDK Tools (located in the right window)
[ or ]
File | Settings | Appearance & Behavior | System Settings | Android SDK | SDK Tools (located in the right window)
Check Show Package Details, click NDK and CMake respectively to ensure the corresponding version tools are checked, the version information of the SDK tools is located in the version.properties file in the root directory of the AutoJs6 project.
JDK Preparation
The JDK (Java Development Kit) version required for the AutoJs6 project should be at least 17, but 21 or higher is recommended.
As of Mar 14, 2026, AutoJs6 supports up to version 25 of the JDK.
Note: If the JDK is already installed on the computer system and the version meets the above requirements, this section can be skipped.
JDK can be downloaded directly via the IDE or from the Oracle website.
Open the Gradle JDK settings page (any of the following ways):
Help | Find action # Input "Gradle JDK"
[ or ]
File | Settings # Search "Gradle"
[ or ]
File | Settings | Build, Execution, Deployment | Build Tools | Gradle
Gradle JDK can be chosen or added with different versions of JDK.
If a suitable version of the JDK (>= 17) already exists in the list, it can be selected directly.
Alternatively, you can choose Download JDK to download a suitable JDK, click the Download button and wait for the download to complete.
You can also choose Add JDK to add an existing local JDK, locating its directory and completing the JDK addition.
AutoJs6 Resources Cloning
Click Get from VCS button on the main page of Android Studio.
Fill URL field with https://github.com/SuperMonster003/AutoJs6.git,
The Directory field can be modified to a specific path if needed.
Click the Clone button, wait for the AutoJs6 project resources to be cloned to the local device.
Note: The above process may require the installation of Git.
AutoJs6 Project Building
After cloning, Android Studio will open the AutoJs6 project window and automatically complete the preliminary Dependencies download and Gradle build work.
Note: The above process may take a long time. If network conditions are poor, it may need to be retried multiple times (click the Retry button).
If the build couldn't proceed automatically or you need to rebuild the project, follow these steps:
- From the
Run/Debug Configurationsmenu in the Toolbar, selectapp, which is the main AutoJs6 application - Click the
Build Project(hammer icon) button on the left to start building the project. The default shortcut is CTRL + F9 - Wait for the build to complete. The
Builder Outputtab will display a message such as "BUILD SUCCESSFUL in 1h 17m 34s"
If the build fails, you can report the error message to the AutoJs6 project's Issues page.
Note: For more details on building and running the app, please refer to Android Docs
AutoJs6 Project Deployment (Run App)
Once the project is built successfully, it can be deployed as an application (App) to a physical device (e.g., phone/tablet) or a virtual device (e.g., Android emulator).
- In the Toolbar, select
appfrom theRun/Debug Configurationsmenu, which is the main AutoJs6 application - In the
Available Devicesdropdown on the right, choose the device on which the project app should run (physical or virtual) - Click the
Run(triangle icon) button on the right to launch the app. The default shortcut isF10 - Wait for the deployment to finish; the chosen device will automatically install and run the project app
AutoJs6 Project Deployment (Generate APK)
Package the project and generate an APK file that can be installed on Android devices:
- Debug Version
Build|Build Bundle(s) / APK(s)|Build APK(s)- Generate signed debug APK
- Path example:
"D:\AutoJs6\app\build\outputs\apk\debug\"
- Release Version
Build|Generate Signed Bundle / APK- Select
APKoption - Prepare the signing file (create new or select existing), generate the signed release package
- Path example:
"D:\AutoJs6\app\release\"
Note: For more information on building an app for user release, please refer to Android Docs
Predefined Gradle Build Tasks for AutoJs6
Besides building the project App, AutoJs6 supports several predefined Gradle build tasks that help developers perform convenient project-related operations.
Under the Run/Debug Configurations menu in the Toolbar, you can find various predefined Gradle tasks, each indicated by an elephant icon on the left.
- AutoJs6 [inrt:assemble]
Assemble the "inrt" build variant, which primarily serves the AutoJs6 script packaging feature.
The AutoJs6 project has various build variants. The "inrt" variant is used for packaging scripts, generating the template file "template.apk" required for packaging.
When using the packaging feature, you might encounter the following error message:
java.io.FileNotFoundException: template.apk
This indicates that the template file does not exist. You need to manually run the inrt:assemble task to generate the template file, then rebuild and redeploy the app.
Note: When the main project code changes and you want to synchronize these changes with the packaged app, you need to rerun the
inrt:assembletask to generate the template files and redeploy the app
- AutoJs6 [app:bundle]
Package the outputs of the debug build process, primarily for the AutoJs6 TypeScript definitions project.
After running the task, it produces the latest JAR file for the AutoJs6 project. Using the Android d.ts Generator (by NativeScript), you can generate the type definitions (d.ts format) for the main AutoJs6 app.
- AutoJs6 [app:digest]
Append digest information to the APK produced by the release build, mainly to finalize the filename before publishing the latest version of AutoJs6 to GitHub.
Below is the comparison of filenames before and after appending the digest information:
Before:
autojs6-v6.6.2-arm64-v8a.apk
After:
autojs6-v6.6.2-arm64-v8a-0f2a9d74.apk
Reference: Android Docs
Script Development Assistance
To develop scripts that run with AutoJs6, appropriate development tools must be used:
For writing and debugging scripts on a PC, the VSCode plugin can enable PC-to-phone connectivity:
- AutoJs6-VSCode-Extension - AutoJs6 debugger (VSCode platform plugin)
When writing code using development tools, code completion functionality can better assist developers in completing code:
- AutoJs6-TypeScript-Declarations - AutoJs6 declaration files (code completion)
When writing code, AutoJs6-related API and usage can be consulted in the documentation at any time:
- AutoJs6-Documentation - AutoJs6 application documentation
Existing script development projects can serve as references and inspire creativity for personal script projects:
- Ant-Forest - Ant Forest energy auto-collect script by TonyJiangWJ
- Ant-Forest - Ant Forest energy auto-collect script by SuperMonster003
- autojs - Auto.js utility scripts by e1399579
- autojsDemo - Auto.js demonstration example by snailuncle
- autojs related repositories - All repositories related to the autojs topic on GitHub
Contribution
Thank you to everyone who contributed to the AutoJs6 project development.
| Contributors | Number of Commits | Recent Submissions |
|---|---|---|
| Willie169 | 1 | 2026/03/03 |
LYS86 (Lin) |
4 | 2025/12/26 |
| wirsnow | 1 | 2025/05/19 |
| TonyJiangWJ | 4 | 2025/04/24 |
| luckyloogn | 3 | 2024/12/31 |
| kvii | 1 | 2024/10/16 |
chenguangming (Tom) |
2 | 2024/05/14 |
LZX284 (AI) |
7 | 2023/11/15 |
kojoe‑code (抠脚本人) |
12 | 2023/07/12 |
| aiselp | 6 | 2023/06/14 |
| Data updated on Mar 4, 2026. |
Data entries sorted in descending order by recent submissions.
Newly initiated, unprocessed Pull Requests will be included in the data statistics after merging.
Some contributors do not appear correctly in the GitHub Contributors due to empty contribution records, but their contribution records can still be viewed via Pull Request.
