pneuma-session

# Refining your session's identity Every Pneuma session has a row in the launcher (Recent Sessions) and inside its project (ProjectPanel). The row has two slots: - **Title** — defaults to `"<Mode> session"` (e.g. "WebCraft session"). Mode-only. - **Description / preview** — defaults to the first user prompt. For project sessions, the first prompt is the server-emitted `<pneuma:env reason="opened" />` synthetic tag — which carries zero information for a human scanning the list. Until you refine, both fields are placeholders. Three "WebCraft session" rows look identical except for their thumbnails. The user has to remember by time, which they won't. This skill is how you fix that. You write a meaningful title + one-sentence summary into `<sessionDir>/session.json`, and the launcher row updates in place. The data persists across reopens; the launcher's own listing always reads from your last refine. ## The mechanism ```bash $PNEUMA_CLI session refine --json '{"displayName": "<≤40 chars>", "description": "<≤280 chars>"}' ``` Always call through the `$PNEUMA_CLI` env var, not the literal `pneuma` binary. The env var resolves to the right invocation regardless of how Pneuma was installed (npm-global, dev worktree, desktop bundle); writing the literal `pneuma session refine` only works when the binary happens to be on `PATH`, which it usually isn't inside the agent's sandbox. `$PNEUMA_CLI` is a single executable path, so the call behaves the same in bash, zsh, and fish, quote...