Summarized terminal output

[egyleader]

i am a flutter developer and I noticed that the LLM needs to run alot of commands that has very long terminal output like flutter run or the build_runner code generation command where might be an error in the middle of the output but not at the beginning or the last part of the log , so terminal truncate option is not very helpful.

I wounder if we can use any small, cheap and fast model to extract only the important parts (errors) from terminal outputs above 10 lines before submitting it to the coding model , this won't just improve the model context usage and reduce API costs but also
I expect to have higher quality output of the coding session over time .

below is an example of long terminal output that have error in the middle and some successes , this is all the info needed .

$ melos run fcln && melos run fgen && melos run l10n
$ melos exec
└> dart run build_runner build --delete-conflicting-outputs
└> RUNNING (in 2 packages)

---

[myApp]: [INFO] Generating build script...
[myApp]: [INFO] Generating build script completed, took 270ms
[myApp]:
[myApp]: [INFO] Precompiling build script......
[myPackage]: [INFO] Generating build script...
[myPackage]: [INFO] Generating build script completed, took 206ms
[myPackage]:
[myPackage]: [INFO] Precompiling build script......
[myApp]: [INFO] Precompiling build script... completed, took 4.7s
[myApp]:
[myApp]: [INFO] Initializing inputs
[myApp]: [INFO] Building new asset graph...
[myPackage]: [INFO] Precompiling build script... completed, took 3.6s
[myPackage]:
[myApp]: [INFO] Building new asset graph completed, took 1.0s
[myApp]:
[myApp]: [INFO] Checking for unexpected pre-existing outputs....
[myApp]: [INFO] Deleting 16 declared outputs which already existed on disk.
[myApp]: [INFO] Checking for unexpected pre-existing outputs. completed, took 0ms
[myApp]:
[myApp]: [INFO] Running build...
[myApp]: [INFO] Generating SDK summary...
[myPackage]: [FlutterGen] v5.10.0 Loading ...
[myPackage]: [FlutterGen] Reading options from pubspec.yaml
ERROR: ERROR: [myPackage]: [FlutterGen] Specified build.yaml as input but the file does not exists.

[myPackage]: [INFO] Initializing inputs
[myPackage]: [INFO] Building new asset graph...
[myPackage]: [INFO] Building new asset graph completed, took 994ms
[myPackage]:
[myPackage]: [INFO] Checking for unexpected pre-existing outputs....
[myPackage]: [INFO] Deleting 2 declared outputs which already existed on disk.
[myPackage]: [INFO] Checking for unexpected pre-existing outputs. completed, took 0ms
[myPackage]:
[myPackage]: [INFO] Running build...
[myPackage]: [FlutterGen] Generated: lib/generated/assets.gen.dart
[myPackage]: [FlutterGen] Generated: lib/generated/fonts.gen.dart
[myPackage]: [FlutterGen] Finished generating.
[myPackage]: [INFO] Running build completed, took 250ms
[myPackage]:
[myPackage]: [INFO] Caching finalized dependency graph...
[myApp]: [INFO] 1.5s elapsed, 0/16 actions completed.
[myPackage]: [INFO] Caching finalized dependency graph completed, took 54ms
[myPackage]:
[myPackage]: [INFO] Succeeded after 318ms with 2 outputs (1 actions)
[myPackage]:
[myApp]: [INFO] 2.6s elapsed, 0/16 actions completed.
[myApp]: [INFO] Generating SDK summary completed, took 3.3s
[myApp]:
[myApp]: [INFO] 4.3s elapsed, 84/101 actions completed.
[myApp]: [INFO] 5.4s elapsed, 92/107 actions completed.
[myApp]: [INFO] 10.5s elapsed, 105/118 actions completed.
[myApp]: [INFO] 11.6s elapsed, 128/131 actions completed.
[myApp]: [INFO] 12.6s elapsed, 131/132 actions completed.
[myApp]: [INFO] 13.7s elapsed, 225/226 actions completed.
[myApp]: [INFO] Running build completed, took 13.9s
[myApp]:
[myApp]: [INFO] Caching finalized dependency graph...
[myApp]: [INFO] Caching finalized dependency graph completed, took 127ms
[myApp]:
[myApp]: [INFO] Succeeded after 14.1s with 94 outputs (468 actions)
[myApp]:

$ melos exec
└> dart run build_runner build --delete-conflicting-outputs
└> SUCCESS

melos run fgen
└> melos exec -- "dart run build_runner build --delete-conflicting-outputs"
└> SUCCESS
melos run l10n
└> melos exec -- "dart run easy_localization:generate -S assets/translations -O lib/generated/translations -f keys -o locale_keys.g.dart &&
dart run easy_localization:generate -S assets/translations -O lib/generated/translations -f json -o codegen_loader.g.dart
"
└> RUNNING

$ melos exec
└> dart run easy_localization:generate -S assets/translations -O lib/generated/translations -f keys -o locale_keys.g.dart && dart run easy_localization:generate -S assets/translations -O lib/generated/translations -f json -o codegen_loader.g.dart

 └> RUNNING (in 1 packages)

---

myPackage:
All done! File generated in /Users/egyleader/dev/_dkilo/dkilo-advertise/packages/myPackage/lib/generated/translations/locale_keys.g.dart
All done! File generated in /Users/egyleader/dev/_dkilo/dkilo-advertise/packages/myPackage/lib/generated/translations/codegen_loader.g.dart
myPackage: SUCCESS

$ melos exec
└> dart run easy_localization:generate -S assets/translations -O lib/generated/translations -f keys -o locale_keys.g.dart && dart run easy_localization:generate -S assets/translations -O lib/generated/translations -f json -o codegen_loader.g.dart

 └> SUCCESS

melos run l10n
└> melos exec -- "dart run easy_localization:generate -S assets/translations -O lib/generated/translations -f keys -o locale_keys.g.dart &&
dart run easy_localization:generate -S assets/translations -O lib/generated/translations -f json -o codegen_loader.g.dart
"

[BradKML]

the most naive way would be to head and tail, but that could miss some critical information. Another idea would be to log them into file and then RAG accordingly, which could do the job, but the issue is that it requires a lot of tokens. I can also think of a way where "regular" logs and "last error" are in separate files, making it easier to isolate issues, or may there a way to create MCP tooling to only pull apart the most important procedures.