Cosindra for Unreal Engine

Drive your open Unreal Engine editor from the AI agent you already use.

This extension connects your AI agent to Unreal Engine over the Model Context Protocol, giving it 300+ editor operations: spawning and configuring actors, building Blueprint graphs, materials, Enhanced Input, UMG, animation, PIE control and log reading.

Agents inside the editor — GitHub Copilot, Cursor's agent — are connected for you. Agents that run in a terminal, like Claude Code and Codex, read their own configuration, so there is one command for them: Connect Claude Code / Codex.

Getting started

Install the extension and open the Cosindra panel in the activity bar.
Sign in — this is also what downloads the local server.
Set up project — installs the Cosindra plugin into your Unreal project and offers to open the editor.
Ask your agent to do something in Unreal.

The panel shows what is ready and what still needs a click, so you never have to guess which step is missing.

Requirements

Unreal Engine 5.7 or 5.8.
A Cosindra account. External AI agents are a paid feature; the trial needs no card.
VS Code 1.101+, or Cursor.

The desktop app is optional. If you already use it, this extension shares the same local server rather than starting a second one.

Commands

All of these are in the panel; the command palette has them too.

Command	What it does
`Cosindra: Set Up Unreal Project`	Install the plugin and open the editor
`Cosindra: Open Unreal Editor`	Open (or restart) the editor for your project
`Cosindra: Connect Claude Code or Codex`	Give a terminal agent the Unreal tools
`Cosindra: Choose a Different Unreal Project`	Switch projects
`Cosindra: Sign In` / `Sign Out`	Manage your account
`Cosindra: Status`	What the extension currently sees

Privacy

Everything runs on your machine and the extension talks only to it. Your account credentials live in the OS keychain, never in a settings file. The local server reports aggregate tool-call counts to your account for plan limits — never your project's contents.

Support

Documentation and account: cosindra.ai
Problems: run Cosindra: Status, then open View → Output → Cosindra and include what it says.

Logs and diagnostics

View → Output → Cosindra shows what the extension is doing. The same lines go to a small rolling file, logs/extension.log in the Cosindra data folder (macOS: ~/Library/Application Support/Cosindra, Windows: %LOCALAPPDATA%\Cosindra, Linux: $XDG_CONFIG_HOME/Cosindra or ~/.config/Cosindra), next to the local server's own logs/debug_*.log.
Details → Copy diagnostics in the Cosindra panel puts versions, connection state and the last 200 log lines on your clipboard, with tokens removed. Paste it into a support message.
If the MCP server itself cannot start, the editor's own MCP output channel shows the launcher's message.

Telemetry

The extension reports a few activation steps and its failures to cosindra.ai so that support can see what went wrong: sign-in completed, local server downloaded, started or failed, project set-up completed or failed, editor opened, agent connected. Each event carries the extension and editor versions, the operating system and an error code — never file paths, prompts or project contents.

It follows the editor's telemetry.telemetryLevel setting: everything under all, only failures under error, nothing under crash or off. It goes through the editor's own telemetry logger, so the editor's telemetry log lists every event.