Troubleshooting
How to report crashes and help us fix them fast
Reporting a Crash
NeoStack AI logs every AI operation automatically. If you experience a crash, sending us this log helps us fix the issue quickly.
Send Us These Files
| File | Location |
|---|---|
| Tool Audit Log | Saved/Logs/AIK_ToolAudit.log |
| Engine Log | Saved/Logs/<YourProject>.log |
How to find them: Open your project folder → Saved → Logs. Or from Unreal: File → Open Project Folder then go into Saved/Logs/.
Send both files to us on Discord along with:
- What you were asking the AI to do when it crashed
- Your Unreal Engine version (5.5, 5.6, 5.7)
- Which agent you were using (Claude Code, Gemini CLI, Codex, OpenRouter)
What the Audit Log Contains
Every AI action is recorded — which asset was modified, what changed, and whether it succeeded or failed:
[2026-02-08 14:23:01] OK | edit_blueprint | BP_Player | + Variable: Health (Float)
[2026-02-08 14:23:02] OK | configure_asset | BP_Player | bReplicates: false -> true
[2026-02-08 14:23:03] FAIL | edit_blueprint | BP_Enemy | Function 'OnDeath' not found
This lets us trace exactly what the AI did before the crash and reproduce the issue on our end.
External CLI install
If Claude Desktop, Claude Code, or Codex isn’t connecting to your editor, ask the agent to “run unreal_status”. The bridge stays online even without an editor and this tool tells you exactly what it found and what’s wrong. Common cases:
“No running Unreal editor found”
The editor is closed, or the NeoStack AI plugin is disabled, or the plugin is older than 3.1.8 (the first version external clients can connect to). Open the project, wait for the editor to fully load, and try again. No client restart is needed.
“More than one Unreal editor is running”
The bridge won’t guess between projects. Pick one:
- Ask the agent to “select the <name> project”.
- Start the CLI from inside the project folder you want.
- Pin a project: set the project directory in Claude Desktop’s extension settings, or set
NEOSTACK_PROJECT_DIRfor CLIs.
“The editor reports its MCP server is not running”
The editor is open but its MCP server is off or failed to start. Check Project Settings → Plugins → NeoStack AI → MCP, then restart the editor.
“Last heartbeat was Ns ago (stale)”
The editor crashed or was force-quit. Restart it and the entry refreshes within a few seconds.
Tools list works but tool calls hang
Tool calls run on the editor’s game thread with a default 60-second budget. Long-running work can hit this ceiling. Raise it via Project Settings → Plugins → NeoStack AI → Tool Execution Timeout.
Still stuck
Share the full unreal_status output when you open an issue. It contains the discovery decision, every editor the bridge saw, and the connection result.