MobileAgent: eight project directories, two model hubs, and no release to pin
Mobile-Agent: The Powerful GUI Agent Family
At a glance
- What is it?
- X-PLUG's MobileAgent repository collects the GUI agent family from Tongyi Lab at Alibaba Group across version directories rather than packages, with weights on HuggingFace and ModelScope and demos on Alibaba Cloud. The last push landed on 2026-10-28, the project has published no GitHub releases at all, and the newest work announced in its news log, ToolCUA, lives in a separate repository.
- Who is it for?
- This repository is worth using when you want the Mobile-Agent framework code and links to the GUI-Owl weights in one place and are willing to pick a version directory yourself, since there is nothing to install from the root and nothing to pin. It is a poor fit if you need a self-hosted path today, a stable version identifier.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 12 days ago.
- What is it written in?
- Mainly Python, 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
- X-PLUG/MobileAgent9,379 ★ · +184
| Repository | 2026-09-12 | 2026-11-15 |
|---|---|---|
| X-PLUG/MobileAgent | 9.2k | 9.4k |
184 Stars in the last 64 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The root has version directories and no packaging file at all
The top level of the repository is index.html, assets/, README.md, README_zh.md and eight project directories: GUI-Critic-R1/, Mobile-Agent-E/, Mobile-Agent-v1/, Mobile-Agent-v2/, Mobile-Agent-v3/, Mobile-Agent-v3.5/, PC-Agent/ and UI-S1/. There is no pyproject.toml, no setup.py, no requirements.txt at the top level.
That layout is the single most important practical fact about this project. Each generation of the agent is a self-contained directory that you read and run, not a package you depend on, so there is nothing to add to a requirements file and nothing for a package manager to resolve. If you are integrating Mobile-Agent into an existing Python service, you are vendoring a directory and pinning a commit, and when you upgrade you choose a different directory rather than bumping a version constraint.
The repository is MIT licensed with Python as its primary language, and the Chinese README sits beside the English one at README_zh.md. The bilingual pairing is worth knowing before you file anything, since the two files do not have to change together.
The documented first run is a hosted demo, not a local install
The README opens by inviting you to try Mobile-Agent-v3.5 through two online demos, one on ModelScope at the computer_use studio and one on Alibaba Cloud Bailian at the adk-computer-use experience page. A separate line says the Mobile-Agent-v3.5 API is provided on Bailian for quick experience, with the documentation linked from the Bailian console model market page for gui-plus-2026-02-26.
The earliest deployment note goes further. The 2025.9.24 entry says the demo is based on Wuying Cloud Desktop and Phone, and that no deployment of models locally or preparation of devices is needed, only an instruction. The 2026.3.31 entry adds that Mobile-Agent-v3.5 is available on Alibaba Cloud Wuying Cloud Phone, a cloud-based Android environment for mobile use.
The consequence is that every friction-free route in this README runs on Alibaba Cloud services, and the 2025.9.24 entry describes its Mobile-Agent-v3 API as limited-time free. A hosted demo is a reasonable way to see the behaviour, but it is a rental arrangement, not an installation, and the free offer is temporary by its own wording.
Announced model sizes outnumber the checkpoints linked in the header
The 2026.2.14 entry announces GUI-Owl-1.5 as a family of native multi-platform GUI agent foundation models at 2B, 4B, 8B, 32B and 235B, in Instruct and Thinking variants, built on Qwen3-VL for desktop, mobile and browser automation. The technical report is at arxiv 2602.16855.
The links in the header cover fewer of those. There is a GUI-Owl-1.5 Collection on HuggingFace at mPLUG/gui-owl-15 and the matching ModelScope collection at iic/GUI-Owl-15, plus individual entries for GUI-Owl-32B and GUI-Owl-7B on both hubs, each under the mPLUG organisation on HuggingFace and the iic organisation on ModelScope. Separately, the 2025.9.16 entry names an OSWorld RL-tuned checkpoint, GUI-Owl-7B-Desktop-RL, and the UI-S1 entry names a model at mPLUG/UI-S1-7B with a dataset at mPLUG/UI_S1_dataset.
So the sizes announced in the news log and the sizes you can click from the header do not correspond one to one. A 235B or 4B member is announced but not linked in the header, which means anyone targeting a specific size has to open the collection and find out what is actually published.
The newest work announced here ships from a different repository
The most recent news entry, dated 2026.5.12, announces ToolCUA as an end-to-end computer use agent for GUI and tool path orchestration, built on a two-stage training pipeline that goes from trajectory-aware tool synthesis to online agentic reinforcement learning, with the paper at huggingface.co/papers/2605.12481 and the code at the X-PLUG/ToolCUA repository.
That pattern runs through the whole log. OSWorld-MCP, released 2025.10.30, is described as a benchmark for evaluating Model Context Protocol tool invocation capabilities in real-world scenarios, and it has its own repository. Only some items live inside MobileAgent, among them UI-S1 with its paper at arxiv 2509.11543 and its code in the UI-S1 directory, and the OSWorld, AndroidWorld and real-world mobile scenario code under Mobile-Agent-v3.
For a reader, this means the news log is a pointer index rather than a changelog. Following the most interesting recent work takes you to a different repository, and the only items you can count on being in this tree are the version directories themselves.
Papers and awards are the only coordinates for a version
The publication record is dense and precise. Mobile-Agent-v2 was accepted at the thirty-eighth annual conference on neural information processing systems in 2024. PC-Agent was accepted at an ICLR 2025 workshop. GUI-Critic-R1 was accepted at NeurIPS 2025. UI-S1 carries the arXiv identifier 2509.11543, the original GUI-Owl and Mobile-Agent-v3 release carries 2508.15144, and GUI-Owl-1.5 carries 2602.16855. There are also best demo awards at the twenty-third China National Conference on Computational Linguistics in 2024 for Mobile-Agent and at the twenty-fourth in 2025 for Mobile-Agent-v3.
What is missing is any machine-readable version history. The project has no GitHub releases, so there is no tag to pin, no release note to diff and no upgrade path that a tool can follow. Each paper describes an architecture, and each directory holds code, but the link between a paper and a commit is left to you.
That combination is unusual: strong external validation with no internal versioning discipline. Anyone deploying this needs to record commit hashes by hand, and anyone citing a result needs the commit beside the arXiv identifier.
Evaluation code is the only clue to the environment an agent expects
Three of the code paths published here are anchored inside the Mobile-Agent-v3 directory, and their anchor names tell you what each one assumes: evaluation on OSWorld, evaluation on AndroidWorld, and deployment of Mobile-Agent-v3 on your own mobile device. The 2025.9.16 entry describes these as the open-sourced code for OSWorld, AndroidWorld and real-world mobile scenarios.
Tool use is treated as a separate capability rather than folded into the agent. OSWorld-MCP exists to evaluate Model Context Protocol tool invocation in real-world scenarios, and ToolCUA targets exactly the decision of when to use a GUI action, when to invoke a tool and when to switch between the two.
For an adopter this is the most useful part of the tree, because those anchors are the only place the repository states what an agent needs around it: a desktop harness for OSWorld, an Android harness for AndroidWorld, and real hardware for the mobile path.
Last push 2026-07-07, no releases, and a news log that ends in May
The last push to main was on 2026-10-28, and the project has never published a GitHub release. The newest dated entry in the news log is 2026.5.12, more than five months before that push, so the recent commits are not the announcements a reader would notice on the front page.
Three facts follow from that. There is no version identifier to require, which means any dependency you express has to be a commit hash you chose. There is no changelog to read before upgrading, since CHANGELOG.md is not among the top level files and the news log is a marketing timeline rather than a change list. And the served weights on the hubs can move under you in a way the repository does not record.
The README also leans on hosted inference throughout: online inference for the GUI-Owl-1.5 series through Alibaba Cloud Bailian and Modelscope API-Inference, and the Mobile-Agent-v3.5 API on Bailian. That is a reasonable way to evaluate the models, but it means the currently documented way to run this project depends on services whose availability and pricing the repository does not describe.
Editorial conclusion
This repository is worth using when you want the Mobile-Agent framework code and links to the GUI-Owl weights in one place and are willing to pick a version directory yourself, since there is nothing to install from the root and nothing to pin. It is a poor fit if you need a self-hosted path today, a stable version identifier. Before committing, decide which directory you actually want, check whether the checkpoint size you need is one of the ones linked in the header, and record the commit hash, because the project has never cut a release.
Frequently asked questions
what is mobile agent
Mobile-Agent is the GUI agent family from Tongyi Lab at Alibaba Group, and this repository holds its generations as separate directories: Mobile-Agent-v1, Mobile-Agent-v2, Mobile-Agent-v3, Mobile-Agent-v3.5 and Mobile-Agent-E, alongside GUI-Critic-R1, PC-Agent and UI-S1. The project is MIT licensed, written mainly in Python, and has no homepage set.
how to install checkpoint mobile agent
The repository root has no packaging file, so checkpoints come from the model hubs rather than from pip. GUI-Owl-1.5 is linked as a collection at mPLUG/gui-owl-15 on HuggingFace and iic/GUI-Owl-15 on ModelScope, with GUI-Owl-32B and GUI-Owl-7B linked individually, and GUI-Owl-7B-Desktop-RL and mPLUG/UI-S1-7B named separately.
Does MobileAgent have a local installation guide?
The entry points visible in the README header and news log are the ModelScope online demo studio, the Bailian online demo, the Bailian model documentation for gui-plus-2026-02-26, and the per-version directories in the repository such as Mobile-Agent-v3.5/ and Mobile-Agent-v3/.
Which MobileAgent version should a new project use?
Nothing in the repository marks a directory as current or deprecated, and there are no GitHub releases to compare. The header invites you to try Mobile-Agent-v3.5 through the ModelScope and Bailian demos, while the news log also covers Mobile-Agent-v3, Mobile-Agent-E, Mobile-Agent-v2 and Mobile-Agent-v1 as separate trees.
What does MobileAgent need to run a GUI agent on mobile?
The README points to the evaluation code anchored in Mobile-Agent-v3 for OSWorld, for AndroidWorld and for deploying Mobile-Agent-v3 on your own mobile device, and separately to Alibaba Cloud Wuying Cloud Phone as a cloud-based Android environment.
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/x-plug-mobileagent)Star history chart for your README
[](https://hysenlabs.com/projects/x-plug-mobileagent)Was this useful?