anthropics / anthropics/claude-code

[Bug] Session Usage Limit Reached Prematurely with Claude Sonnet Medium Thinking

Aperta
#93,984 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub
area:cost bug platform:linux
Lingua principale
Python
Stelle
145k
Fork
23.1k
Metriche di merge delle PR
Metriche PR in attesa

Descrizione

**Bug Description**
Hello Anthropic Support,

I’m contacting you regarding a serious issue with my Pro service.

I purchased my Pro subscription using the email address **[sabonasonofwaktole@gmail.com](mailto:sabonasonofwaktole@gmail.com)**.

I was using **Claude Sonnet with the Medium thinking setting** under a **5-hour session**, but the session reached its usage limit after only approximately **7 minutes**. This has happened **twice**, which has effectively consumed the session time far faster than I reasonably expected from a 5-hour session.

I would like Anthropic to investigate the usage and session logs for my account and verify exactly how the session limit was calculated. In particular, please check the token usage, thinking usage, model configuration, and session accounting to determine why a 5-hour session reached its limit in approximately 7 minutes.

I understand that different models and thinking settings can consume usage at different rates. However, having a 5-hour session reach its limit within 7 minutes, twice, is significant enough that I believe it deserves a proper investigation.

I am also requesting **compensation or restoration of the Pro session time that was lost**. I paid for the Pro service expecting to have reasonable access to the service, and losing the session so quickly has materially affected my ability to use it.

Please review my account and server-side usage records and provide me with:

1. An explanation of why the 5-hour session reached its limit after approximately 7 minutes.
2. Confirmation of the actual usage recorded during those sessions.
3. An explanation of whether this behavior was expected for Sonnet Medium or resulted from an issue with usage accounting.
4. Appropriate compensation or restoration for the session time that was lost.

I would appreciate a detailed investigation rather than a generic explanation of usage limits, since this occurred twice and the session was exhausted unusually quickly.

Thank you for taking this seriously. I’m looking forward to a fair resolution.

Best regards,
Sabona Tafese

**Environment Info**
- Platform: linux
- Terminal: kitty
- Version: 2.1.240
- Feedback ID: 892e0820-430c-4ba8-8261-3f2c0638867a

**Errors**
```json
[]
```

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Direzione di ricerca

No repository file, test, or code entry point is identified; start by reviewing the reported Feedback ID 892e0820-430c-4ba8-8261-3f2c0638867a alongside the account and server-side usage records. Done means explaining the two seven-minute session limits, confirming recorded usage and configuration, and resolving any compensation or restoration request.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
linux
Ambito
cloud
Tipo di issue
Bug
Difficoltà
5/5
Tempo stimato
Più di una settimana
Stato di attività
Attiva
Chiarezza
Da chiarire
Idoneità per principianti
15/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.