[BUG] Account suspension triggered by abnormal usage likely caused by Claude Code extension background activity

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?

In VS code Claude Code extension after latest extension update, my usage spike and limit end just in few minutes, my account (MAX PLAN) was automatically flagged and suspended due to “high volume exchanges.”

However:

• I did not intentionally generate such high usage
• All activity originated from my own devices
• The spike in usage appears to be caused by unexpected background or automated requests from the extension

This suggests the extension may be:

• generating requests without clear user interaction
• or triggering repeated calls unintentionally

As a result, my account was suspended despite normal intended usage.

What Should Happen?

• Extensions should not generate excessive or automated traffic without explicit user action

Users should be protected from unintended usage spikes

• The system should distinguish between:

• intentional abuse
• and extension-induced behavior

Error Messages/Logs

No direct error logs.

Observed behavior:

Sudden spike in usage
Rapid exhaustion of hourly limits
Followed by account suspension due to “high volume exchanges”

Steps to Reproduce

1. Install Latest Claude Code extension in VS Code
2. Use normally or keep workspace open
3. Monitor usage over time with perform small task

👉 Result:

• Unexpected increase in usage
• Possible triggering of rate limits and safety systems
• Potential account suspension

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.8

Claude Code Version

2.1.87

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

No signs of account compromise (all sessions are mine)
Behavior indicates possible unintended automated requests
This led to false-positive enforcement action (account suspension)

Impact
Loss of paid subscription access
Potential false-positive policy violation
Risk for other users using the same extension