Unreal Engine 5.8 support

ClaudusBridge for Unreal Engine 5.8 is not the 5.7 plugin recompiled. Unreal 5.8 shipped the pieces an agent bridge previously had to invent for itself: a ToolsetRegistry that turns reflected functions into callable tools, an AllToolsets plugin that collects the engine's own toolset definitions, and an AgentSkill asset type. The 5.8 generation was rebuilt on top of them, which means it stopped hand-writing tool wrappers and started harvesting them from the engine.

What the engine gives it

Any UFUNCTION marked with the AICallable metadata on a UToolsetDefinition becomes a callable tool. Its parameters become a JSON input schema, its return value an output schema, and its doxygen-style comment becomes the description the model reads when choosing what to call. The catalog follows the enabled engine and project toolsets; describe the live schema rather than assuming a fixed list.

What the 5.8 build ships

• An embedded coding agent at Resources/Agent uses your system Node.js and provider credentials. The bundled native CLI is a separate executable and needs neither Node.js nor a provider account for scripted Unreal operations.
• A real terminal in the editor. SClaudusCode is a native Slate terminal emulator over a genuine pseudo-terminal, ConPTY on Windows and forkpty on macOS and Linux, with a VT parser, so the agent's full interface, spinners and permission prompts behave exactly as they do in a shell.
• A programmatic path. FClaudusAcpClient speaks the Agent Client Protocol over stdio to drive the embedded agent, with a configurable permission mode and a delegate for permission requests.
• ClaudusBridge 2.0 exposes stdio MCP through the bundled native proxy. An authenticated loopback connection reaches the exact Unreal project; no HTTP MCP listener or health URL is provided.
• Tool-search mode exposes discovery and dispatch meta-tools alongside local timeline helpers. Eager registration stays available for clients that need the live engine tools registered individually.
• A native CLI runs individual requests or persistent MCP sessions. It can launch a hidden Unreal commandlet for supported operations, coordinate interactive takeover, and rediscover a replacement backend after a restart. Inspect uncertain mutations before retrying.
• Multi-User awareness. The agent joins the same Concert session as you, as a separate participant with its own desktop presence avatar, reusing Unreal's existing MultiUser client rather than forking it.
• Multi-agent orchestration in 2.0 combines backend identity, persistent sessions, enforced package leases, dirty ownership, a job queue and an offline-readable project timeline.

Native commands and agent sign-in

The embedded agent uses Node.js and a chosen provider account. The separate native CLI runs scripted operations without either requirement. External stdio MCP clients handle their own model authentication; the local Unreal connection does not route through an AI service.

5.7 generation to 5.8 generation