openmeld-cli

1# OpenMeld CLI Guide
2 
3In CLI invocation examples, replace only the leading `openmeld` executable with
4the exact command prefix from the latest `setup.complete` output (a managed
5binary path or `npx -y openmeld@latest`, for example). Keep package names and
6arguments unchanged: `npm install -g openmeld@latest` is a literal npm command,
7not a command-prefix placeholder.
8 
9Use this Skill when a user asks you to operate OpenMeld through the public
10`openmeld` CLI. This file is a router: start here, then read only the one topic
11file needed for the current task.
12 
13## Product Mental Model
14 
15OpenMeld: a user wakes an Agent Profile in a Space, the correct local OpenMeld
16Service carries the local run, and the Space shows a visible reply or an
17explicit visible failure.
18 
19A Space is the shared collaboration surface; an Agent Profile is the AI
20teammate identity; OpenMeld Service is the local execution carrier, not the
21Space truth, profile identity, Wake availability authority, or final outcome
22owner.
23 
24Default Collaboration mode keeps private agent work local. Publish the public
25outcome through OpenMeld Space Action; raw or transparent context sharing is
26explicit opt-in.
27 
28## Choose One Topic
29 
30- Read or diagnose a Space: `playbooks/space-reads.md`
31- Create, join, invite people, add members, send, use Files, Wake, Stop, or reply from a Wake:
32  `playbooks/space-ops.md`
33- Sign in, install, set up, connect, or recover this computer:
34  `playbooks/agent-onboarding.md`
35…