ue-log-reader

An Unreal Engine crash can leave behind a log file that runs into the millions of lines. Scanning for Fatal entries, deduplicating the same error that fired three hundred times, stitching together stack frames, and drafting a bug report — every step slows the debugging loop. ue-log-reader lets the model read and interpret that log right inside the conversation and renders the result as an interactive quick-read card. You just read the conclusion and hit one button to copy the bug-summary text.

Key capabilities include: streaming line-by-line parsing (defaults to the trailing 200 MB, so even several-hundred-MB files stay within memory); aggregation and deduplication keyed on category plus normalised message, so an error printed 300 times becomes a single entry with a x300 badge; automatic extraction of the crash cause, the first 10 stack frames, and the engine version. The card presents Fatal, Error, Ensure, and Warn counts as colour-coded stat blocks that filter on click, a Top-issues list with hover-to-reveal original text, and a collapsible crash detail panel in monospace. It supports both the standard UE log format and all four Android adb logcat variants (threadtime, time, brief, raw), stamping a logcat badge in the card header when active. On the safety side, explicit paths must resolve inside projectRoot or logRoots, all operations are strictly read-only, scans are rate-limited and serialised, results are cached by path+mtime+size, and every failure surfaces a clear reason rather than a silent blank.

Built for teams shipping UE-powered games or UE-shell applications who work inside the DeepSeek Harness desktop client. A single sentence in the chat — "crashed just now, check the log" — kicks off the entire pipeline, from pinpointing the root cause to producing a copyable bug-summary text, all within one conversation turn.