Should smart glasses display every line of a coding agent's terminal output?
Usually, no. Terminal output is written for a screen that can hold history and detail. Forwarding every line to glasses can bury the one message that needs attention beneath installation logs, repeated progress messages and partial output.
Summarize changes in state
A better default is to send meaningful transitions: started, waiting for input, failed and completed. The agent can keep detailed logs on the computer while the glasses show why the state changed. We would let the wearer ask for more detail instead of requiring them to dismiss a stream of routine events.
For example, fifty dependency-installation lines can become “Installing dependencies.” A failure should carry the specific problem, such as “Package download failed; retry available.” Summaries should retain that distinction rather than turning every unsuccessful command into the same generic error.