Save changed scenes and assets, then quit a Unity Editor started by a CLI session. A matching session identifier is required, and editors opened manually are left running. Headless editors are supported.
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`.
Review the instructions the agent will receive before you install.
Save 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"
]
}
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Build unity-mcp-cli from its TypeScript source and optionally make the command available across terminals with npm link. Covers dependency installation, compilation, version checks, and reporting errors when a step fails.
Review unresolved GitHub pull request comments against the current code, apply minimal fixes for valid issues, and reply to review threads. Comments that need human judgment remain open, while fixed or unnecessary requests are resolved with explanations.
Add packages to a Unity project from its package registry, a Git URL, or a local path. Choose a compatible version or specify one, and receive the installation result after any required reload.
List packages installed in a Unity project with their names, versions, sources, and descriptions. Filter by source or keyword, or show only direct dependencies—the packages explicitly listed in the project manifest.
Remove an installed UPM package, a package managed by Unity, from a project. Checks that it exists, updates manifest.json, and delivers the result after any reload. Built-in packages and dependencies of other packages cannot be removed.
Search Unity's package registry and installed packages by name, ID, or description. Review available versions and installation status before adding a package, using cached results or online lookups for exact matches.