Copilot harness: in-Chat terminals are more difficult to follow and cancel by default

Now that the Copilot harness is becoming the default, a noticeable UX downgrade is related to how in-Chat terminals behave. See how Local handles a live terminal: And here is the command run through Copilot: It seems Copilot, being its own process, is interpreted differently by tools such as Nx. Major differences: - No live output most of the times. The Chat should behave as a user, not as a CI machine. - No ability to easily cancel the terminal run. With Local, I can simply put the cursor inside the terminal box and stop the execution. - (Minor) Lack of ability to see the process directly in VS Code.