troubleshootinglisted

# Mullion troubleshooting Check for `$MULLION_SESSION_ID` before following anything below — if it's unset, you're not inside a Mullion-hosted session; none of this applies. ## "If something 403s" You named a full-scope-only op, or a session id you're not pinned to. This is expected, not a bug — see the Mullion host skill's scope model table for exactly which ops are session-reachable. Run `mullion config` (below) to confirm which scope your connection actually resolved to. If you're certain this should have worked, check whether authentication is disabled on this host — the scope model doesn't apply at all in that mode, so a 403 there means something else is wrong. ## Reading `mullion config` ```bash mullion config ``` Prints the resolved socket path, which env var supplied the token, your own session id, and the **resolved scope** (`full`/`session`) — determined by actually probing a full-scope-only op, not just inspecting which token you were handed. Run this first whenever behavior doesn't match what the the Mullion host skill's scope table says it should. ## A hook that silently stopped firing If a hook-driven feature (a SessionStart nudge, a notification) that used to work has gone quiet, and you're on Codex or agy: their hook registration lives in a global, host-wide file (`~/.codex/hooks.json`, `~/.gemini/config/hooks.json`) that only gets rewritten when a session of that agent type is spawned. If the forwarder path it points at was deleted (a `make dev` worktr