I often turn off the cursor (CURSOR plugin) in long-running BTMs designed to monitor a process. I noticed recently that a pipe instance will cause the cursor to become visible again. With "cursor 0 & echo foo & delay 5" the cursor remains off until the prompt returns. With "cursor 0 & echo foo | tee nul & delay 5" the cursor is visible during the delay (even with "if %_pipe == 1 cursor 0" in my tcstart.btm). With "cursor 0 & echo foo | (cursor 0 & tee nul) & delay 5" the cursor remains off. So it seems that somewhere after tcstart.btm, TCC does something to turn the cursor on. Could you change that behavior so the cursor will stay off when the user wants it off. I can think of no reason to have it on in a pipe instance.