Install and start
The current published package is phynite-lab@0.1.5. Node.js version >=22.13.0 is required. npm installs the launcher and the matching optional native application package for the host OS and CPU.
Keep npm optional dependencies enabled. If a package manager was configured with --omit=optional or the selected platform package was removed, the launcher reports a missing runtime instead of silently using a development fixture.
The launcher binds services to loopback, opens a browser, and stores the local workspace under ~/.phynite-lab. User projects and runtimes remain outside the npm installation directory.
npm install -g phynite-lab@latest
phynite-labSupported platforms
| Platform | Package/runtime | Notes |
|---|---|---|
| macOS Apple Silicon | darwin-arm64 | Native arm64 package. |
| Linux ARM64 | linux-arm64 | Requires glibc >=2.39 and verified user namespaces. |
| Linux x64 / Omarchy / Arch | linux-x64 | Requires glibc >=2.39 and verified user namespaces. |
| Windows | WSL2 linux-x64 | Run npm and phynite-lab inside WSL2; a Windows-native solver is not installed. |
Launcher commands and workspace identity
The default command starts the service in the foreground. --no-open prints the loopback URL without opening a browser. --port requests a port; if it is already used, the launcher selects an available loopback port and reports the actual origin. --data-dir gives each workspace its own database, projects, runtimes, and logs.
status reports the healthy instance for that data directory. stop asks the instance owned by that workspace to shut down cleanly. doctor checks distribution identity, service readiness, data paths, and startup diagnostics. Launching the same workspace again reuses its healthy instance instead of starting a duplicate.
phynite-lab --no-open --port 3000 --data-dir /path/to/workspace
phynite-lab status --data-dir /path/to/workspace
phynite-lab doctor --data-dir /path/to/workspace
phynite-lab stop --data-dir /path/to/workspaceUpdate without losing projects
The local app may show an update notice after checking https://registry.npmjs.org/phynite-lab/latest. A successful check is cached for up to six hours; an unavailable or invalid response is retried after about five minutes. The check sends no project data or credentials, does not install anything automatically, and never blocks local work while offline.
- Finish or cancel active jobs and stop the current instance.
- Run the npm update command from the same Node installation that owns the global package.
- Start the app again and open Settings → Compute to confirm the runtime capabilities remain available.
- If startup fails, run phynite-lab doctor and inspect the logs in the selected data directory; reinstalling the package does not remove ~/.phynite-lab.
npm install -g phynite-lab@latest
phynite-lab --versionCommon npm startup fixes
| Symptom | Check |
|---|---|
| Node version rejected | Run node --version and install a Node.js version satisfying >=22.13.0. |
| Missing runtime package | Reinstall with optional dependencies enabled; check the package target reported by doctor. |
| Port already used | Use --no-open, follow the printed port, or choose --port with a free value. |
| Projects are missing | Use the original --data-dir; each directory is an independent workspace. |
| Startup service stopped | Run status and doctor, then read logs/<service>.log in the data directory. |
| Update is unavailable | Continue offline, check npm/network later, and retry; the notice is informational. |