hostlisted

# Mullion host Check for `$MULLION_SESSION_ID` before following anything below — if it's unset, you're not running inside a Mullion-hosted session (a plain terminal, a different host, or this repo checked out somewhere else) and none of this applies. Nothing here works, or is needed, outside a Mullion-hosted session. ## The four env vars you were spawned with | Variable | Unlocks | | --------------------- | -------------------------------------------------------------------------------------------- | | `MULLION_HOOK_SOCKET` | Structured notifications — `mullion notify` — and the hook channel your launcher wired up. | | `MULLION_HOOK_TOKEN` | Authenticates both the hook socket above AND the control socket below, at **session scope**. | | `MULLION_SOCKET_PATH` | Where the control socket lives — lets `mullion`/`mullion mcp`, run with no flags, find it. | | `MULLION_SESSION_ID` | Which session you are — lets `mullion`/`mullion mcp` default every op to yourself. | That's the entire surface you need — no config file to read, and nothing else grants you anything. Omit `--session`/`sessionId` everywhere below; it defaults to you. ## The scope model (read this before reaching for command syntax) `MULLION_HOOK_TOKEN` authenticates at **session scope**: pinned to this one session. Enough for get/rename/logs on yourself, the full `browser` surface, `project actions`, an