Requests kept failing but AIC consumption kept increasing
- Linguagem predominante
- Shell
- Estrelas
- 11.2k
- Forks
- 1.9k
- Merge médio
- 14h 16min
- PRs com merge (30d)
- 6
Descrição
### Describe the bug
I had a terrible experience today where requests kept failing with `Response was interrupted due to a server error. Retrying...` and `Request failed due to a transient API error. Retrying...` all the while my AIC consumption kept increasing
I was using GPT 5.4 with a 400k context. Everything worked perfect in the first hour during a `/grill-me` session, then I switched to autopilot for the implementation. It worked for a while then it hit a few hiccups so I left the AI on its own while I take a lunch break. Came back to a session that consumed half of the allocated credits for a month, and almost nothing to show for it
In the screenshot above, the session has taken up 168k / 400k of context. I saw it starting to fail with transient errors so I went for lunch and left the AI to work.
An hour later I get this:
### Affected version
1.0.62
### Steps to reproduce the behavior
Do an intensive planning session using the [`/grill-me`](https://github.com/mattpocock/skills/blob/main/skills/productivity/grill-me/SKILL.md) skill by [Matt Pocock](https://github.com/mattpocock/skills)
Switch to `autopilot` for the implementation
Watch it burn a little then go for lunch
### Expected behavior
I would expect either that the tool gives up and stops trying, or at least that the AIC consumption doesn't increase.
I shouldn't have to pay to use a faulty system
### Additional context
This was on a Github Enterprise account with EU data residency
Guia de contribuição
Direção de pesquisa
Reproduce this in version 1.0.62 using an intensive /grill-me session followed by autopilot, then observe behavior after transient or server-error retries begin. Trace the retry handling and AIC accounting paths; done means the tool stops retrying or otherwise prevents continued AIC consumption when requests repeatedly fail.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- shell
- Domínio
- cli
- Tipo de issue
- Bug
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Status de atividade
- Pouca atividade
- Clareza
- Razoavelmente clara
- Facilidade para iniciantes
- 45/100