[Bug] Feedback loops cause excessive token consumption with unresponsive background jobs

Status Closed — not planned
Reported on v2.1.170
Maintainer reply None cached
Activity 2 comments · opened Jun 11, 2026 · closed Jul 21, 2026

Happen esp. on Fable. ultracode is most effected, as it may spawn dozen of workers that can exhaust a 5h limit on a Max 5x plan within minutes, and worst: the jobs don't produce a response making it so claude wants to retry rather than change its wasteful approach.

Yet also on effort max, I don't see twice the token consumption; it's more but it seems buggy in the sense: it takes long time to "think", it does not generate the repsonse, it then tries again increasing the token burn.

Bug Description
feedback loops burn token fast, background jobs die without response wasting huge amount of tokens

Environment Info

  • Platform: linux
  • Terminal: windows-terminal
  • Version: 2.1.170
  • Feedback ID: 937da718-c431-4c0f-ae38-b32e6528397d

Errors

[]

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗