Desktop app (macOS): turn timer + pulsing logo keep counting after response completes (still occurring on 2.1.160; ref #48170)

Summary

In the Claude desktop app (Claude Code mode) on macOS, after a session finishes, the pulsing Claude asterisk/logo and the turn timer (the "Xs" counter) at the bottom of the session keep animating and the seconds keep incrementing indefinitely — even though the response is fully delivered and nothing is running in the background. It happens on every session.

This is the same bug as #48170 ("Desktop app: session turn timer continues counting after response completes"), which was auto-closed as not planned due to inactivity with no fix. The closing bot asked to open a new issue if it's still relevant — it is. Related prior reports: #50354, #58722.

Steps to reproduce

1. Open the Claude desktop app (Claude Code)
2. Send a message that involves tool use (bash commands, file edits, builds)
3. Wait for the full response to be delivered
4. Observe the turn timer next to the asterisk icon — it keeps counting, and the logo keeps pulsing

Expected behavior

The timer stops and the logo stops pulsing once the response is fully delivered.

Actual behavior

The timer keeps incrementing and the logo keeps pulsing indefinitely after the response is complete, with no background task running. It only resets when the session is restarted / switched.

Scope (important)

Only the desktop app is affected. The same work in the Claude Code CLI, in VS Code, and in other IDEs does not show this — the timer stops correctly there. So it appears specific to the desktop app's UI layer. Likely a UI rendering bug where the "streaming complete" event doesn't stop the turn-timer animation.

Persistence

Has occurred for ~3 weeks across multiple app updates. Relaunching/updating the app does not fix it.

Environment

• App: Claude desktop app (Claude Code mode)
• Claude Code engine: 2.1.160
• OS: macOS Sequoia 15.7.3 (Darwin 24.6.0)
• Device: MacBook Air M4

Notes

No background tasks were running when observed (verified locally: no claude background processes consuming CPU). The bug is purely cosmetic but persistent and misleading, since it makes a finished session look like it's still working.