Add a no-Docker local run/test path (mxcli run --local) and document it in skills

[ako]

Problem

mxcli's run/test workflow assumes Docker/Devcontainer. In Docker-restricted corporate environments, users must reinvent every step themselves.

Specifics from the report:

• App startup: mxcli docker run is unusable; users fall back to Deploy-for-Eclipse (runtimelauncher.jar), which isn't documented in the skills.
• Test execution: playwright-cli is a devcontainer-only tool; npm-based Playwright works but isn't documented.
• Redeploy: after model changes, a 3-step stop → mxbuild → restart is required, but the procedure is unclear.

Current behavior

mxcli docker run (cmd/mxcli/docker.go:52-104) hard-requires Docker (Compose V2 / Podman). There is no mxcli run --local. Skills run-app.md and test-app.md assume Docker-in-Docker + globally-installed playwright-cli in the devcontainer.

Request

Add a local (no-Docker) path — either a mxcli run --local command (manage runtime + DB outside Docker) or, as a cheaper first step, document the runtimelauncher.jar startup + npm-Playwright + redeploy flow in the skills.

Related

• mxcli docker run` fails on Mendix 10.x — no alternative path to run the app #211 mxcli docker run fails on Mendix 10.x — no alternative path to run the app (same "no non-Docker path" theme).
• mxcli docker run fails on Apple Silicon: Studio Pro 11.10.0 Beta launches x86_64 Deno, panics under Rosetta #557 mxcli docker run Apple Silicon failure.

---

Source: customer feedback batch (2026-06). Reporter: Miwa. Reporter severity: 4/5.
Filed after codebase investigation at 297e0b0a.

[github-actions]

Issue Triage

Summary:
The issue requests a no‑Docker local run/test option for mxcli (e.g., mxcli run --local) and documentation of the alternative workflow using runtimelauncher.jar and npm‑based Playwright for users in Docker‑restricted environments.

Checklist for feature request completeness

Required info	Present?	Details
Use case – why the feature is needed, what problem it solves	✅	Describes Docker‑restricted corporate environments and the need to avoid reinventing steps.
Proposed syntax or behavior (if applicable)	✅	Suggests adding mxcli run --local or documenting the runtimelauncher.jar + npm‑Playwright + redeploy flow.
Mendix version relevance (if version‑specific)	❌	No explicit mention of which Mendix versions the feature should target or be tested against.

Missing information:
Could you please clarify the Mendix version(s) this feature should support (e.g., 9.x, 10.x, or a specific range)? Knowing the version relevance will help prioritize and implement the solution correctly.

Thank you for the detailed request!

---

Automated triage via OpenRouter — workflow source