[FEATURE] Chat Status Visibility Issues
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
Environment
IDE: Visual Studio Code
Extension: Claude Code (official extension)
Remote SSH
OS: macOS + Ubuntu 22.04
Description
When chat panels are displayed in the right frame of VS Code, there is no visual indication of chat status without opening each individual chat. This differs from Cursor IDE's implementation, which provides clear visual status indicators for all chats.
Steps to Reproduce:
Open Claude Code extension in VS Code
Create multiple chat sessions
View chat list in right panel
Attempt to determine chat status (generating, completed, waiting for confirmation) without opening chats
Expected Behavior:
Chat status should be visible in the chat list, showing:
Currently generating response (in progress)
Generation completed
Awaiting user confirmation/input
Reference Implementation: Cursor IDE displays visual status indicators directly in the chat list, allowing users to see at a glance which chats are active, finished, or require attention.
Actual Behavior:
No visual status indicators are present in the chat list. Users must open each chat individually to check its current state, making it impossible to monitor multiple chats simultaneously.
Impact
Severity: Medium
User Impact:
Reduces workflow efficiency when managing multiple concurrent tasks
Requires unnecessary context switching to check chat states
Makes it difficult to prioritize which chats need attention
Slows down development workflow, especially when following the recommended practice of creating separate chats per task
Proposed Solution
Implement visual status indicators similar to Cursor IDE's approach:
Add status icons or color coding to chat items in the list
Show loading/spinner animation for chats currently generating
Display badge or indicator for chats awaiting user input or confirmation
Use distinct visual state for completed chats
Alternative Solutions
_No response_
Priority
High - Significant impact on productivity
Feature Category
Interactive mode (TUI)
Use Case Example
_No response_
Additional Context
_No response_
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗