Tool call headers

Every tool call gets a one-line header the instant it starts, before its result is even known, naming the tool being used and the one specific detail that distinguishes this call from any other call to the same tool.

For a file operation, that detail is the path; for a search, it is the pattern; for a shell command, it is the command itself. This is enough to follow along with what tCode is doing in real time without waiting for the whole turn to finish first.

See Tools for exactly what each of these tools does and when the model reaches for one over another.

This header is printed the moment the call starts, not once it completes; for a step that takes a noticeable amount of time, a large search or a slow shell command, you see it begin rather than only learning about it retroactively once the result comes back.

The specific formatting, a leading marker followed by the tool name and its one distinguishing detail in parentheses, is consistent across every tool and every kind of turn, local or remote, so it never needs to be relearned from one session to the next.