MaaEnd: A Visual AI Automation Assistant for Arknights Endfield
MaaEnd is an automation assistant for Arknights Endfield that combines visual AI, scripting, and task orchestration to support practical in-game workflows.
At a glance
- What is it?
- MaaEnd is an open-source, Go-based automation assistant for Arknights Endfield that combines visual AI, scripting, and task orchestration. This review covers its feature set, architecture, setup, limitations, and alternatives.
- Who is it for?
- MaaEnd suits players who want to automate repetitive in-game tasks across PC and Android, especially those comfortable with a fast-moving, community-driven project. It is not for players who require stability, polished documentation, or who avoid AGPL-3.0 licensing.
- Can I use it commercially?
- Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
- Is it still maintained?
- Yes. The repository received new commits within the last day.
- What is it written in?
- Mainly Go, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- MaaEnd/MaaEnd4,456 ★ · +939
| Repository | 2026-07-28 | 2026-11-15 |
|---|---|---|
| MaaEnd/MaaEnd | 3.5k | 4.5k |
939 Stars in the last 110 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
What MaaEnd Solves and Who It Is For
MaaEnd addresses the problem of repetitive, time-consuming tasks in Arknights Endfield, a game that demands daily logins, resource farming, and combat grinding. The project targets players who want to offload these chores to an automated assistant. It is built on MaaFramework and MXU, leveraging visual AI to recognize game states and scripted actions to respond. The README lists a wide range of features, from auto-combat and item pickup to inventory management and base building. This is not a general-purpose bot; it is specifically designed for Endfield's mechanics, such as matrix screening, protocol space farming, and blueprint import. The intended user is a player who spends significant time in-game and wants to reduce manual effort, not a developer seeking a generic automation framework.
Core Mechanisms: Visual AI, Scripting, and Orchestration
The underlying architecture is not described in detail in the README, but the feature list reveals a clear pattern. MaaEnd uses visual AI to identify game elements on screen, such as flashing pickups, puzzle patterns, or matrix affixes. The project then executes scripted actions, like clicking, swiping, or performing skill combos. Task orchestration ties these together: for example, after a matrix farm battle, it can automatically trigger matrix screening. The README mentions 'real-time exploration assistance' that continuously recognizes the screen and performs key operations as needed. This suggests a loop of screenshot capture, image recognition, decision, and action. The README says MaaEnd is powered by MaaFramework, MXU and MaaFwApp. The Go language is the primary implementation language, alongside a C++ algorithm directory under agent/cpp-algo.
Getting Started: Installation and Configuration
The README directs users to the official website (https://maaend.com/) to download the latest version. It explicitly states that new versions auto-update, so manual updates are unnecessary. The developer guide is available at a docs index in the repository, but the README does not provide setup commands or configuration keys. For developers, the repository includes a docs directory with a developer documentation index. The project supports PC (Win32), Android (ADB), Linux and macOS controllers, as listed under multi-platform adaptation. The absence of detailed setup steps in the README is a limitation; users must rely on the website or community support. The README mentions QQ groups and Discord for user and developer support, which indicates a community-driven onboarding process.
Feature Depth: From Auto-Battle to Inventory Management
MaaEnd's feature list is extensive, covering nearly every repetitive aspect of Endfield. Combat assistance includes auto-attack, dodge, skill use, ultimate, and focus-fire. It also handles auto-pickup of glowing items and collection points. Puzzle solving is a standout: the 'Puzzle Master' feature uses AI to solve puzzles in single, loop, or demo modes. Matrix screening automatically locks or discards items based on weapon rarity, matrix type, and extension rules. The 'Matrix Farming' feature chains battles into screening, creating a one-stop workflow. Other features include environmental monitoring, protocol space farming, ecological farm management, auto-collection, gift giving, weapon upgrades, and trading. The breadth is impressive, but it also means the project is complex. Each feature likely requires specific image templates and scripts, which the README does not document. The 'Baker mouthpiece' feature that clears chat messages suggests attention to minor UI annoyances, which is a nice touch.
Limitations and Wrong-Tool Cases
The README warns that this is a 'rapidly iterating project' with 'small bugs' and encourages issue reports. This is a clear signal that stability is not guaranteed. The auto-update feature, while convenient, could introduce breaking changes without user consent. The project is tied to a specific game, so it becomes useless if the game updates its UI or if the user stops playing. It is also not suitable for players who prefer manual play or who are concerned about violating the game's terms of service, though the README does not address ToS. The lack of detailed documentation on configuration is a practical limitation: the feature list mentions presets, but no details on how to customize them. The project is primarily Chinese-language, with an English README available, and the developer documentation index the README links is under docs/zh_cn. This could be a barrier for non-Chinese speakers. Finally, the AGPL-3.0 license means that any derivative work must also be open source, which may deter commercial use.
Alternatives and Different Approaches
A direct alternative is manual play, which is the baseline. For automation, MaaFramework itself is a general-purpose automation framework that can be used to build custom assistants for any game. MaaEnd is built on MaaFramework, so using MaaFramework directly gives users more control but requires more development effort. Another alternative is using a macro recorder or scripting tool like AutoHotkey for Windows, which does not rely on visual AI but instead uses fixed coordinates or pixel colors. This approach is simpler but less adaptable to dynamic game states. The key difference is that MaaEnd uses real-time image recognition to make decisions, whereas macro tools execute static sequences. This makes MaaEnd more robust to UI changes, but also more resource-intensive. The project's use of MXU, which is another MistEO project, suggests a tight integration with the MAA ecosystem, giving it a community advantage over generic tools.
Maintenance, Upgrade Cost, and Licensing
MaaEnd's release cadence is rapid, with multiple beta versions in a short span. The last push was on 2026-11-02, the same day as v3.0.0-beta.3, preceded by v3.0.0-beta.2 and v3.0.0-beta.1. This indicates active development, but also a high upgrade frequency. The auto-update feature reduces the user's manual effort, but it also means users must adapt to changes frequently. The project is not archived, and the default branch is v2, suggesting a stable major version. The license is AGPL-3.0, which is a strong copyleft license. This means that if you modify the code and distribute it, you must release your modifications under the same license. For personal use, this is not a concern, but for anyone considering integrating MaaEnd into a commercial product, the license implications are significant. The README does not provide any contribution guidelines beyond a developer docs index, so the maintenance cost for contributors is unclear. The project relies on community support via QQ and Discord, which suggests that documentation may be less formalized.
Editorial conclusion
MaaEnd suits players who want to automate repetitive in-game tasks across PC and Android, especially those comfortable with a fast-moving, community-driven project. It is not for players who require stability, polished documentation, or who avoid AGPL-3.0 licensing. Before adopting, verify that your platform (Win32, ADB, Linux or macOS) is supported, check the latest release notes for known bugs, and review the developer docs for configuration specifics. The project's rapid iteration means you should expect frequent updates and occasional breakage.
Frequently asked questions
What is MaaEnd?
An automation assistant for the game Arknights Endfield, described as combining visual AI, scripting and task orchestration for in-game workflows. It is written in Go with a native Android component and builds on the Maa automation framework, and the README says it is iterating quickly and may contain bugs.
How do I install MaaEnd?
By downloading the latest version from the project's official website, which is the only instruction the README gives.
Does MaaEnd update itself?
Yes. The usage notes say new versions update automatically with no manual action needed. The three newest releases are v3.0.0-beta.1, v3.0.0-beta.2 and v3.0.0-beta.3, published between 2026-10-31 and 2026-11-02.
What can MaaEnd automate?
More than thirty in-game tasks, including skipping dialogue and choosing branches automatically, combat assistance, item pickup, puzzle solving, resource collection routes, bulk blueprint importing, base building tasks, credit shop shopping and gift sending. One feature logs out and switches accounts, another sends batch friend requests that can target strangers, and another deletes friends by last-login time.
What languages is the MaaEnd codebase written in?
Go, plus a native Android component, a C++ algorithm directory, and Python and Node toolchains for the development scripts. The repository carries three coding-agent configuration directories, and a default branch named with a version prefix.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/maaend-maaend)Star history chart for your README
[](https://hysenlabs.com/projects/maaend-maaend)Was this useful?