mjlisted

# Drive Mjolnir sessions Mjolnir (`mj`) runs coding sessions on local or remote targets. This skill is how you, an agent running inside one session, start and steer other sessions. ## Check availability first ```sh command -v mj mj api-info ``` `mj api-info` prints the API base URL and the file holding the bearer token. Both commands must succeed. They often fail inside containers and on remote targets, because the worker there cannot reach the daemon on the user's machine. When `mj` is unusable, use the `mj-agents` MCP tools if your harness lists them. When neither is available, say once that session orchestration is not reachable from here, and continue with the task by yourself. ## The mj-agents MCP server Some sessions are given an MCP server named `mj-agents`. It delegates work to child sessions in the same target and filesystem: - `list_profiles` — the profiles and models a child may use. - `spawn` — start a child; returns `child_session_id` at once, before the child has started running. - `list_agents` — this parent's children and their status. - `send_input` — send follow-up input to one child. - `wait` — block until the named children finish their current turn. Status `complete` means the reports are in `output`; `still_running` means the timeout came first. That is not a failure: call `wait` again with the same `child_session_ids`. - `interrupt` — stop the child's current turn. - `close` — stop a child and keep its conversation. Prefer these tools w