How to reduce zig build command output when "autopilot" it with LLM

Help
1

I am using cline in VSCode. One trick I often use is to have LLM validate the proposed changes by running zig build test. Currently it generates these outputs friendly to human but redundant for LLM inputs.

[4/6] steps
q [0/2] run test
   q root.test.cuda initialization

[4/6] steps
q [0/2] run test
   q root.test.cuda initialization

[4/6] steps
q [0/2] run test
   q root.test.cuda initialization

[4/6] steps
q [0/2] run test
   q root.test.cuda initialization

[4/6] steps
q [0/2] run test
   q root.test.cuda initialization

[4/6] steps
q [0/2] run test
   q root.test.cuda initialization

[4/6] steps
q [1/2] run test
   q root.test.kernel

[4/6] steps
q [1/2] run test
   q root.test.kernel

[4/6] steps
q [1/2] run test
   q root.test.kernel

[4/6] steps
q [1/2] run test
   q root.test.kernel
2

Hi @jackal, welcome to Ziggit. Can you explain more what you are hoping to accomplish? Are you trying to get the summary to be more concise?

3

You can disable progress output by setting env var TERM:

 TERM=dumb zig build test
4 Likes
4

Thanks. What I am hoping to accomplish is to find a way to have zig build do not print the progress with backspace like [4/6] steps [1/2] run test. The reason is that will unnecessarily take up context length of the LLM input.

5

Thanks. This works.