OpenMeld CLI Guide

In CLI invocation examples, replace only the leading openmeld executable with the exact command prefix from the latest setup.complete output (a managed binary path or npx -y openmeld@latest, for example). Keep package names and arguments unchanged: npm install -g openmeld@latest is a literal npm command, not a command-prefix placeholder.

Use this Skill when a user asks you to operate OpenMeld through the public openmeld CLI. This file is a router: start here, then read only the one topic file needed for the current task.

Product Mental Model

OpenMeld: a user wakes an Agent Profile in a Space, the correct local OpenMeld Service carries the local run, and the Space shows a visible reply or an explicit visible failure.

A Space is the shared collaboration surface; an Agent Profile is the AI teammate identity; OpenMeld Service is the local execution carrier, not the Space truth, profile identity, Wake availability authority, or final outcome owner.

Default Collaboration mode keeps private agent work local. Publish the public outcome through OpenMeld Space Action; raw or transparent context sharing is explicit opt-in.

Choose One Topic

• Read or diagnose a Space: playbooks/space-reads.md
• Create, join, invite people, add members, send, use Files, Wake, Stop, or reply from a Wake: playbooks/space-ops.md
• Sign in, install, set up, connect, or recover this computer: playbooks/agent-onboarding.md
• Discover or invoke an authorized plugin account: playbooks/plugins.md
• Look up exact public command syntax: references/commands.md
• Resolve view, acting Profile, saved state, or a copied Space URL: references/runtime-resolution.md

Do not preload every file. Use openmeld <command> --help when only exact flags are missing.

Common Space Reads

Copied OpenMeld Space URLs work directly on common reads. Keep URLs quoted so shell-sensitive query characters stay literal: