EDIT2: it finally finished after I let it sit for 18 minutes. Didn’t even fixe the issue (super simple spacing issue in a react native app), and said “The slight difference you see between B and C on iOS is likely a separate minor issue — possibly measurement timing with measureInWindow for the flex layout between ModalHeader and the action bar. If it’s still noticeable after this fix, you could pass a small bottomOffset on the custom-emoji-picker’s EmptyState to compensate.” which means AKA “I literally didn’t attempt to fix it.” EDIT: just checked, and it really is using tokens. However, I don’t know if, when you press ctrl+o and then go back, as the token count starts from 0 again, it is re-counting the ones it used or if it’s really starting the step it’s stuck on all the way from 0. The initial prompt will run 30+ seconds before it starts showing any actions besides the orange text. Then it will read a file or several. Then it will be reading a file or several and just never finish. The token count keeps rising. Pressing ctrl+o at this point shows nothing, but escaping back to the main thread just shows the token count increase again starting all the way from 0. It will increase forever until you cancel out. Interrupting it and giving an instruction doesn’t change anything. I can’t do anything at all, because it won’t actually complete ANYTHING. I’ve let it go for 10+ minutes. It just counts up to 15k+ tokens and never finishes. What’s extra obnoxious is I don’t even know if I’m actually being charged for those tokens—which is a lot on Opus 4.6 extra high reasoning. This has been happening since yesterday, through 5+ sessions in completely fresh terminal instances each time. During this period, it has randomly continued to completion once or twice if I press ctrl+o—but I don’t know if the bug filled up the context with random BS or what. submitted by /u/Virtamancer
Originally posted by u/Virtamancer on r/ClaudeCode
You must log in or # to comment.