anthropics / anthropics/claude-code

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

Abierto
#93,984 0 comentarios 0 reacciones 0 asignados Ver en GitHub
area:cost bug platform:linux
Lenguaje dominante
Python
Estrellas
145k
Forks
23.1k
Métricas de merge de PR
Métricas de PR pendientes

Descripción

**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
[]
```

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
linux
Área
cloud
Tipo de issue
Error
Dificultad
5/5
Tiempo estimado
Más de una semana
Estado de actividad
Activo
Claridad
Necesita aclaración
Aptitud para principiantes
15/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.