How Install Works
The Install Prompt
Open any AI and paste:What Happens During Install
ldm install does these things in order:
- Self-update. Checks npm for a newer version of itself. Updates first, then re-runs with new code.
- System scan. Reads
~/.ldm/extensions/,~/.openclaw/extensions/, Claude Code MCP config, CLI binaries on PATH. - Catalog check. Matches installed tools against the catalog. Shows what’s available, what’s behind.
- npm version check. Checks every installed tool against npm for newer versions.
- Update. Clones from GitHub, builds if needed, deploys to extension dirs, registers connections/hooks/skills.
- Health check. Verifies CLIs exist, no broken symlinks, no stale configs.
- Cleanup. Removes staging dirs, prunes ghost entries from registry.
Dry Run
Always preview first:Installing a Specific Tool
What Gets Installed Where
| Interface | Location |
|---|---|
| Tools | ~/.ldm/extensions/<name>/ |
| CLIs | /opt/homebrew/bin/<name> (via npm -g) |
| Connection Points | Registered in ~/.claude.json |
| Automation Hooks | Registered in ~/.claude/settings.json |
| Background Integrations | Deployed to ~/.openclaw/extensions/ |
| Skills | Deployed to ~/.openclaw/skills/ + ~/.claude/skills/ |
| Rules | Deployed from ~/.ldm/shared/rules/ to ~/.claude/rules/ |
| Commands | Deployed from ~/.ldm/shared/commands/ to ~/.claude/commands/ |
| AI Definitions | Deployed from ~/.ldm/agents/ to ~/.claude/agents/ |
Rules and Commands Deployment
ldm install syncs rules, commands, and skills from ~/.ldm/ to each AI app:
- Reads
~/.ldm/shared/rules/… copies to~/.claude/rules/ - Reads
~/.ldm/agents/<agent>/rules/… copies to~/.claude/rules/(AI-specific) - Reads
~/.ldm/shared/commands/… copies to~/.claude/commands/ - Reads
~/.ldm/shared/skills/… copies to~/.claude/skills/
workspace/TOOLS.md. Skills go to extensions/.
Edit at the ~/.ldm/ level. The AI app gets the result.
Old Versions
Never deleted. Moved to~/.ldm/_trash/ with a timestamp. Recoverable.