Analyze a log file

Turn an Unreal Engine log into prioritized findings, crash triage, and statistics with analyze_logs.

When something goes wrong in your project, the log file usually holds the answer — but engine logs are long and noisy. This guide runs a full analysis with analyze_logs and shows you what to do with the results.

Before you start

Your AI client is connected.
You have a plain-text log file on disk — for example Saved/Logs/MyProject.log (live editor), a crash log, or a CI build log.

This is a paid tool — a fixed credit cost per session, billed only when analysis runs; empty logs and logs without Error or Fatal entries are free. Current price: pricing page.

Pick the right log

Live-editor problems: Saved/Logs/<Project>.log from the current or last session.
Crashes: the log written before the crash. After a crash the editor process is gone, so use the file on disk.
CI builds: the build step's log file.

Plain text only — crash dumps (.dmp) are rejected; analyze the text log written next to them instead.

Start the analysis

Ask your client:

Analyze the log file at Saved/Logs/MyProject.log

The tool opens a session, then analyzes the uploaded copy so log bytes never flow through your chat.

Known limitation — file upload to object storage is pending deployment in production. Until it goes live, the paste path (inline log text) works; your client falls back to it automatically.

Read the report

Work through the findings top-down — they're prioritized by severity and frequency. Each finding shows evidence excerpts so you can jump to the matching lines yourself. If the log contains a crash, check the crash triage block first: it names the suspect Blueprint and a root-cause summary.

Not yet available — a deeper Blueprint review (analyze_blueprint) is planned. Today: after crash triage names the Blueprint, ask your client to inspect it with search_docs_code on the failing subsystem.

Follow up

Ask your client to search the docs for the top finding — see Search Unreal Engine documentation.
If the fix involves cleanup, continue with Audit your project's assets or Generate an editor script.

Verify

The report appeared in your chat with a summary, findings, and statistics.
The portal's Usage page shows the call, and your balance dropped by 5 (or nothing, for a free outcome).

Next steps

analyze_logs reference — inputs, outputs, and limits
Fix a problem — error messages and remedies

Was this page helpful?