Native CLI and editor-closed workflows

Claudus 2.0 ships a native command-line executable alongside the plugin. Choose the exact project once in your command or MCP configuration, discover its live tools, and invoke Unreal operations from your terminal. Scripted CLI use does not require Node.js or an AI provider account; those requirements belong to the optional embedded coding agent.

One project, two ways to work

• Run one-shot commands such as status, toolsets, describe and call, with JSON output for automation and file-based arguments for larger requests.
• Keep an MCP connection open over stdio for an external agent client. The proxy connects to the authenticated native endpoint for the selected project; there is no HTTP MCP listener to configure.
• Use --launch-headless to start a hidden Unreal commandlet when a suitable backend is unavailable. Supported tools still use Unreal object loading, reflection and serialization while the editor window is closed.
• Connect to the matching interactive editor when the task needs its UI or viewport. Backend discovery and takeover coordinate the project writer; two independent writers should not edit the same project root.
• Inspect tool schemas and returned results, then save and reload intended changes. A connection loss during a mutation can leave an uncertain outcome, so inspect the project before retrying.

Assets and offline inspection

The live asset and reflection tools operate through Unreal. The separate asset command family also exposes a file-to-JSON converter for offline inspection and checked round trips. Use asset check on the original file before relying on that path; converter compatibility and runtime discovery have their own limits, especially on macOS. Do not overwrite a package that a running editor or hidden backend has loaded.