@wipcomputer/wip-ldm-os 0.4.44 → 0.4.46

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/SKILL.md +242 -88
  2. package/package.json +1 -1
package/SKILL.md CHANGED
@@ -5,7 +5,7 @@ license: MIT
5
5
  interface: [cli, skill]
6
6
  metadata:
7
7
  display-name: "LDM OS"
8
- version: "0.4.44"
8
+ version: "0.4.46"
9
9
  homepage: "https://github.com/wipcomputer/wip-ldm-os"
10
10
  author: "Parker Todd Brooks"
11
11
  category: infrastructure
@@ -30,22 +30,181 @@ metadata:
30
30
  compatibility: Requires git, npm, node. Node.js 18+.
31
31
  ---
32
32
 
33
- # LDM OS
33
+ # LDM OS: Learning Dreaming Machines
34
34
 
35
- ## CRITICAL: Bootstrap (read this first)
35
+ ## All your AIs. One system.
36
36
 
37
- If `ldm` is not installed, run this BEFORE anything else:
37
+ You use Claude Code, GPT, OpenClaw, others. They don't share memory. They don't know each other. They don't know how to work together.
38
+
39
+ LDM OS is the shared infrastructure layer. Install it once and every AI you use gets:
40
+
41
+ - **Identity** ... each AI gets its own behavior, personality, and skills
42
+ - **Memory** ... shared memory across all your AIs, secure, sovereign, yours to take anywhere
43
+ - **Ownership** ... every interaction, every memory, across every AI you use is yours, portable, encrypted, never locked in
44
+ - **Collaboration** ... your AIs communicate, share tools, and work together
45
+ - **Compatibility** ... any skill, plugin, or tool works with all your AIs. Install once, use everywhere.
46
+ - **Payments** ... your AI hits a paywall, you approve it with Face ID, Apple Pay for your AI
47
+
48
+ ## Included Skills
49
+
50
+ Ships with LDM OS.
51
+
52
+ **Bridge**
53
+ - Cross-platform agent bridge. Enables Claude Code CLI to talk to OpenClaw CLI without a human in the middle.
54
+
55
+ **Universal Installer**
56
+ - Point any skill, application, or plugin at any AI running LDM OS, and it will convert those skills to work with all of your AIs.
57
+ - Build applications that work with any AI, even ones that don't have LDM OS.
58
+
59
+ **Shared Workspace**
60
+ - One directory for all your AIs. Memories, tools, identity files, boot config. Every AI you use reads from and writes to the same place.
61
+ - Lives in one folder on your computer. Easy to back up, easy to move, easy to own.
62
+
63
+ **System Pulse**
64
+ - Is everything working? What's installed? What needs fixing? A complete picture of your AI setup in seconds.
65
+
66
+ **Recall**
67
+ - Every session, your AI starts with full context. Identity, memory, tools, what happened yesterday. No blank slates. No repeating yourself.
68
+
69
+ **LUME**
70
+ - Language for Unified Memory and Emergence. A memory language for AI agents to document their own learning and maintain continuity across sessions. Not a programming language. A way for your AI to write memories to itself, retrieve past learnings, track unfinished thoughts, and pass context between sessions.
71
+
72
+ ## Optional Skills
73
+
74
+ The OS connects your AIs. Add-ons are what they actually use. Each one is a full product that plugs into LDM OS and works with every AI you run.
75
+
76
+ **Memory Crystal** (recommended)
77
+ - All your AI tools. One shared memory. Private, searchable, sovereign. Memory Crystal lets all your AIs remember you ... together. You use multiple AIs. They don't talk to each other. They can't search what the others know. Memory Crystal fixes this. All your AIs share one memory. Searchable and private. Anywhere in the world.
78
+ - *Stable* ... `wipcomputer/memory-crystal`
79
+
80
+ **AI DevOps Toolbox**
81
+ - Your AI writes code. But does it know how to release it? Check license compliance? Protect your identity files? Sync private repos to public? Follow a real development process? AI DevOps Toolbox is the complete toolkit. Built by a team of humans and AIs shipping real software together.
82
+ - *Stable* ... `wipcomputer/wip-ai-devops-toolbox`
83
+
84
+ **1Password**
85
+ - 1Password secrets for AI agents. Headless, no biometric popups, service account driven.
86
+ - *Stable* ... `wipcomputer/wip-1password`
87
+
88
+ **Markdown Viewer**
89
+ - Live markdown viewer for AI pair-editing. Updates render instantly in any browser.
90
+ - *Stable* ... `wipcomputer/wip-markdown-viewer`
91
+
92
+ **xAI Grok**
93
+ - xAI Grok API. Search the web, search X, generate images, generate video.
94
+ - *Stable* ... `wipcomputer/wip-xai-grok`
95
+
96
+ **X Platform**
97
+ - X Platform API. Read posts, search tweets, post, upload media.
98
+ - *Stable* ... `wipcomputer/wip-xai-x`
99
+
100
+ **Dream Weaver Protocol**
101
+ - Memory consolidation protocol for AI agents with bounded context windows. A practical guide for remembering memories.
102
+ - `wipcomputer/dream-weaver-protocol`
103
+
104
+ **Agent Pay**
105
+ - Micropayments for AI agents. Your AI hits a paywall, you approve it with Face ID. Apple Pay for your AI.
106
+ - *Coming Soon*
107
+
108
+ **OpenClaw**
109
+ - Open-source agent runtime. Run AI agents 24/7 with identity, memory, and tool access. The existence proof for LDM OS.
110
+ - `openclaw/openclaw`
111
+
112
+ ---
113
+
114
+ ## Step 1: Check if LDM OS is already installed
115
+
116
+ **Always check first. Never assume.**
38
117
 
39
118
  ```bash
40
- npm install -g @wipcomputer/wip-ldm-os
119
+ which ldm && ldm --version 2>/dev/null
41
120
  ```
42
121
 
43
- Then check: `ldm --version`. If that works, proceed with `ldm install --dry-run`.
122
+ If you cannot run shell commands (e.g. you are GPT, Grok, Claude macOS, or another AI without terminal access), tell the user: "I can't run commands from here. Open a terminal-capable AI (like Claude Code) and paste the install prompt there. Or run `which ldm` in your terminal and tell me the result."
44
123
 
45
- If npm/node is not installed, the user needs Node.js 18+ from https://nodejs.org first.
124
+ This determines everything. Branch on the result:
125
+
126
+ ---
127
+
128
+ ## If LDM OS IS installed (ldm command exists)
129
+
130
+ **Do NOT re-explain what LDM OS is.** The user already knows. Show them what they have and what's new.
131
+
132
+ ### Run status
133
+
134
+ ```bash
135
+ ldm status 2>&1
136
+ ```
137
+
138
+ `ldm status` checks the CLI and all extensions against npm. It shows:
139
+ - CLI version and whether a newer version exists
140
+ - Extension count and how many have updates available
141
+ - Specific version diffs for each outdated extension
142
+
143
+ **Use the output of `ldm status` as your summary.** Do not say "up to date" if `ldm status` shows updates available.
144
+
145
+ ### Present what changed
146
+
147
+ Show a table of components with updates:
148
+
149
+ ```
150
+ | Component | Current | Available | Package |
151
+ |-----------|---------|-----------|---------|
152
+ | LDM OS CLI | v0.4.41 | v0.4.45 | @wipcomputer/wip-ldm-os |
153
+ | wip-branch-guard | v1.9.44 | v1.9.51 | @wipcomputer/wip-branch-guard |
154
+ ```
155
+
156
+ **Always show a table.** Never collapse updates into a paragraph or bullet list. Every update gets its own row.
157
+
158
+ ### Show what changed per component
159
+
160
+ **Do NOT skip this step.** Before asking if the user wants to install, you MUST fetch and show release notes for every component with an update.
161
+
162
+ For each component with an update, fetch the release notes and summarize what actually changed:
163
+
164
+ ```bash
165
+ # For each component with an update:
166
+ gh release list --repo wipcomputer/<repo-name> --limit 5 --json tagName,name --jq '.[]'
167
+ # Then for each release between current and available:
168
+ gh release view <tag> --repo wipcomputer/<repo-name> --json body --jq .body
169
+ ```
170
+
171
+ Show 2-3 bullet points per component summarizing the release notes. The user needs to know WHAT changed, not just THAT a version number moved.
172
+
173
+ Then answer:
174
+ 1. **What changed for this AI?** New rules, boot config changes, CLAUDE.md updates.
175
+ 2. **What changed across all my AIs?** Shared rules, shared prompts, new extensions.
176
+
177
+ ### Ask
178
+
179
+ - Do you have questions?
180
+ - Want to see a dry run?
181
+
182
+ If they say yes:
183
+ ```bash
184
+ ldm install --dry-run
185
+ ```
186
+
187
+ **Don't install anything until the user says "install".**
188
+
189
+ When they say install:
190
+ ```bash
191
+ npm install -g @wipcomputer/wip-ldm-os@latest # CLI update
192
+ ldm install # update all registered extensions
193
+ ldm doctor # verify everything works
194
+ ```
195
+
196
+ Updates deploy new code without touching data. crystal.db, agent files, secrets, and state are never overwritten.
46
197
 
47
198
  ---
48
199
 
200
+ ## If LDM OS is NOT installed (ldm command not found)
201
+
202
+ Now explain. The user is new.
203
+
204
+ ### What is LDM OS?
205
+
206
+ Learning Dreaming Machines. All your AIs. One system.
207
+
49
208
  You use Claude Code, GPT, OpenClaw, others. They don't share memory. They don't know each other. They don't know how to work together.
50
209
 
51
210
  LDM OS is the shared infrastructure layer. Install it once and every AI you use gets:
@@ -57,60 +216,77 @@ LDM OS is the shared infrastructure layer. Install it once and every AI you use
57
216
  - **Compatibility** ... any skill, plugin, or tool works with all your AIs. Install once, use everywhere.
58
217
  - **Payments** ... your AI hits a paywall, you approve it with Face ID, Apple Pay for your AI
59
218
 
60
- ## Platform Compatibility
219
+ ### What does it install?
61
220
 
62
- | Interface | Requires | Examples |
63
- |-----------|----------|----------|
64
- | CLI | Shell access (run bash/node commands) | `ldm init`, `ldm install`, `ldm doctor` |
65
- | Skill | SKILL.md file (works in Claude Code and OpenClaw) | You're reading it right now |
221
+ - `~/.ldm/extensions/` ... where tools and plugins live
222
+ - `~/.ldm/agents/` ... each AI gets its own identity, personality, and memory here
223
+ - `~/.ldm/memory/` ... shared memory across all your AIs (including the Memory Crystal)
224
+ - `~/.ldm/state/` ... configuration and sync state
225
+ - `~/.ldm/shared/rules/` ... dev conventions deployed to every AI harness
66
226
 
67
- **Built and tested on:**
68
- - **Claude Code CLI** ... full support (shell, CLI)
69
- - **OpenClaw** ... full support (shell, CLI)
227
+ ### What ships with it?
70
228
 
71
- ## Operating Rules
229
+ LDM OS includes six built-in skills:
72
230
 
73
- **Check before you run.** Before running any `ldm` command, check if it's installed: `which ldm`. If not found, tell the user: "I can run `ldm install --dry-run` to show you exactly what will change, but first I need to install the LDM OS CLI. That's one npm package (`npm install -g @wipcomputer/wip-ldm-os`) that gives us the `ldm` command. It doesn't install anything else until you say so." Never show the user a "command not found" error you already knew would happen.
231
+ - **Bridge** ... cross-platform agent bridge. Your AIs talk to each other without a human in the middle.
232
+ - **Universal Installer** ... point any skill at any AI running LDM OS and it converts those skills to work with all your AIs. Build applications that work with any AI, even ones that don't have LDM OS.
233
+ - **Shared Workspace** ... one directory for all your AIs. Memories, tools, identity files, boot config. Easy to back up, easy to move, easy to own.
234
+ - **System Pulse** ... is everything working? What's installed? What needs fixing? A complete picture of your AI setup in seconds.
235
+ - **Recall** ... every session, your AI starts with full context. Identity, memory, tools, what happened yesterday. No blank slates. No repeating yourself.
236
+ - **LUME** ... Language for Unified Memory and Emergence. A memory language for AI agents to document their own learning and maintain continuity across sessions.
74
237
 
75
- **Always dry-run first.** Before installing or making changes, run with `--dry-run` so the user can see exactly what will happen. Only proceed when the user explicitly says to.
238
+ ### What changes for this AI?
76
239
 
77
- **Never touch sacred data.** The installer never overwrites: crystal.db, agent data, secrets, state files. Code gets updated. Data stays.
240
+ - Boot sequence reads from `~/.ldm/agents/` (identity, memory, daily logs)
241
+ - Rules deployed to `~/.claude/rules/` (git conventions, security, release pipeline)
242
+ - Extensions like Memory Crystal, wip-release are managed centrally
243
+ - Stop hooks write to crystal and daily logs after every turn
244
+
245
+ ### What changes across all my AIs?
78
246
 
79
- ## Install
247
+ - Shared memory (crystal.db) accessible to every AI
248
+ - Shared rules (same conventions everywhere)
249
+ - Shared extensions (install once, every AI sees it)
250
+ - Agent identity (each AI is its own entity with its own prefix)
80
251
 
81
- ### Step 1: Install LDM OS
252
+ ### Ask
82
253
 
254
+ - Do you have questions?
255
+ - Want to see a dry run?
256
+
257
+ If they say yes, install the CLI first:
83
258
  ```bash
84
259
  npm install -g @wipcomputer/wip-ldm-os
260
+ ```
261
+
262
+ If npm/node is not installed, the user needs Node.js 18+ from https://nodejs.org first.
263
+
264
+ Then dry run:
265
+ ```bash
85
266
  ldm init --dry-run
86
267
  ```
87
268
 
88
- Show the user the dry run output. Explain what it creates:
89
- - `~/.ldm/extensions/` ... where tools and plugins live
90
- - `~/.ldm/agents/` ... each AI gets its own identity, personality, and memory here
91
- - `~/.ldm/memory/` ... shared memory across all your AIs
92
- - `~/.ldm/state/` ... configuration and sync state
269
+ **Don't install anything until the user says "install".**
93
270
 
94
- When the user approves:
271
+ When they say install:
95
272
  ```bash
96
273
  ldm init
97
274
  ```
98
275
 
99
- ### Step 2: Install Skills
276
+ ### Install Skills
100
277
 
101
- LDM OS ships with a skill catalog. Show the user what's available:
278
+ After LDM OS is initialized, show the user the optional skills catalog:
102
279
 
103
- | Skill | What it is | Status |
104
- |-------|-----------|--------|
105
- | **Memory Crystal** (recommended) | Persistent memory. Search, capture, consolidation. | Stable |
106
- | **AI DevOps Toolbox** | Release, deploy, license, repo management. | Stable |
107
- | **1Password** | 1Password secrets for AI agents. | Stable |
280
+ | Skill | What it does | Status |
281
+ |-------|-------------|--------|
282
+ | **Memory Crystal** (recommended) | All your AIs share one memory. Private, searchable, sovereign. | Stable |
283
+ | **AI DevOps Toolbox** | Release, deploy, license, repo management. The complete dev toolkit. | Stable |
284
+ | **1Password** | 1Password secrets for AI agents. Headless, service account driven. | Stable |
108
285
  | **Markdown Viewer** | Live markdown viewer for AI pair-editing. | Stable |
109
- | **xAI Grok** | xAI Grok API. Search the web, search X, generate images. | Stable |
286
+ | **xAI Grok** | xAI Grok API. Search the web, search X, generate images, generate video. | Stable |
110
287
  | **X Platform** | X Platform API. Read posts, search tweets, post, upload media. | Stable |
111
- | **OpenClaw** | AI agent platform. Run AI agents 24/7 with identity, memory, and tool access. | Stable |
112
- | **Dream Weaver Protocol** | Memory consolidation protocol for AI agents. | Stable |
113
- | **Bridge** | Cross-platform agent bridge. Claude Code to OpenClaw communication. | Stable |
288
+ | **Dream Weaver Protocol** | Memory consolidation for AI agents with bounded context windows. | Stable |
289
+ | **Agent Pay** | Micropayments for AI agents. Apple Pay for your AI. | Coming Soon |
114
290
 
115
291
  To install a skill:
116
292
  ```bash
@@ -122,17 +298,39 @@ Show the dry run. When approved:
122
298
  ldm install wipcomputer/memory-crystal
123
299
  ```
124
300
 
125
- The installer detects what a repo supports (CLI, MCP Server, OpenClaw Plugin, Skill, CC Hook, Module) and deploys each interface to the right location automatically.
126
-
127
- **Note:** Skills installed before LDM OS (via `crystal init`, `wip-install`, or manual setup) may not appear in the registry. Run `ldm install <org/repo>` to re-register them.
128
-
129
- ### Step 3: Verify
301
+ ### Verify
130
302
 
131
303
  ```bash
132
304
  ldm doctor
133
305
  ```
134
306
 
135
- This checks: LDM root exists, version.json valid, registry intact, all extensions deployed, hooks configured, MCP servers registered.
307
+ ---
308
+
309
+ ## Platform Compatibility
310
+
311
+ | Interface | Requires | Examples |
312
+ |-----------|----------|----------|
313
+ | CLI | Shell access (run bash/node commands) | `ldm init`, `ldm install`, `ldm doctor` |
314
+ | Skill | SKILL.md file (works in Claude Code and OpenClaw) | You're reading it right now |
315
+
316
+ **Built and tested on:**
317
+ - **Claude Code CLI** ... full support (shell, CLI, hooks, MCP)
318
+ - **OpenClaw** ... full support (shell, CLI, plugins, hooks)
319
+
320
+ **Works with (read-only, no shell):**
321
+ - **GPT** ... can read the skill and explain LDM OS, but cannot run install commands
322
+ - **Grok** ... can read the skill and explain LDM OS, but cannot run install commands
323
+ - **Claude macOS** ... can read the skill and explain LDM OS, but cannot run install commands
324
+
325
+ If you are an AI without shell access: explain LDM OS using this document, then tell the user to open a terminal-capable AI (Claude Code or OpenClaw) to run the install.
326
+
327
+ ## Operating Rules (both paths)
328
+
329
+ **Check before you run.** Before running any `ldm` command, check if it's installed: `which ldm`. If not found, tell the user: "I need to install the LDM OS CLI first. That's one npm package (`npm install -g @wipcomputer/wip-ldm-os`) that gives us the `ldm` command. It doesn't install anything else until you say so." Never show the user a "command not found" error you already knew would happen.
330
+
331
+ **Always dry-run first.** Before installing or making changes, run with `--dry-run` so the user can see exactly what will happen. Only proceed when the user explicitly says to.
332
+
333
+ **Never touch sacred data.** The installer never overwrites: crystal.db, agent data, secrets, state files. Code gets updated. Data stays.
136
334
 
137
335
  ## Commands
138
336
 
@@ -163,40 +361,6 @@ When you run `ldm install`, it automatically detects what a repo supports:
163
361
 
164
362
  No manual configuration needed. Point it at a repo and it figures out the rest.
165
363
 
166
- ## Update
167
-
168
- If LDM OS is already installed, run `ldm status` BEFORE presenting the summary to the user:
169
-
170
- ```bash
171
- ldm status 2>&1
172
- ```
173
-
174
- `ldm status` checks both the CLI and all extensions against npm. It shows:
175
- - CLI version and whether a newer version exists
176
- - Extension count and how many have updates available
177
- - Specific version diffs for each outdated extension
178
-
179
- **Use the output of `ldm status` as your summary.** Do not say "up to date" if `ldm status` shows updates available. Do not make your own summary without running `ldm status` first.
180
-
181
- When the user asks for a dry run or wants to update, run `ldm install --dry-run` and display the results as a **table**:
182
-
183
- ```
184
- | Extension | Current | Available | Package |
185
- |-----------|---------|-----------|---------|
186
- | wip-branch-guard | v1.9.30 | v1.9.36 | @wipcomputer/wip-branch-guard |
187
- | memory-crystal | v0.7.24 | v0.7.26 | @wipcomputer/memory-crystal |
188
- ```
189
-
190
- **Always show a table.** Never collapse updates into a paragraph or bullet list. Every update gets its own row. Show ALL updates, not a summary.
191
-
192
- When the user says "install":
193
- ```bash
194
- ldm install # update all registered extensions
195
- ldm doctor # verify everything works
196
- ```
197
-
198
- Updates deploy new code without touching data. crystal.db, agent files, secrets, and state are never overwritten.
199
-
200
364
  ## Part of LDM OS
201
365
 
202
366
  LDM OS is the runtime. Skills plug into it:
@@ -212,13 +376,3 @@ LDM OS is the runtime. Skills plug into it:
212
376
  - **Bridge** ... `wipcomputer/wip-bridge`
213
377
 
214
378
  Run `ldm install` anytime to add more skills.
215
-
216
- ## Claude Code Marketplace
217
-
218
- If you're running Claude Code, you can browse and install all LDM OS plugins available from WIP Computer:
219
-
220
- ```
221
- /plugin marketplace add wipcomputer/claude-plugins
222
- ```
223
-
224
- This adds LDM OS skills to Claude Code's Discover tab alongside Anthropic's official plugins. Install any skill with `/plugin install`.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@wipcomputer/wip-ldm-os",
3
- "version": "0.4.44",
3
+ "version": "0.4.46",
4
4
  "type": "module",
5
5
  "description": "LDM OS: identity, memory, and sovereignty infrastructure for AI agents",
6
6
  "engines": {