Skip to main content

automas-maafw-runner

Isolated MaaFW runner service for AUTO-MAS.

It provides maafw.runner.v1. The service builds run plans in the host process and runs MaaFW through a worker subprocess so importing the service does not load maa into the AUTO-MAS main process.

The wheel includes the MaaFW runtime worker code. maa is imported only by the worker subprocess entrypoint, not by MaaFWRunnerService.

Runner environments are now selected from maafw.runtime_pool.v1 by a canonical requirement selector rather than by project path. The returned environment holds a lease for the worker lifetime; callers must invoke MaaFWRunnerService.release_environment() in their worker cleanup path. Runtime Pool keeps selector venvs isolated while uv reuses a pool-local package cache with hardlinks. Runner 0.4.0 requires Agent Env 0.1.4+ and Runtime Pool 0.2.0+, which record installer/cache/link metadata, never composes environments through PYTHONPATH, and prunes the pool-local uv cache after collecting stale runtimes. Successful reclaim statistics and explicit unavailable/unsafe/error states are written to the runner log.

MaaFWRunnerService.prepare_project_environment() prewarms both the exact canonical Runtime Pool identity used by the first real run and the project Agent environments. Its short preflight lease is always released; the later worker run reacquires the same runtime without reinstalling unchanged requirements. Optional progress events expose deterministic runtime/Agent stages and do not invent dependency-download byte counts.

For a Managed project, the caller supplies the Store-authoritative complete selector, runtimeId, poolId, and runtime.python constraint. Runner checks the bound Pool manifest and Python identity, then reuses that trusted binding; it does not recompute a CP313 runtime ID from the AUTO-MAS host's CP312 interpreter. Preparation and execution therefore acquire the same runtime.

Managed projects may declare runtime.constraint, runtime.binding, runtime.python, and nativePluginPaths in .auto_mas_maafw_project.json. An isolated Python Agent reuses the worker interpreter only when the manifest explicitly sets runtime.sharedAgentDependenciesComplete to true. Legacy, incomplete, binary, and external Agents keep their previous routing behavior.

Runner 0.3.0 also implements ProjectInterface v2.8 hotkey substitution for AUTO-MAS Direct:

  • saved values stay readable (E, Ctrl+A, Ctrl+Shift+A);
  • {Name} and {Name}.primary become one integer virtual key code;
  • {Name}.modifier1 and {Name}.modifier2 follow the saved modifier order;
  • Win32 uses Windows Virtual-Key codes and Adb uses Android KeyEvent codes;
  • unsupported controller types, unknown keys and missing referenced modifiers fail the run-plan build with an actionable error.

Release files for automas-maafw-runner 0.4.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for automas-maafw-runner 0.4.0
File Size Uploaded
automas_maafw_runner-0.4.0.tar.gz 55.6 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for automas-maafw-runner 0.4.0
File Interpreter ABI Platform
automas_maafw_runner-0.4.0-py3-none-any.whl Python 3 none any Details

Total release size: 115.8 kB

Release files / automas_maafw_runner-0.4.0.tar.gz

Download URL automas_maafw_runner-0.4.0.tar.gz
Size 55.6 kB
Tags Source
SHA-256 checksum
How to use checksums
733d2d47dd6219f6f3a0b2b096c74c39fe77cbae13bc6620904ebbcde8be45a8
BLAKE2b-256 checksum
How to use checksums
ad02464958f7501b0ddb54a048b19b37b4b8671179e0e3c3caa54728daeeb9f4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 9, 2026.

Transparency log

Release files / automas_maafw_runner-0.4.0-py3-none-any.whl

Download URL automas_maafw_runner-0.4.0-py3-none-any.whl
Size 60.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
dd1e5e2323d197cd89190c5eba24eb4110e862caa919847cb55120ae9dff4838
BLAKE2b-256 checksum
How to use checksums
d42d6f0c3ba0cf5f76b9ab98b40bed956c2eef2b804a8faa6db0167c52dd0a2c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 9, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.4.0 This release

2 release files

0.1.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page