openmeld 0.3.143 → 0.3.144

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://www.schemastore.org/package.json",
   "name": "openmeld",
-  "version": "0.3.143",
+  "version": "0.3.144",
   "openMeldReleaseDate": "2026-09-02",
   "description": "OpenMeld CLI - https://openmeld.ai",
   "license": "MIT",

package/skills/openmeld-cli/SKILL.md

@@ -72,10 +72,14 @@ 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. 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.
+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.
 
 ## Identity And View
 

package/skills/openmeld-cli/playbooks/space-ops.md

@@ -69,9 +69,15 @@ project folder, prefer `openmeld space add-me <space-url-or-id> --project-folder
 are accepted aliases, but `--project-folder` is the canonical option. This
 confirms Space membership only; it does not prove Wake readiness.
 
+`add-me` creates a new Agent Profile by default. Do not list or inspect all
+existing profiles to guess which one might represent this session. Only reuse
+an Agent Profile when you remember its exact ID from an earlier successful
+step in this same session: add `--agent-profile <agent-profile-id>`. Do not
+search for substitutes.
+
 Use `--model <model>` and optional `--reasoning-effort <level>` only when the
-user or Agent explicitly selects them. If neither flag is present, an existing
-Codex thread keeps its current model and reasoning settings.
+user or Agent explicitly selects them. If neither flag is present, OpenMeld
+does not force a model selection.
 
 If you are running inside Codex, `add-me` detects `CODEX_THREAD_ID` when
 present and binds that Codex thread to the Project folder you pass. If you
@@ -82,7 +88,7 @@ printf '%s\n' "$CODEX_THREAD_ID"
 pwd
 ```
 
-Use the thread ID as `--agent-controller-conversation-id` with
+Use the thread ID as `--native-session <id>` with `--session resume` and
 `--agent-controller builtin:codex`. If it is empty, do not invent a thread ID.
 Codex can resume an explicit thread ID, but the Project folder still tells OpenMeld
 where future local work should run.
@@ -99,7 +105,7 @@ printf '%s\n' "$CLAUDE_CODE_SESSION_ID"
 pwd
 ```
 
-Use the session ID as `--agent-controller-conversation-id` with
+Use the session ID as `--native-session <id>` with `--session resume` and
 `--agent-controller builtin:claude-code`. If it is empty, do not invent a
 session ID.
 
@@ -108,9 +114,9 @@ Cursor is a supported local Agent Controller through the official
 conversation. Bind `builtin:cursor` explicitly and let OpenMeld create or load
 the private Cursor ACP session for that Agent Profile.
 
-If `add-me` times out while reading Agent Profile Bindings, no Space membership
-was written before that step completed. Run `openmeld service status`, then retry the
-same command: `openmeld space add-me <space-url-or-id> --project-folder <path> --view agent`.
+If `add-me --agent-profile <id>` times out while reading that exact Agent
+Profile Binding, no Space membership was written before that step completed.
+Run `openmeld service status`, then retry the same command.
 
 ## Send Messages
 

package/skills/openmeld-cli/references/commands.md

@@ -23,10 +23,12 @@ the current local agent session path first:
 openmeld space add-me <space-url-or-id> --project-folder "$(pwd)" --view agent
 ```
 
-When OpenMeld can identify the current supported controller conversation, `add-me`
-creates or reuses the wakeable Agent Profile for that conversation and adds it
-to the Space. If the current session ID is missing, fail closed instead of
-creating a fake wakeable teammate.
+When OpenMeld can identify the current supported controller conversation,
+`add-me` creates a new wakeable Agent Profile for that conversation and adds it
+to the Space. Reuse only an exact Profile ID remembered from this session by
+adding `--agent-profile <agent-profile-id>`; do not search existing Profiles.
+If the current session ID is missing, fail closed instead of creating a fake
+wakeable teammate.
 
 Cursor is a supported OpenMeld Agent Controller, but this current-session
 shortcut does not adopt an existing Cursor IDE conversation. Bind Cursor
@@ -294,7 +296,7 @@ openmeld space add-agents <space-id> --all --profile <human-profile-id> --view a
 Create a new Agent Profile first when the Space needs a new agent identity:
 
 ```bash
-openmeld profiles create "Codex Agent" --kind agent --agent-controller builtin:codex --agent-controller-conversation-id <agent-controller-conversation-id> --profile <human-profile-id> --view agent
+openmeld profiles create "Codex Agent" --kind agent --agent-controller builtin:codex --session resume --native-session <agent-controller-conversation-id> --view agent
 openmeld space add-agents <space-id> --agent-profile <agent-profile-id> --profile <human-profile-id> --view agent
 ```
 
@@ -306,7 +308,7 @@ printf '%s\n' "$CODEX_THREAD_ID"
 pwd
 ```
 
-Use that value as `--agent-controller-conversation-id` only with
+Use that value as `--native-session <id>` only with `--session resume` and
 `--agent-controller builtin:codex`. If it is empty, do not invent a thread ID.
 Codex can resume an explicit thread ID, but the Project folder still tells OpenMeld
 where future local work should run.
@@ -319,7 +321,7 @@ printf '%s\n' "$CLAUDE_CODE_SESSION_ID"
 pwd
 ```
 
-Use that value as `--agent-controller-conversation-id` only with
+Use that value as `--native-session <id>` only with `--session resume` and
 `--agent-controller builtin:claude-code`. The session ID and original Project
 folder belong together. Claude Code resume is scoped to the directory where the
 session was created, so future Wake must run from that Project folder.
@@ -328,7 +330,7 @@ For Cursor, verify the exact `cursor-agent` CLI and its separate CLI login:
 
 ```bash
 cursor-agent login
-openmeld profiles create "Implementation Agent" --kind agent --agent-controller builtin:cursor --model 'default[]' --agent-controller-permission-mode default --profile <human-profile-id> --view agent
+openmeld profiles create "Implementation Agent" --kind agent --agent-controller builtin:cursor --model 'default[]' --agent-controller-permission-mode default --view agent
 ```
 
 Cursor runs through the official `cursor-agent acp` interface. Cursor CLI
@@ -341,7 +343,7 @@ reasoning setting, so do not pass `--reasoning-effort` for Cursor.
 ### `openmeld space add-me`
 
 Add yourself to a Space with one command. If you are running inside a supported
-agent controller, OpenMeld creates or reuses the Agent Profile for the current
+agent controller, OpenMeld creates a new Agent Profile for the current
 controller conversation, sets the Project folder, and adds that Agent Profile
 to the Space through the normal membership path. If no supported agent
 controller is detected, OpenMeld adds the current Human Profile instead.
@@ -352,6 +354,7 @@ the current project folder."
 ```bash
 openmeld space add-me <space-url-or-id> --project-folder "$(pwd)" --view agent
 openmeld space add-me <space-url-or-id> --project-folder /absolute/path --view agent
+openmeld space add-me <space-url-or-id> --project-folder "$(pwd)" --agent-profile <exact-profile-id> --view agent
 ```
 
 Use `--project-folder` as the preferred option name. `--workspace-path`,
@@ -361,9 +364,15 @@ Human Profile used as the signed-in user's acting identity; it is not the Agent
 Profile being added. Space membership does not prove Wake readiness; use status
 or trace diagnostics when you need Wake proof.
 
+Omitting `--agent-profile` always means create a new Agent Profile. Do not list
+or inspect the account's other profiles before running the default command.
+Pass `--agent-profile <exact-profile-id>` only when you remember that exact
+profile from an earlier successful step in this controller session; OpenMeld
+checks only that profile and never searches for a substitute.
+
 To make an explicit model selection on the Agent Profile Binding, add
 `--model <model>` and optionally `--reasoning-effort <level>`. Without these
-flags, an existing Codex thread keeps its current model and reasoning settings.
+flags, OpenMeld does not force a model selection.
 Do not pass `--reasoning-effort` without `--model`.
 
 When run inside Claude Code, `add-me` detects `CLAUDE_CODE_SESSION_ID` and uses
@@ -374,9 +383,9 @@ belong to another Project folder.
 When run inside Codex, `add-me` detects `CODEX_THREAD_ID` when present and uses
 `--project-folder` as the future local workspace for that Codex thread.
 
-If preparation times out while reading Agent Profile Bindings, no Space
-membership was written before that step completed. Run `openmeld service status`, then
-retry the same command: `openmeld space add-me <space-url-or-id> --project-folder <path> --view agent`.
+If preparation with `--agent-profile <id>` times out while reading that exact
+Binding, no Space membership was written before that step completed. Run
+`openmeld service status`, then retry the same command.
 
 ### `openmeld space add-human-profiles`
 
@@ -582,10 +591,15 @@ openmeld profiles create <profile-name> --kind agent --view agent
 openmeld profiles list --view agent
 openmeld profiles set <profile-id> --view agent
 openmeld profiles show <profile-id> --view agent
+openmeld profiles show <profile-id> --details --view agent
 openmeld profiles update <profile-id> --name <profile-name>
 openmeld profiles delete <profile-id> --force
 ```
 
+Agent View `show` and `update` output is compact by default. Use `--details`
+only when you need full runtime and diagnostic evidence; use `--json` on
+`show` when a machine-readable full payload is required.
+
 Create your own Agent Profile or request one for a teammate through the same
 entry, then manage requests separately: