← ClaudeAtlas

session-opslisted

Spawning a child session, notifying the human, and what you can and can't do with a dev server/dock from inside a Mullion-hosted session. Read this if you're an agent CLI running inside a Mullion-hosted session and need to fan out work, surface progress, or check on a dev server, in ANY repo.
s3ntin3l8/mullion-session-manager · ★ 0 · AI & Automation · score 63
Install: claude install-skill s3ntin3l8/mullion-session-manager
# Mullion session ops Check for `$MULLION_SESSION_ID` before following anything below — if it's unset, you're not inside a Mullion-hosted session and none of this applies. ## Spawning a child session `spawn_child_session` (MCP) / `mullion session spawn-child --command <cmd>` (CLI) is reachable at session scope — it spawns a real child session (its own PTY, own terminal) of the session you're running inside, in the same project. You never need to name a project or your own session id; both are derived automatically. A hard cap on live children applies (ask a human to raise `settings.sessions.maxChildSessionsPerParent` if you hit it); `cwd`, if overridden, must stay inside the project directory. This is a genuine child session — it survives if you're later killed, not a `Task`-tool subagent (no session, no PTY). A spawned child always starts as an ordinary, visible `terminal` session with permission prompts on; `kind` and `skipPermissions` are silently ignored from inside a session even if you pass them (only a full-scope operator can set either — unless this host has auth disabled entirely, in which case you already are one; see the Mullion host skill's scope caveat). If a child needs to act unattended (edit files, run tests, commit) rather than wait on a human, it needs `skipPermissions: true` to actually take effect. Its panel doesn't auto-open unless a human turned that on separately — either way it shows in the sidebar. **Don't bake prompt text into `command`.** Use `