How this channel uses _thinking traces_ In the channel's material on hands-on model evaluation, thinking traces comes up in the context of testing how models reason. When the Every team runs day-zero checks on a new release — as with Opus 4.8 — part of the exploration is understanding not just what a model answers, but the reasoning it shows on the way to an answer. That visible reasoning is what lets a reviewer judge where a model excels, where it hesitates, and how much reasoning effort a given task actually needs.