Save and quit an editor that a CLI session started (`unity-mcp-cli exec`, `open --headless`). Needs the session lease nonce; an editor the user opened is never closed. Used by `unity-mcp-cli close`.
77%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./Unity-MCP-Plugin/.claude/skills/editor-session-quit/SKILL.mdSave and quit an editor that a CLI session started.
nonce — the nonce of the project's session lease (.ai-game-dev/session.json), which the CLI also passed to the editor as AIGD_SESSION_NONCE.Refuses unless this editor was started by a CLI session (AIGD_SESSION_OWNER=cli) with the same nonce. Otherwise answers right away, then saves changed scenes that have a file and changed assets and exits — as the idle shutdown does. Unlike the OS polite-quit signal it also reaches a headless (-batchmode) editor. Prefer unity-mcp-cli close --owned-only over calling it directly.
unity-mcp-cli run-system-tool editor-session-quit --input '{
"nonce": "string_value"
}'For complex input (multi-line strings, code), save the JSON to a file and use:
unity-mcp-cli run-system-tool editor-session-quit --input-file args.jsonOr pipe via stdin (recommended):
unity-mcp-cli run-system-tool editor-session-quit --input-file - <<'EOF' {"param": "value"} EOF
If unity-mcp-cli is not found, either install it globally (npm install -g unity-mcp-cli) or use npx unity-mcp-cli instead.
Read the /unity-initial-setup skill for detailed installation instructions.
| Name | Type | Required | Description |
|---|---|---|---|
nonce | string | Yes | The nonce of the project's CLI session lease (.ai-game-dev/session.json). |
{
"type": "object",
"properties": {
"nonce": {
"type": "string"
}
},
"required": [
"nonce"
]
}{
"type": "object",
"properties": {
"result": {
"type": "string"
}
},
"required": [
"result"
]
}IvanMurzak/Unity-MCP
09079ed
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.