The screen re-read its window every 3 seconds unless a trace was already shown as being made, so an answer that ended between two reads came with its trace. It now asks twice a second for history_stamp (the newest record and trace ids and the steps of the traces being made, cheap and not logged) and reads the window again as soon as it changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>