anthropics / anthropics/claude-code

Inconsistent usage percentage display between VS Code extension and claude.ai

Abierto
#90,177 2 comentarios 0 reacciones 0 asignados Ver en GitHub
area:cost bug platform:vscode platform:windows
Lenguaje dominante
Python
Estrellas
145k
Forks
23.1k
Métricas de merge de PR
Métricas de PR pendientes

Descripción

### Preflight Checklist

- [x] I have searched [existing issues](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug) 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?

Description:
I'm reporting a discrepancy in weekly usage limit information shown across different Claude Pro surfaces.

Issue 1: Incorrect reset time prediction
- On Wednesday afternoon, the Claude Code extension in VS Code showed: "95% used, resets in 1 day."
- Today (Thursday), 24 hours later, the same VS Code extension shows 99% used — no reset has happened yet.
- Checking Settings > Usage on claude.ai just now confirms 99% used, with the actual reset scheduled for tomorrow, Friday at 19:00.
- So the original "resets in 1 day" message (Wednesday afternoon) was wrong — the real gap was almost 2 days, not 1.

Because of this wrong prediction, I kept working on Thursday morning believing I still had quota available, and ran out unexpectedly.

Issue 2: Simultaneous percentage mismatch
- Right now, at the same moment:
- VS Code (Claude Code extension): 99% used
- claude.ai (Settings > Usage): 99% used
- Claude desktop app (Cowork): 75% used — for the same account and the same period
- Screenshots available showing all values at the same moment.

Impact:
The wrong "1 day" prediction caused me to lose track of my real usage and run out of quota mid-task. The percentage mismatch between the Claude desktop app (Cowork) and the other two interfaces (VS Code, claude.ai) makes it impossible to trust any single number without cross-checking claude.ai directly..

Environment:
Plan: Claude Pro
VS Code extension on Windows and Claude desktop app (Cowork)

Related issues:
Similar behavior reported in #51222, #69082, #54974, #55150, #49616, #52921 (e.g.)

### What Should Happen?

The weekly reset countdown and usage percentage should be accurate and consistent across all interfaces (claude.ai, the VS Code extension, and the Claude desktop app), always matching the exact reset date/time shown in claude.ai (Settings > Usage).

### Error Messages/Logs

```shell

```

### Steps to Reproduce

1. Use Claude Code in VS Code until usage approaches ~98-99% of the weekly quota
2. Note the "resets in X days" message shown in the extension
3. Compare it with the exact reset timestamp shown in claude.ai (Settings > Usage)
4. Separately, check the usage percentage shown in the Claude desktop app (Cowork) at the same moment
5. Compare the three values (VS Code, claude.ai, Claude desktop app) side by side

Image

### Claude Model

Other

### Is this a regression?

I don't know

### Last Working Version

_No response_

### Claude Code Version

Claude Code 2.1.247

### Platform

Anthropic API

### Operating System

Ubuntu/Debian Linux

### Terminal/Shell

VS Code integrated terminal

### Additional Information

https://github.com/anthropics/claude-code/issues/51222
https://github.com/anthropics/claude-code/issues/69082
https://github.com/anthropics/claude-code/issues/54974
https://github.com/anthropics/claude-code/issues/55150
https://github.com/anthropics/claude-code/issues/49616
https://github.com/anthropics/claude-code/issues/52921

Guía de contribución

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

Línea de trabajo

Start by comparing the usage shown in the VS Code extension, claude.ai Settings > Usage, and the Claude desktop app's Cowork view at the same time. Reproduce the reset countdown and percentage discrepancy near 98–99% usage, then verify that all interfaces show the same percentage and exact reset time.

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

Evaluación

Stack tecnológico
linux, ubuntu, vscode
Área
analytics, api, backend
Tipo de issue
Error
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Activo
Claridad
Necesita aclaración
Aptitud para principiantes
38/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.