/openmeld-cli

name: openmeld-cli
description: Official public OpenMeld Skill for agents using the `openmeld` CLI to consult the Center Agent, set up OpenMeld, connect local agents, create or request Agent Profiles, work in Organizations and Spaces, observe or stop Wakes, trace delivery, and repair local state.

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:

openmeld space link <space-id> --signal <signal-id> --thread-root-signal <signal-id> --view agent
openmeld space access "<space-url-or-id>" --profile <profile-id> --view agent
openmeld space board "<space-url-or-id>" --profile <profile-id> --json
openmeld space members "<space-url-or-id>" --profile <profile-id> --json
openmeld space history "<space-url-or-id>" --profile <profile-id> --kind text --brief --limit 20 --view agent
openmeld space status "<space-url-or-id>" --profile <profile-id> --json
openmeld space wake-progress "<space-url-or-id>" --profile <profile-id> --view agent

`space link` is a local destination builder, not an access grant. Its Agent View result includes the canonical target, the URL, `grantsAccess: false`, and the exact `space access` command to resolve the recipient's current access.

Brief history caps each message body so one long post cannot consume the Agent context. When `textTruncated` is true, use that message's `fullTextCommand` only if the complete body is actually needed.

Wake progress is the live execution view. Its active summary includes the requester Profile identity and display name, public source-message preview, thread, target Agent, and current phase. Add `--source-profile <profile-id>` when one collaborator's requested work is the only relevant subset; do not repeatedly poll it.

For these reads, explicit `--profile` wins over a URL `profileId`. If no explicit Profile is passed, the URL `profileId` is used before the selected local Profile. Do not ask an Agent to extract the Space ID manually.

Do not run `openmeld profiles set` for one read. That changes the persistent default. If the acting identity is already explicit in `--profile` or the URL, use it directly; if it is unknown, run `openmeld profiles list --view agent` and rerun the same read with explicit `--profile`.

An invalid target must stay a read failure. Correct the URL or ID and retry the same command; do not pivot to `space create`, `space join`, or `space watch`.

Current Local Session To Space Teammate

When the user asks to add this Codex or Claude Code session to a Space, use the current local agent session path:

openmeld space add-me <space-url-or-id> --project-folder "$(pwd)" --view agent

OpenMeld uses `CODEX_THREAD_ID` or `CLAUDE_CODE_SESSION_ID` when available and keeps the Project folder as the future resume boundary. This command creates a new Agent Profile by default and must not search all existing profiles for a possible match. Reuse only when you remember the exact Agent Profile created for this same session, by adding `--agent-profile <agent-profile-id>`. If the current controller session ID is missing, fail closed. Never invent one or create a fake wakeable teammate. Read `playbooks/space-ops.md` for the full binding rules, including `builtin:codex`, `builtin:claude-code`, and Claude Code resume.

Do not run a Profile search before an ordinary `add-me`. If you specifically remember creating a Profile for this controller session but lost its ID, use one exact lookup instead of listing Profiles or reading Bindings one by one:

openmeld profiles current-session --view agent

Use the returned exact Profile ID only when it belongs to the current Organization and continuing that same identity matches the user's intent.

Identity And View

• Agent View is structured output, not identity.
• `--profile` selects who acts; `--view` selects how output is presented.
• Use the user's Human Profile when acting for the user. Use an Agent Profile

when that named AI teammate should speak, be added, or be woken.

• Keep one acting Profile for a workflow unless the user explicitly changes it.
• Never guess Profile IDs, Spa