A quiet coding-agent transcript is ambiguous. The agent may have finished, stalled, started a long command, or simply stopped writing for a moment.
Process state does not resolve that ambiguity. A running CLI can be waiting for the user, and a finished turn can leave its process alive. File modification time is also weak evidence because metadata may be written after the conversation changed state.
A safer classifier starts with the latest meaningful turn event.
Find the event that changed the turn
Transcript files include conversation events, tool results, titles, mode changes, and bookkeeping. The newest JSON line may not represent a state transition.
