I traced the session against our backend records, and the times in the chat are actually correct. The confusion is coming from the Usage page: each row there is one request, dated by when it started, not when it finished. A subagent is a single request that can run for many minutes across dozens of model calls, so it shows up as one row stamped with its start time.
In your case the turn started at 16:16:43 (the 4:16 PM on your message). The subagent at 16:46:15 kept working until about 16:54:50, then the main agent made its final calls and wrapped up around 16:56. That is where both numbers come from: 16:16:43 to roughly 16:56:09 is the 39m 26s, and 16:56 is the completion time.
Let me know if you disagree, if this doesn’t make sense or if you see other oddities and I can take a closer look!
The prompt was sent at 13:07
The agent continuously managed the team of subagents until at least 16:46
I expect that “Worked for” will display the duration of the agent’s work from the time the request was sent.
The second screenshot from the bug report also shows that the completion time for K3-low doesn’t match reality. Furthermore, I checked this metric when K3-max started, and at that time it showed the correct stop time (I didn’t take a screenshot of that).
