anthropics / anthropics/claude-code

[BUG] Fable 5.1 burns tokens faster than 5.0 100% of limit in 20 mins.

Offen
#91,289 4 Kommentare 5 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
area:cost area:model bug needs-repro platform:linux
Vorherrschende Sprache
Python
Sterne
145k
Forks
23.1k
PR-Merge-Kennzahlen
PR-Kennzahlen ausstehend

Beschreibung

### 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?

Fable 5.1 medium burns through 100% of claude code limit in under 20 mins!!! its even less token efficient than 5.0 even though you report it as more efficient.

### What Should Happen?

Fable 5.1 medium burns through 100% of claude code limit in under 20 mins!!! its even less token efficient than 5.0 even though you report it as more efficient.

### Error Messages/Logs

```shell

```

### Steps to Reproduce

Fable 5.1 medium burns through 100% of claude code limit in under 20 mins!!! its even less token efficient than 5.0 even though you report it as more efficient.

### Claude Model

Other

### Is this a regression?

Yes, this worked in a previous version

### Last Working Version

_No response_

### Claude Code Version

2.1.257

### Platform

Anthropic API

### Operating System

Ubuntu/Debian Linux

### Terminal/Shell

VS Code integrated terminal

### Additional Information

_No response_

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Rechercherichtung

No source file, test, logs, or exact Fable model identifier is provided. Start by reproducing the report with Claude Code 2.1.257 in the VS Code terminal on Ubuntu/Debian, comparing Fable 5.1 medium with 5.0 while recording token usage. Done means the regression is reproducible with enough usage data to identify the affected component and verify a fix.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
linux, vscode
Bereich
cli, performance
Issue-Typ
Bug
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Aktiv
Klarheit
Muss geklärt werden
Anfängerfreundlichkeit
25/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.