Recently created a small program (wtg) to summarize program stdout logs. Primary intended uses are finding errors in lengthy logs which might be missed with a skim or summarizing otherwise obtuse log messages. It keeps program output using a similar log structure as the unix script command but also supports inputs via non-interactive pipes. It uses a heuristic for determining the start/end of new shell command sequences using only bytes from stdin which I'm not fully satisfied (i.e. segmenting by newlines/carriage returns) with but works well enough in practice.
Ironically, in creating the example demo, Rust log messages were not the best example since they are often quite detailed and self-explanatory to parse, so the demo is a long C++ template compilation error 
.
First crate - would appreciate any feedback!
Code: GitHub - brylee10/wtg: What The GPT (wtg), a CLI to chat with your program logs