export.compose

Since next

[disk (with a Ready build)] Compose the player's native executable from a Ready build (build.status names it).

It carries EVERY scene and ui/ and boots the manifest's startupScene, not the open one. Needs the deploy tools beside the editor; a release needs an application icon. target "web" writes a site a browser plays instead, at <out>/web (no Ready build needed).


Title	Export the game
Mode
Token cost	about 437 tokens (in the default list, paid on every call)
Toolset	core

Arguments

Argument	Type	Required	Default	Allowed values	Description
`agent`	`string`	no			The name of the agent making the call, when several agents share one connection: each named agent is its own actor and plays its own game. Leave it out when there is one agent.
`apply`	`boolean`	no			web: false answers what would run and writes nothing
`artifactId`	`string`	no
`buildId`	`string`	no
`contentRoot`	`string`	no			The revision's snapshot; found when absent
`jobId`	`string`	no
`modulesRoot`	`string`	no			The build's modules/*.js; from jobId when absent
`name`	`string`	no			web: the folder's name
`out`	`string`	yes			The executable to write, absolute
`precompress`	`boolean`	no			web: also .br and .gz beside each file
`purpose`	`enum`	no	`development`	`development`, `release`
`revisionId`	`string`	no			build.status's lastReady when absent
`target`	`enum`	no	`host`	`host`, `linux`, `windows`, `web`	web: a folder a browser plays (needs no Ready build)
`toolsDir`	`string`	no			Optional; found beside the install when absent
`webRuntime`	`string`	no			web: the runtime to bundle; the installed SDK's when absent
`zip`	`boolean`	no			web: also <out>/<name>-web.zip

Example

An MCP tools/call with the required arguments (placeholders in angle brackets).

{
  "name": "export.compose",
  "arguments": {
    "out": "<out>"
  }
}