happier-session-control

# Happier Session Control (CLI JSON) This skill enables an agent framework (for example OpenClaw) to control Happier sessions using the **existing** `happier` CLI in `--json` mode. ## Prerequisites - The `happier` CLI is installed and authenticated. - If using multiple servers/profiles, pass server selection flags **before** `session` (prefix-only): - `happier --server <profile-id-or-name> session list --json` - `happier --server-url <url> --webapp-url <url> session list --json` ## Contract All JSON outputs are a pure-stdout envelope: ```json { "v": 1, "ok": true, "kind": "...", "data": {} } ``` or: ```json { "v": 1, "ok": false, "kind": "...", "error": { "code": "..." } } ``` Common error codes to handle: - `not_authenticated`: run `happier auth login` on the host (or mount/provide a valid `HAPPIER_HOME_DIR`). - `session_id_ambiguous`: pick deterministically from `error.candidates` (prefer exact id; otherwise ask the user). - `session_not_found`: call `happier session list --json` and retry. - `unsupported`: feature disabled by server policy or backend doesn’t support the requested intent. ## Independent session delegation Use an independent Happier session only when the user asks for new sessions or when an invoking workflow explicitly selects that topology. Native subagents remain the owner for in-session delegation. When an independent session owns a complete work bundle: - create it with a self-contained `initialMessage`, descriptive `title` and `tag`, ...