openmeld 0.3.119 → 0.3.120

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://www.schemastore.org/package.json",
   "name": "openmeld",
-  "version": "0.3.119",
+  "version": "0.3.120",
   "openMeldReleaseDate": "2026-08-27",
   "description": "OpenMeld CLI - https://openmeld.ai",
   "license": "MIT",

package/skills/openmeld-cli/SKILL.md

@@ -429,10 +429,15 @@ openmeld org computers --view agent
 Create or request a new-session Agent Profile with the same configuration:
 
 ```bash
-openmeld profiles create "Review Agent" --kind agent --owner self --agent-controller builtin:codex --computer <computer-id> --session new --source local-agent --request-key <stable-key> --view agent
+openmeld profiles create "Review Agent" --kind agent --owner self --agent-controller builtin:codex --session new --source local-agent --request-key <stable-key> --view agent
 openmeld profiles create "Review Agent" --kind agent --owner <member-user-id> --agent-controller builtin:codex --computer <computer-id> --session new --source local-agent --request-key <stable-key> --view agent
 ```
 
+For `--owner self`, omit `--computer` to use this computer when the selected
+Local Agent is ready here. Pass an exact `--computer` when the user selected a
+different computer. Teammate-owned requests always require `--computer`; never
+guess which of the teammate's computers to use.
+
 Use `--source local-agent` when a supported Local Agent is making the request;
 ordinary terminal use defaults to `--source cli`. The server derives the real
 requester and actor from the signed-in OpenMeld identity. Source is attribution,

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

@@ -588,7 +588,7 @@ Create your own Agent Profile or request one for a teammate through the same
 entry, then manage requests separately:
 
 ```bash
-openmeld profiles create <profile-name> --kind agent --owner self --agent-controller builtin:codex --computer <computer-id> --session new --source local-agent --request-key <stable-key> --view agent
+openmeld profiles create <profile-name> --kind agent --owner self --agent-controller builtin:codex --session new --source local-agent --request-key <stable-key> --view agent
 openmeld profiles create <profile-name> --kind agent --owner <member-user-id> --agent-controller builtin:codex --computer <computer-id> --session new --source local-agent --request-key <stable-key> --view agent
 openmeld profiles create <profile-name> --kind agent --owner <member-user-id> --agent-controller builtin:codex --computer <computer-id> --session resume --native-session <native-session-id> --source local-agent --request-key <stable-key> --view agent
 openmeld profiles create <profile-name> --kind agent --owner <member-user-id> --agent-controller builtin:codex --computer <computer-id> --session fork --native-session <native-session-id> --source local-agent --request-key <stable-key> --view agent
@@ -601,6 +601,11 @@ openmeld profiles requests preferences get --view agent
 openmeld profiles requests preferences set --new-session automatically-allow --existing-session ask-every-time --view agent
 ```
 
+For `--owner self`, omit `--computer` to use this computer when the selected
+Local Agent is ready here. Pass an exact `--computer` when the user selected a
+different computer. Teammate-owned requests always require `--computer`; never
+guess which of the teammate's computers to use.
+
 Resume and Fork accept the exact provider-native Session ID. They fail clearly
 until OpenMeld Agent Activity can verify the selected Project Session. Approval
 policy values are `never-allow`, `ask-every-time`, and `automatically-allow`.