# Install OpenMotion 0.6.4-test.9

Current test version: 0.6.4-test.9. Commands follow the npm test tag for the complete application `@openmotion/app@test` on the **test** software channel. It includes MCP, the built Studio and five Skills. The default template environment is **dev**: new test versions embed DEV defaults, stable versions embed prod, and previously published versions keep their original environment.

## Instructions for the Agent

1. Collect OS/CPU, Node.js/npm versions and the current Agent identity together, using the host's supplied context where available. Node.js 22.18+ with npm and the Agent must already be installed. Supported native targets: darwin/arm64 (26.0+), win32/x64 (Windows 11+). Do not claim support for another target from package-download success.
2. Select the current host explicitly: `codex` (Codex), `claude` (Claude Code), `deepseek` (DeepSeek Harness) or `workbuddy` (WorkBuddy). An explicit user selection takes precedence. Do not infer the current host from which CLIs happen to be installed. Ask only when the current host or required profile cannot be established. Configure only that host; preserve projects, credentials and unrelated MCP/Skills settings.
3. For a test candidate, use a separate host profile, application home, project data and Skills directory. Keep those paths and reuse them for prepare and future reconnects. The [platform installation recipes](https://github.com/nexu-io/html-anything/blob/5102a6cc6668e7c798f5ac72a058bc15eff82a9d/docs/npm-installation.md) describe the actual supported options. Do not run a test candidate into the user's daily profile by default.
4. Choose exactly one setup command below, applying the test isolation paths first when required. Setup starts checked video-component downloads in the background. Do not wait for prepare to connect MCP, create/edit projects or open ordinary preview. Studio shows preparation status and retry; media import, automated capture and export require their respective components. Follow the selected host's discovery/reload mechanism. Compatible phase-one updates can keep existing connections; reconnect closed or incompatible transports. Confirm the application version, template environment, eleven public Tools and five Skills through that host, including an actual `motion_get_project` call. Registration alone does not prove loading.
5. Report the result and any failed step. Introduce the available capabilities and wait for the user's next request. Installation does not authorize generating a video or calling a paid model.

## Choose the selected host's setup command

The commands below show normal installations. For test candidates, apply the separate configuration/profile, home, data and Skills paths from the [platform recipes](https://github.com/nexu-io/html-anything/blob/5102a6cc6668e7c798f5ac72a058bc15eff82a9d/docs/npm-installation.md) first. Run only the selected row.

| Current Agent | Setup command | Host-specific selection |
| --- | --- | --- |
| Codex | `npx --yes --package "@openmotion/app@test" openmotion setup --host codex` | Preserve the selected `CODEX_HOME` and Skills root. |
| Claude Code | `npx --yes --package "@openmotion/app@test" openmotion setup --host claude` | Preserve the selected `CLAUDE_CONFIG_DIR` and Skills root. |
| DeepSeek Harness | `npx --yes --package "@openmotion/app@test" openmotion setup --host deepseek --profile PROFILE` | Replace `PROFILE` with the actual selected profile from the host context; do not guess `web` or `desktop`. The standard macOS Desktop CLI is detected even when `dsh` is absent from PATH; use `--dsh` for another executable location. |
| WorkBuddy | `npx --yes --package "@openmotion/app@test" openmotion setup --host workbuddy` | Preserve the selected `WORKBUDDY_CONFIG_DIR` and Skills root. |

Optional: explicitly wait for all video components or retry preparation for the same installation:

```sh
npx --yes --package "@openmotion/app@test" openmotion prepare
```

Repeat an explicit `--home` from setup on prepare. Setup installs the selected host's MCP and Skills; a second installer or application/manifest download is unnecessary. Use `openmotion --help`, `setup --help` or `prepare --help` from the installed package for supported options. Inspect installer source or host internals only to investigate a concrete failure; a missing CLI on PATH alone is not a reason to create a wrapper.

## Runtime and environment

Setup copies the checked application into a managed writable directory and installs its locked production npm dependencies. The application and user projects do not run from the temporary npx cache. Setup starts a detached preparation worker for the platform's independent native archives concurrently: browser/FFmpeg/ffprobe separately on macOS, browser/combined media on Windows. The local backend and Studio start without waiting. Studio displays per-component download/verification/extraction/checking status and retries failed components. Installers, MCP and Studio join shared cache locks rather than downloading again. An explicit prepare waits for all components and reports failure; successful checked components remain reusable. No export starts automatically after preparation. This is not an offline package.

There is no persisted switch-environment command in this version. Test versions embed DEV defaults and use an environment-specific installation; stable versions embed prod. DEV access still requires the service network/authentication. A public npm package does not grant access or bundle private catalog contents. When changing environment, use a separate home/data/profile; merely setting an environment variable while running setup does not configure a later desktop Agent. Do not silently fall back from one environment to another.

## Upgrade, recovery and feedback

Record and pin the installed version when reproducing an issue. Before an upgrade, back up project data and preserve the same installation/data paths. Compatible phase-one updates retain existing connections and active exports. For an incompatible protocol, finish active exports before updating only this installation's connection and idle backend together; reconnect after setup/prepare. Refresh host discovery for new Tools or Skills, and preserve unrelated settings. Older applications may not read newer data formats: compatible reinstall or backup restoration requires separate verification. Moving a server-side default does not downgrade installed clients.

Include the exact version, OS/CPU, Node/Agent versions, template environment, project/revision, reproduction and redacted logs in a report. Installation, real Agent creation, technical MP4 export and human audiovisual acceptance are separate results.

Guide version identity (the npm tag may advance): source `5102a6cc6668e7c798f5ac72a058bc15eff82a9d`; npm tgz SHA256 `5df0e4cabd7fcad47f7deab8d13e144b523672ba67efe62470911c65751305c4`. [Source and installation details](https://github.com/nexu-io/html-anything/blob/5102a6cc6668e7c798f5ac72a058bc15eff82a9d/docs/npm-installation.md).