This is something we’ve seen reported: agent terminals staying in the “Running” state (timer still ticking) after the command has actually finished. A recent update did include a fix for terminals not clearing after they finish, but from your report it looks like that didn’t fully resolve it on Windows, so I’ve reported your case for the team to take another look.
Two quick things to help me narrow it down:
When this happens, does the agent keep working normally and it’s only the “N Terminals Running” indicator that stays up, or does it actually leave the agent waiting/blocked?
If you run “Developer: Reload Window” (Ctrl+Shift+P → type “Reload Window”), do the stale entries clear?
It shouldn’t stop Cursor from working in the meantime, but I know the ticking timers are misleading. Let me know and I’ll keep this thread updated.
