[BUG] VS Code extension stuck at 100% usage, fails to auto-rotate to new session
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Core Issue: The Claude Code VS Code extension fails to automatically start a new session when current session reaches usage limits. The panel becomes stuck showing "100% used" and stops responding, despite having remaining account-wide usage available.
Expected Behavior:
Claude Code should automatically rotate to a new session when the current session reaches its usage limit, allowing uninterrupted work (similar to how the CLI handles session management).
Actual Behavior:
- Session reaches ~88-100% usage
- Panel shows "100% used" in input area
- User can type messages but receives no responses
- Panel remains stuck indefinitely - no automatic session reset occurs
- Must manually intervene despite having account usage at only ~7% weekly
Environment:
- OS: macOS
- VS Code: 1.106.3
- Claude Code: 2.1.3
- Subscription: Claude Max
Steps to Reproduce:
- Use VS Code extension until session usage reaches ~88%+
- Attempt to continue conversation
- Observe: Messages sent but no responses received
- Check:
/usageshows current session at high % but weekly usage still low - Observe: Panel never auto-resets to new session
Troubleshooting Attempted (None Resolved Issue):
- Restarted Extension Host
- Reinstalled extension completely
- Updated from 2.0.64 to 2.1.3
- Restarted VS Code multiple times
- Closed/reopened panels
Key Observation:
- ✅ CLI terminal mode works correctly (auto-rotates sessions)
- ✅ Account has remaining usage (7% weekly)
- ❌ VS Code panel does NOT auto-rotate sessions
- ❌ Panel stuck requiring manual intervention
Impact:
The lack of automatic session rotation makes the VS Code extension unreliable for extended work sessions. Users must constantly monitor usage and manually restart to avoid getting stuck.
Workaround:
Switch to CLI terminal mode, which correctly handles automatic session rotation.
Possible Relation:
May be related to recent usage limit display/management issues reported January 7-8, 2026.
What Should Happen?
Core Issue: The Claude Code VS Code extension fails to automatically start a new session when current session reaches usage limits. The panel becomes stuck showing "100% used" and stops responding, despite having remaining account-wide usage available.
Expected Behavior:
Claude Code should automatically rotate to a new session when the current session reaches its usage limit, allowing uninterrupted work (similar to how the CLI handles session management).
Actual Behavior:
- Session reaches ~88-100% usage
- Panel shows "100% used" in input area
- User can type messages but receives no responses
- Panel remains stuck indefinitely - no automatic session reset occurs
- Must manually intervene despite having account usage at only ~7% weekly
Environment:
- OS: macOS
- VS Code: 1.106.3
- Claude Code: 2.1.3
- Subscription: Claude Max
Steps to Reproduce:
- Use VS Code extension until session usage reaches ~88%+
- Attempt to continue conversation
- Observe: Messages sent but no responses received
- Check:
/usageshows current session at high % but weekly usage still low - Observe: Panel never auto-resets to new session
Troubleshooting Attempted (None Resolved Issue):
- Restarted Extension Host
- Reinstalled extension completely
- Updated from 2.0.64 to 2.1.3
- Restarted VS Code multiple times
- Closed/reopened panels
Key Observation:
- ✅ CLI terminal mode works correctly (auto-rotates sessions)
- ✅ Account has remaining usage (7% weekly)
- ❌ VS Code panel does NOT auto-rotate sessions
- ❌ Panel stuck requiring manual intervention
Impact:
The lack of automatic session rotation makes the VS Code extension unreliable for extended work sessions. Users must constantly monitor usage and manually restart to avoid getting stuck.
Workaround:
Switch to CLI terminal mode, which correctly handles automatic session rotation.
Possible Relation:
May be related to recent usage limit display/management issues reported January 7-8, 2026.
Error Messages/Logs
No error message sent
Steps to Reproduce
Core Issue: The Claude Code VS Code extension fails to automatically start a new session when current session reaches usage limits. The panel becomes stuck showing "100% used" and stops responding, despite having remaining account-wide usage available.
Expected Behavior:
Claude Code should automatically rotate to a new session when the current session reaches its usage limit, allowing uninterrupted work (similar to how the CLI handles session management).
Actual Behavior:
- Session reaches ~88-100% usage
- Panel shows "100% used" in input area
- User can type messages but receives no responses
- Panel remains stuck indefinitely - no automatic session reset occurs
- Must manually intervene despite having account usage at only ~7% weekly
Environment:
- OS: macOS
- VS Code: 1.106.3
- Claude Code: 2.1.3
- Subscription: Claude Max
Steps to Reproduce:
- Use VS Code extension until session usage reaches ~88%+
- Attempt to continue conversation
- Observe: Messages sent but no responses received
- Check:
/usageshows current session at high % but weekly usage still low - Observe: Panel never auto-resets to new session
Troubleshooting Attempted (None Resolved Issue):
- Restarted Extension Host
- Reinstalled extension completely
- Updated from 2.0.64 to 2.1.3
- Restarted VS Code multiple times
- Closed/reopened panels
Key Observation:
- ✅ CLI terminal mode works correctly (auto-rotates sessions)
- ✅ Account has remaining usage (7% weekly)
- ❌ VS Code panel does NOT auto-rotate sessions
- ❌ Panel stuck requiring manual intervention
Impact:
The lack of automatic session rotation makes the VS Code extension unreliable for extended work sessions. Users must constantly monitor usage and manually restart to avoid getting stuck.
Workaround:
Switch to CLI terminal mode, which correctly handles automatic session rotation.
Possible Relation:
May be related to recent usage limit display/management issues reported January 7-8, 2026.
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
Claude Code: 2.1.3
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Other
Additional Information
Core Issue: The Claude Code VS Code extension fails to automatically start a new session when current session reaches usage limits. The panel becomes stuck showing "100% used" and stops responding, despite having remaining account-wide usage available.
Expected Behavior:
Claude Code should automatically rotate to a new session when the current session reaches its usage limit, allowing uninterrupted work (similar to how the CLI handles session management).
Actual Behavior:
- Session reaches ~88-100% usage
- Panel shows "100% used" in input area
- User can type messages but receives no responses
- Panel remains stuck indefinitely - no automatic session reset occurs
- Must manually intervene despite having account usage at only ~7% weekly
Environment:
- OS: macOS
- VS Code: 1.106.3
- Claude Code: 2.1.3
- Subscription: Claude Max
Steps to Reproduce:
- Use VS Code extension until session usage reaches ~88%+
- Attempt to continue conversation
- Observe: Messages sent but no responses received
- Check:
/usageshows current session at high % but weekly usage still low - Observe: Panel never auto-resets to new session
Troubleshooting Attempted (None Resolved Issue):
- Restarted Extension Host
- Reinstalled extension completely
- Updated from 2.0.64 to 2.1.3
- Restarted VS Code multiple times
- Closed/reopened panels
Key Observation:
- ✅ CLI terminal mode works correctly (auto-rotates sessions)
- ✅ Account has remaining usage (7% weekly)
- ❌ VS Code panel does NOT auto-rotate sessions
- ❌ Panel stuck requiring manual intervention
Impact:
The lack of automatic session rotation makes the VS Code extension unreliable for extended work sessions. Users must constantly monitor usage and manually restart to avoid getting stuck.
Workaround:
Switch to CLI terminal mode, which correctly handles automatic session rotation.
Possible Relation:
May be related to recent usage limit display/management issues reported January 7-8, 2026.
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗