openmeld 0.3.76 → 0.3.78

package/package.json

@@ -1,8 +1,8 @@
 {
   "$schema": "https://www.schemastore.org/package.json",
   "name": "openmeld",
-  "version": "0.3.76",
-  "openMeldReleaseDate": "2026-08-19",
+  "version": "0.3.78",
+  "openMeldReleaseDate": "2026-08-21",
   "description": "OpenMeld CLI - https://openmeld.ai",
   "license": "MIT",
   "type": "module",
@@ -14,7 +14,7 @@
     "access": "public"
   },
   "engines": {
-    "node": ">=20"
+    "node": "20.x || >=22 <26"
   },
   "files": [
     "README.md",
@@ -44,6 +44,7 @@
     "@mariozechner/pi-tui": "0.57.1",
     "@modelcontextprotocol/sdk": "^1.29.0",
     "@opencode-ai/sdk": "^1.18.7",
+    "better-sqlite3": "^12.6.2",
     "commander": "^14.0.0",
     "picocolors": "^1.1.1",
     "string-width": "^8.1.0",
@@ -72,6 +73,7 @@
     "@openmeld/space-mesh": "workspace:*",
     "@openmeld/start": "workspace:*",
     "@openmeld/utils": "workspace:*",
+    "@types/better-sqlite3": "^7.6.13",
     "@types/node": "^24.3.0",
     "@types/ws": "^8.18.1",
     "oxc-resolver": "^11.0.0",

package/skills/openmeld-cli/SKILL.md

@@ -1,6 +1,6 @@
 ---
 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, work in Organizations and Spaces, observe or stop Wakes, trace delivery, and repair local state.
+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
@@ -225,6 +225,36 @@ openmeld service status --view agent
 openmeld profiles list --view agent
 ```
 
+## Local Agent Session Inventory
+
+When the user asks which Local Agent Sessions exist in the active Organization,
+or needs a stable Session reference for Agent Profile creation, read the Core-owned
+Session Inventory instead of scanning provider files yourself:
+
+```bash
+openmeld activity sessions --view agent
+openmeld activity sessions --project <project-slug> --provider codex --view agent
+openmeld activity sessions --native-session <provider-native-session-id> --json
+```
+
+Use `nextCursor` with `--cursor` until it is null when the task requires a
+complete inventory. Every row already contains the authorized Owner, Project,
+Computer, Local Agent, Native Session ID and title, status, freshness, origin,
+`canResume`, `canFork`, and current Agent Profile Binding. Treat those fields as
+facts; do not recalculate them from provider files, process presence, timestamps,
+or Activity events.
+
+A visible Native Session ID is a locator, not operation authority. Before any
+resume, fork, Agent Profile creation, Binding change, or Space membership change,
+use the owning OpenMeld command and let it recheck identity, Organization,
+Project, Computer, provider capability, and permission. When `canResume` or
+`canFork` is false, do not simulate that capability. When coverage or status is
+`unknown`, `stale`, `unsupported`, or `error`, report that state directly.
+
+Session Inventory is metadata-only. Never read or upload transcripts, prompts,
+responses, reasoning, tool inputs or outputs, file contents, diffs, commands,
+terminal content, credentials, or local absolute paths to supplement it.
+
 ## Organization Skills
 
 Organization Skills are optional methods owned by the active OpenMeld
@@ -381,6 +411,69 @@ Create or select an Agent Profile through setup:
 openmeld start --view agent --kind agent --profile-name "Codex Agent"
 ```
 
+### Create Or Request An Agent Profile
+
+`openmeld profiles create` is the one creation entry for your own Agent Profile
+and for requesting a teammate-owned Agent Profile. Read the Organization
+directory for member user IDs, then read the team-safe Computer projection for
+the exact Computer and local-agent controller references available to that owner:
+
+```bash
+openmeld org directory --view agent
+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 <member-user-id> --agent-controller builtin:codex --computer <computer-id> --session new --source local-agent --request-key <stable-key> --view agent
+```
+
+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,
+not authority. Reuse the same `--request-key` only when retrying the same logical
+request.
+
+Resume and Fork use the exact provider-native Session ID:
+
+```bash
+openmeld profiles create "Review Agent" --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 "Review Agent" --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
+```
+
+Pass only a Session exposed by OpenMeld Agent Activity for the selected Project.
+Keep the provider-native ID unchanged. OpenMeld currently fails these requests
+clearly until it can verify that Session; use `--session new` when verification
+is unavailable. Prefer Fork when preserving an active working Session matters;
+prefer Resume when continuing the original Session is intentional. Check the
+selected local agent's `conversationCapabilities` from `openmeld org computers`
+before requesting Fork. Never simulate Fork by summarizing context into a new
+Session.
+
+Track and manage requests:
+
+```bash
+openmeld profiles requests list --view agent
+openmeld profiles requests approve <request-id> --view agent
+openmeld profiles requests decline <request-id> --view agent
+openmeld profiles requests cancel <request-id> --view agent
+openmeld profiles requests retry <request-id> --view agent
+```
+
+Set separate approval policies for new and existing Sessions:
+
+```bash
+openmeld profiles requests preferences get --view agent
+openmeld profiles requests preferences set --new-session automatically-allow --existing-session ask-every-time --view agent
+```
+
+Approval policy values are `never-allow`, `ask-every-time`, and
+`automatically-allow`. The target owner controls these settings. Approval does
+not silently grant Space membership; when the request records an intended
+Space, use the normal Space membership flow after the Agent Profile exists.
+
 Select a profile for the current terminal:
 
 ```bash
@@ -604,7 +697,7 @@ action. Keep purely local code or file work local. The goal is to finish the
 user's job with fewer handoffs, not to route every small question through
 OpenMeld.
 
-### Organization Directory And Invite Link
+### Organization Directory, Computers, And Invite Link
 
 Read the active Organization directory in Agent View or as one JSON envelope:
 
@@ -613,6 +706,61 @@ openmeld org directory --view agent
 openmeld org directory --json
 ```
 
+Read the Organization-visible Computer and local-agent readiness projection:
+
+```bash
+openmeld org computers --view agent
+openmeld org computers --json
+```
+
+Join `ownerUserId` to the directory member `user.id`, then use the exact
+`computerId` and `agentControllerRef` when creating a teammate-owned Agent.
+This projection is deliberately team-safe: do not expect private account names,
+local paths, launch commands, or private skills.
+
+Use the directory before answering questions such as:
+
+- who belongs to the Organization and whether they are an owner, admin, or
+  member
+- which Human Profile represents a person
+- which Agent Profiles a member owns and whether one is currently ready for
+  work
+- when OpenMeld last accepted real Human activity from a member
+
+The response contains active members, Organization roles, user identity,
+Human Profiles, Agent Profiles, and an optional `lastActiveAt`. Agent Profiles
+are returned as Organization-level records; match an Agent Profile's
+`ownerUserId` to the member's `userId` instead of guessing from names.
+
+Treat a missing `lastActiveAt` literally: OpenMeld has no authoritative Human
+activity timestamp for that member. Never substitute a Computer heartbeat,
+login/session refresh, or Agent Activity timestamp.
+
+The directory is intentionally not a dump of every People drawer field. It
+does not expose Connected Channel management, private Computer paths or file
+access, Profile Report drafts or bodies, credentials, or private local-agent
+state. Use the Center Agent when approved Organization documents, Profile
+Report context, or another Organization-owned capability is needed. Use
+team-safe Computer reads only after resolving the exact member from the
+directory.
+
+For example, to find an admin who owns a ready Agent Profile, read the
+directory, filter members by `role`, then join Agent Profiles by `ownerUserId`
+and inspect their returned readiness. Do not infer role, ownership, or
+readiness from display names.
+
+Read the same team-safe Organization Computers projection used by OpenMeld Web
+and the Center Agent. Usage Limits are included when providers report them:
+
+```bash
+openmeld org computers --view agent
+openmeld org computers --json
+```
+
+This read never exposes provider credentials, account identity, executable
+paths, setup commands, or Computer controls. Do not scrape the Web UI or query a
+provider separately.
+
 Read or manage the Organization invite link:
 
 ```bash

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

@@ -139,6 +139,55 @@ openmeld org directory --view agent
 openmeld org directory --json
 ```
 
+The directory returns active members, roles, user identity, Human Profiles,
+Organization-level Agent Profiles, and optional authoritative Human
+`lastActiveAt` timestamps. Match Agent Profiles to members with `ownerUserId`.
+A missing `lastActiveAt` means that OpenMeld has no authoritative Human
+activity timestamp; do not replace it with Computer, session, or Agent
+Activity time.
+
+This command does not expose Connected Channel management, private Computer
+paths or file access, Profile Report drafts or bodies, credentials, or private
+local-agent state.
+
+### `openmeld activity sessions`
+
+List the active Organization's authorized Local Agent Session Inventory. Agent
+View emits the shared Session contract as stable result codes; `--json` emits
+one `activity.sessions` envelope. Continue with the opaque cursor until
+`nextCursor` is null when a complete inventory is required.
+
+```bash
+openmeld activity sessions --view human
+openmeld activity sessions --view agent --limit 100
+openmeld activity sessions --project openmeld --provider codex --view agent
+openmeld activity sessions --status working --origin openmeld --json
+openmeld activity sessions --native-session <provider-native-session-id> --json
+openmeld activity sessions --cursor <opaque-cursor> --view agent
+```
+
+Filters: `--project`, `--member`, `--provider`, `--status`, `--origin`,
+`--native-session`, `--query`, `--limit`, and `--cursor`. A returned Native
+Session ID is a locator, not permission to resume, fork, create a Binding, or
+add an Agent Profile to a Space.
+
+### `openmeld org computers`
+
+List the active Organization's team-visible Computers and supported Local
+Agents. Agent View preserves the validated Organization Computers projection;
+`--json` emits one scriptable JSON envelope. When a provider reports Usage
+Limits, the same normalized limits shown in Web and available to the Center
+Agent are included.
+
+```bash
+openmeld org computers --view agent
+openmeld org computers --json
+```
+
+Join `ownerUserId` to `openmeld org directory`, then use the exact `computerId`
+and `agentControllerRef` with `openmeld profiles create`. Private local paths,
+account identities, launch commands, and private skills are not exposed.
+
 ### `openmeld org invite-link`
 
 Read, create or reset, and revoke the active Organization invite link. OpenMeld
@@ -519,6 +568,29 @@ openmeld profiles update <profile-id> --name <profile-name>
 openmeld profiles delete <profile-id> --force
 ```
 
+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 <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
+openmeld profiles requests list --view agent
+openmeld profiles requests approve <request-id> --view agent
+openmeld profiles requests decline <request-id> --view agent
+openmeld profiles requests cancel <request-id> --view agent
+openmeld profiles requests retry <request-id> --view agent
+openmeld profiles requests preferences get --view agent
+openmeld profiles requests preferences set --new-session automatically-allow --existing-session ask-every-time --view agent
+```
+
+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`.
+Read `conversationCapabilities` from `openmeld org computers` before choosing
+Fork; never substitute a generated summary for a controller-native Fork.
+
 ### `openmeld agents`
 
 Find, enable, repair, and review local agents on this computer. Use `openmeld setup`