Stuck Process Animation After Task Completion/Timeout

What version of the VS Code extension are you using?

0.4.0

Which IDE are you using?

Cursor

What platform is your computer?

Darwin 24.6.0 arm64 arm

What steps can reproduce the bug?

Description:
When running shell commands through the Cursor AI agent that get stuck or hang indefinitely, the "Running [command]" animation continues to spin even after the conversation/task is terminated or times out. The UI doesn't provide any timeout indication or way to manually stop the animation.

**

<img width="679" height="285" alt="Image" src="https://github.com/user-attachments/assets/5211c26a-365d-497d-af54-0fb75c957f57" />

**

1. Start a conversation with Cursor AI agent
2. Request execution of a shell command that may hang or get stuck (e.g., npm run test:phase1)
3. The command gets stuck during execution (in my case, during async cleanup operations)
4. End the conversation or let it timeout
5. The "Running npm run test:phase1" animation continues spinning indefinitely

What is the expected behavior?

• The animation should stop when the conversation ends
• There should be a timeout mechanism with user notification
• Users should have the ability to manually cancel running operations
• The UI should indicate when a process is stuck or has timed out

What do you see instead?

• The spinning animation persists indefinitely
• No timeout notification is shown
• No way to manually stop the animation from the UI
• The underlying process may still be running even after conversation ends

Additional information

Environment:

• OS: macOS
• Shell: zsh 5.9

Cursor:

• Version: 1.5.9
• VSCode Version: 1.99.3
• Commit: de327274300c6f38ec9f4240d11e82c3b0660b20
• Date: 2025-08-30T21:02:27.236Z
• Electron: 34.5.8
• Chromium: 132.0.6834.210
• Node.js: 20.19.1
• V8: 13.2.152.41-electron.0
• OS: Darwin arm64 24.6.0

Additional Context:
The underlying Node.js process was actually stuck in an async operation and had to be manually killed using kill [PID] from terminal. The UI animation provided no indication that the process was stuck or that there was any issue.

Suggested Improvements:

1. Implement operation timeouts with user notifications
2. Add a "Cancel" button for running operations
3. Stop animations when conversations are terminated
4. Show process status indicators (running/stuck/timeout)