morph-install

name	morph-install
description	Install, configure, update, or verify Morph for Codex, Claude Code, Hermes Agent, OpenCode, or OpenClaw from the morph-public repository. Use when the user asks to set up Morph or connect its skill and MCP server. Do not use for creating or editing product stories.

Install Morph

Install Morph from the current ychampion/morph-public checkout. Keep the repository unchanged unless a documented setup command is genuinely broken and the user explicitly asked for implementation work.

1. Identify the host

Determine which agent is running this task from the current environment and available CLI. Supported values are:

• codex
• claude-code
• hermes
• opencode
• openclaw

Do not guess when more than one host CLI is installed. Use the host that owns the current agent session. If that cannot be established, report the ambiguity and show the supported values.

2. Check prerequisites

Confirm:

node --version
npm --version
ffmpeg -version
ffprobe -version

Node.js must be 22 or newer. FFmpeg and FFprobe must be available with H.264 support. Read configuration.md for paths and host behavior. Read troubleshooting.md only when a check fails.

3. Inspect the plan

Run the host-specific dry run first:

npm run install:agent -- --agent <host> --dry-run

Review the reported runtime path, skill path, and registration commands. Do not continue if the plan targets an unrelated existing directory or a different agent host.

4. Install

Run:

npm run install:agent -- --agent <host>

The command performs setup, builds the runtime, installs the shared Morph skill, registers the local MCP server, and verifies the installed copy. Do not recreate these steps with ad hoc copies or hand-written configuration when the installer supports the host.

5. Verify discovery

The installer verifies the runtime and host registration. Then verify that the current host can discover the morph skill. Reload plugins or start a new agent session when the host caches skills.

Do not record a website as an installation test. Use the deterministic doctor/runtime checks only.

6. Report

Report:

• the detected host;
• the installed runtime and skill locations;
• prerequisite, build, doctor, MCP startup, and host-registration results;
• whether a reload or new session is required;
• any step that could not be verified in the current environment.

Never claim another host was verified merely because its generated configuration is valid.