StarRailCopilot: a Python bot for Honkai: Star Rail daily chores and Simulated Universe

What StarRailCopilot automates, and for whom

StarRailCopilot is a Python script that plays Honkai: Star Rail for you. The README lists four jobs. It runs Calyx and Echo of War stages, including double-drop events, with a character development planner deciding what to farm. It collects daily mission rewards, dispatch assignments and Nameless Honor rewards. It grinds Simulated Universe, spending Trailblaze Power on inner relics. And it can host the whole thing in the background: it starts the emulator and the game itself, then reports resource status on a dashboard.

The intended user is someone who already runs an emulator and wants the daily loop handled without sitting in front of the game. The README is blunt about why an emulator is required. If you run the script against the desktop client, the game window has to stay in the foreground, and the README's own phrasing is that you would be stuck unable to touch your mouse and keyboard. Emulator support is documented on the AzurLaneAutoScript wiki, which covers Windows, Mac and Linux.

There is also a cloud option, but the README marks it as China server only, pointing to a wiki page about running SRC on the cloud version of the game. Everyone else needs local emulation.

How the Alas base and the image pipeline fit together

SRC is built on AzurLaneAutoScript, the Azur Lane bot by the same author. The README frames the new project as a rewrite of problems accumulated in Alas over three years, and it names them: an OCR stack trained on cnocr 1.2.2 with an mxnet dependency the README describes as no longer very active; a hand-rolled code generator for config files, to be replaced by pydantic; a button_extract tool that maintains more than 4000 template images but has serious performance problems; and tight coupling between the Alas framework and Azur Lane itself.

That coupling point matters for anyone evaluating the architecture. The README says the completed Arknights plugin MAA and the in-progress fgo-py plugin both ran into the same problem, which is why reducing game-specific coupling is an explicit goal rather than a side effect.

The detection layer is template matching and OCR over emulator frames, with minimap tracking handled separately; the README links a wiki page on the minimap recognition principle. Input goes through adbutils and uiautomator2, which is how the script talks to an Android emulator. Configuration is validated with pydantic, and a webapp directory plus a gui.py entry point provide the interface shown in the README screenshots. The repository layout also carries route/, tasks/, module/, assets/ and config/, which matches a task-and-route scheduler model rather than a single monolithic script.

Installing StarRailCopilot and running your first task

The README does not put install commands inline. It points to a Chinese installation tutorial on the wiki that covers automatic installation, usage and manual installation, and to the device support document on the Alas wiki for emulator and OS coverage. Treat those two pages as the source of truth, because the repository ships installer.py and console.bat alongside a requirements.txt generated by pip-compile for Python 3.10, and the manual path is what those files serve.

For a manual install on Python 3.10, the pinned dependency set is what the project expects:

pip install -r requirements.txt

After installation, the graphical entry point is gui.py, and the console wrapper is console.bat on Windows:

python gui.py

The README screenshots show a configuration panel and a dashboard. In the panel you select the emulator and the game server, then enable the tasks you want: the daily dungeon run, the reward collection, Simulated Universe. The dashboard is where resource status appears once the scheduler is running. The README does not document a rollback procedure or a config migration path, so back up the config directory before upgrading.

If you prefer the packaged route, the README links the releases page for downloads, and the newest release listed is v2025.03.04, tagged StarRailCopilot 0.5.7.

The emulator requirement is a real constraint, not a footnote

Running through an emulator is the design decision with the most consequences. It buys background operation, which is the entire point. It costs you a second rendering path: the script sees an emulated Android frame, not the native client, so anything that changes in the emulator's rendering or input layer can break detection. The README's performance note is anecdotal hardware detail from the author, an 8700k with a 1080ti reaching about 40fps in MuMu 12 at very high settings, and it is not a benchmark you should plan capacity around.

The cloud path is narrower than it first looks. The README labels it China server only, so players elsewhere cannot substitute cloud play for a local emulator.

Asset coverage is the other sharp edge. The README says adding multi-language or multi-server support requires adapting assets, and links a development document section on adding a button. That is a development task, not a setting. If your server or language is not already covered, you are either contributing assets or not running the bot. The README also notes that in Alas, missing assets for foreign servers were drowned in noisy logs, which suggests the new project is trying to improve that reporting, but the underlying dependency on complete assets remains.

StarRailCopilot versus March7thAssistant and other HSR automation

The closest comparison people search for is March7thAssistant, another Honkai: Star Rail automation project. The difference in approach is lineage and framework. SRC is a port of the Alas architecture, which means it inherits a task scheduler, a pydantic-validated config system, a template-matching asset pipeline and a web interface that were built and hardened for a different game first. March7thAssistant is its own codebase, and this material does not describe its internals, so the honest statement is that the two differ in framework heritage rather than in a feature table I can verify here.

What SRC's heritage buys is a documented extension path: the README points contributors at the Alas wiki for development documentation, at a roadmap issue for planned work, and at the button-extraction workflow for assets. What it costs is the coupling the README itself calls out as a problem in the parent project, plus the weight of a large dependency tree pinned to Python 3.10.

If you want a scheduler you can extend for a different game, SRC's structure is the more interesting one. If you want the smallest possible moving part for one game, a single-purpose project is easier to reason about.

Maintenance cadence, licence and upgrade cost

The repository is not archived, and the last push was on 2026-09-21, two days before this writing. That is a current codebase. The release cadence is a different story: v2024.07.03, v2025.01.15 and v2025.03.04 are the three most recent releases listed, so tagged versions arrive far less often than commits. If you track releases, expect to wait; if you track master, expect to absorb untagged changes.

The licence is GPL-3.0. That is a copyleft licence, and the practical implication for anyone modifying and distributing the code is that derivative distributions carry the same licence obligations. Running it privately for your own account is a different situation from shipping a modified build. This is not legal advice; read the LICENSE file in the repository root if you plan to redistribute.

Upgrade cost is dominated by the pinned dependency set. requirements.txt is generated by pip-compile for Python 3.10 with exact pins across adbutils, uiautomator2, onnxruntime, opencv-python and the rest. Moving off Python 3.10 means regenerating that set, which is a maintainer task, not an end-user one. The README does not document a config migration path between versions, so keep a copy of the config directory before you pull.

Editorial conclusion

Adopt StarRailCopilot only if you accept GPL-3.0 obligations, run it against an emulator rather than the desktop client, and treat the account risk as yours. Skip it if you play on a platform the emulator route does not cover, or if you need the desktop client to stay in the foreground. Before anything else, verify the installation wiki page and the emulator support document for your OS, confirm which server and language assets your account needs, and check the release page for the newest build rather than the one described here.

Frequently asked questions

Official sources

1. Issues
2. License: GPL-3.0
3. LmeSzinc/StarRailCopilot on GitHub
4. README
5. Releases