“Legacy YAML” specifically means the YAML automation protocol provided by @midscene/cli: a workflow uses top-level tasks, each task contains flow, platform and Agent runtime configuration commonly lives in YAML, and execution uses the midscene command or YAML batch configuration with fields such as files, setup, and concurrent.

The legacy path is now in maintenance mode. Existing projects remain compatible and necessary issues will be fixed, but it will not receive new syntax, capabilities, configuration fields, or CLI options. Existing cases, batch configuration, directory layout, and the midscene command can remain unchanged. Upgraded versions execute them through the shared kernel and generate the new Test report page. Use Midscene Test for new projects, new cases, and future capability development.

Run legacy files and YAML batch configuration with midscene; run native cases/steps files and TypeScript project configuration with midscene-test. The two formats may live in separate directories in one repository, but a file or command invocation must not mix them. Start with Midscene Test overview, then follow Migrate to Midscene Test to convert fields and switch commands.