Glicol CLI keeps the previous graph running on a parse error, reporting it in the TUI console

When a file edit contains a parse error, Glicol CLI does not stop playback — it keeps the previous valid graph running and reports the error in its TUI console. This is deliberate for robustness in live use: audio never cuts out due to a typo. The consequence is that a new edit does not take effect until it parses correctly, so performers must watch the TUI console to know whether a change landed or the old version is still playing.

Examples

Edit a running session to introduce a syntax error → TUI shows error, previous sound continues. Fix the error → TUI clears, new graph loads.

Assessment

Describe the listener experience when a performer types an invalid Glicol node name mid-set. Where do they look to diagnose it, and what do they hear meanwhile?