Status

Call status once before the first Loomle operation in a task:

status({})

It reports the running Client version, PID, platform target, executable path, update availability, current project binding, and the bound Bridge’s health and version when known. It is read-only, has no arguments, and does not install updates. It may complete Loomle’s normal automatic binding rules, but only project explicitly binds or switches a project.

If the session is unbound, continue with project. Update discovery is informational: offline access or unavailable GitHub Release metadata reports unknown without blocking SAL or project operations. Loomle reads the latest stable GitHub Release directly; the website is not an update manifest for current Clients. A frozen website manifest exists only to move Clients through 0.7.6 onto the GitHub-native updater in 0.7.7.

When an update is available, Loomle asks the agent to get user approval, close affected Unreal Editors, replace the complete plugin, and restart the MCP Server. On Windows only, it also identifies the running Client by PID and executable path so the agent can stop every process using that installation before replacing the locked executable. macOS does not require that extra process-stop step. The returned guidance names the ordinary PowerShell Stop-Process -Id <pid> command explicitly; it is run outside the Client connection being stopped.