happier: Skill for Claude Code

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:

{ "v": 1, "ok": true, "kind": "...", "data": {} }

or:

{ "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, the intended repository path, and only user-selected or safely resolved machine/profile/backend/model options;
• use canonical read-only permission mode for diagnosis when the selected backend supports it, plus an explicit no-write constraint in the brief. Permission modes are backend-applied policy, not a universal security sandbox; do not overclaim enforcement;
• treat a successful accepted spawn as the triage lane's completion for that bundle;
• return the new session id/title and allocation to the user, then stop by default;
• let the spawned session present its diagnosis directly to the user;
• do not wait for idle or pull its transcript merely to re-present the same result;
• do not instruct the spawned session to create further independent sessions unless the user explicitly requested recursive orchestration.