Skip to content

[Bug]: loopx app runing failed on macbook M5 #9133

Open

Description

@xiaods

Preflight

  • I searched existing issues and discussions for this behavior.
  • This report is not an unpatched security vulnerability.
  • The report and attachments contain no credentials or private/internal material.

Issue origin

Observed or reproduced in a real environment

LoopX version or commit

Version 2.3.0 (2.3.0)

Host or runtime surface

Codex App

LoopX area

Control plane (goals, todos, quota, scheduler, registry, runtime)

Problem

image

Minimal reproduction

  1. install loopx app
  2. run it and failed.

Expected behavior

works like a charm.

Actual behavior

missing nodejs

Sanitized diagnostics

Additional context

No response

Activity

  1. added
    bugSomething isn't working
    triageNeeds maintainer triage or routing.
    on Nov 20, 2026
  2. LIHUA919 commented on Nov 20, 2026

    @LIHUA919
    Contributor

    Characterized on current main; this is the documented system-prerequisite path, not an M5-specific defect. 2.3.0 is the current stable, so there is also no newer release that changes this behavior.

    What the message means

    The App installs its bundled runtime snapshot by running scripts/install-local.sh (spawned from apps/desktop/loopx-control-plane/src-tauri/src/bundled_runtime.rs). The installer validates the release candidate with loopx --format json doctor --deep --installation-only; the typescript_effect_runtime_ready doctor check is required and fails closed when no Node.js is found on the probe PATH (loopx/control_plane/runtime/node_probe.py resolves node via shutil.which). Doctor then exits 1, the installer exits 1, and the App surfaces runtime_install_exit_1. The boot page combines that exit code with the environment probe environment.node_found=false and renders the message in your screenshot (「安装程序退出(1);App 的启动环境未找到 Node.js…」).

    Why Node is expected

    LoopX's control plane runs a managed TypeScript Effect runtime that requires Node.js 22.22.3 or newer (Node.js 24 LTS recommended) on the machine; the App bundles its own source snapshot and verified frontend but deliberately does not bundle Node (see docs/guides/installing-loopx.md, "Validate Node before installing or upgrading LoopX"). A fresh Mac has no Node, so first boot stops here — the same shape as the documented fresh-Mac-without-Python case (runtime_install_exit_2) in the App README's Known Issues.

    One nuance worth knowing: a Finder-launched App does not inherit your shell PATH. The App searches a bounded set (~/.local/bin, /opt/homebrew/bin, /usr/local/bin, the Homebrew keg-only node@24/node@22 prefixes, then the inherited process PATH). Node installed via nvm/fnm/volta is invisible to the App even though it works in your terminal.

    Self-service recovery

    1. Install a supported Node: brew install node (or brew install node@24), or the official installer from nodejs.org (22.22.3+).
    2. Reopen the App, or press 「修复当前版本」(Repair this version) in the 恢复与更新 (Recovery & updates) panel; the environment probe refreshes automatically and installation resumes.
    3. Verify via the App's own 诊断信息 (Diagnostics) panel — environment.node_found / node_version — rather than only a terminal, since that also answers the nvm case above.

    If it still fails with a Node the App can see, expand 诊断信息 on the boot screen, press the copy button, and attach it here; the diagnostics block in the report is empty, and that JSON (public-safe by design) is what we would need next.

    Follow-up

    The App README (apps/desktop/loopx-control-plane/README.md) documents the Python analog of this failure but not the Node one. I'll send a small docs PR adding the parallel Known Issues entry so this recovery path is documented alongside the Python case.

  3. LIHUA919 commented on Nov 20, 2026

    @LIHUA919
    Contributor

    Docs sent in #9135 (branch codex/app-nodejs-missing-9133, based on latest main eb552a8bb): the App README's Known Issues now documents this exact failure (runtime_install_exit_1 + environment.node_found=false) with the self-service steps above, mirroring the existing fresh-Mac-without-Python entry, and the Prerequisites Node bullet now states the actual 22.22.3+ (24 LTS recommended) runtime requirement. Docs-only; no code or packaging change, since the runtime requiring a user-provided Node is the documented design. If installing a visible Node does not unblock your App, please attach the copied diagnostics JSON from the boot screen.

  4. xiaods commented on Nov 21, 2026

    @xiaods
    ContributorAuthor

    my node is here:
    ❯ which node
    /Users/xiaodeshi/.nvm/versions/node/v24.22.1/bin/node

  5. LIHUA919 commented on Nov 21, 2026

    @LIHUA919
    Contributor

    Thanks — that confirms the exact variant characterized above: your Node lives under ~/.nvm/versions/node/v24.22.1/bin, and the Finder-launched App does not load your shell profile, so its bounded node search (~/.local/bin, /opt/homebrew/bin, /usr/local/bin, Homebrew keg-only node@24/node@22 prefixes, then the inherited process PATH) never sees nvm-managed binaries. The App's diagnostics would show node_found=false for the same reason.

    Quickest fixes (any one):

    1. brew install node@24 (or node@22) — the App resolves the Homebrew prefix directly; or
    2. Symlink the existing binary into a searched location, e.g. mkdir -p ~/.local/bin && ln -s ~/.nvm/versions/node/v24.22.1/bin/node ~/.local/bin/node; or
    3. Launch the App from a terminal (open -a LoopX...) after nvm use 24 so it inherits your shell PATH.

    Then use Repair this version (or restart the App) so the runtime installation re-runs; the boot screen should clear once node --version resolves to 24.22.1. The README patch in #9135 adds this exact recovery entry to Known Issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingtriageNeeds maintainer triage or routing.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions