sdmitry

I've been seeing ridiculous shortening of the amount of time it takes me to reach a limit. Two $200 max accounts are now not enough to get through a working day, even a couple days ago it was hard to imagine.

In addition to putting pressure on Anthropic to explain themselves and hoping they are going to fix something, I'm also wondering if there are other factors at play as well.

In particular, whether there is also a combination of factors like larger token inputs with opus 1m, having channels feature enabled (wasteful notifications/idle state messages that we may not see in UI), and potentially even bugs in the agent code itself (like not keep cache long enough, drift in cache keys

I think I found at least an answer (if not "the" answer) why Opus turns to shit sometimes for some people, seemingly randomly.

  // When this condition triggers after CF9 failed attempts:                                                                                                                                                                                                                                                                                   
  if (D34(J) && wO1(K.model)) {  // D34 = error check, wO1 = is Opus                                                                                                                                                            

I can't believe I'm posting this, here, but here we are. Now I'm one of the people complaining. I ran out of my $200 max plan over the course of intense usage through the week. I've been using multiple simultaneous sessions, basically working non-stop throughout the day, but nothing crazy - I'm still in the loop. It usually lasts me a week. All running almost purely opus, including for the subagents (through env var).

Today I ran out and subscribed for an additional $100 max plan to wrap up some work. In about 30 minutes of a single session usage, without even any fancy subagent crap (just code, commit, verify, code some more), it suddenly stopped with a message "You've hit your limit · res

I've tried a bunch of terminals – built-in, standalone – nothing helped. Finally found a fix that worked for me by turning on the "Maximize throughput at the cost of higher latency" option in iTerm2 (latest beta, not sure if that matters though). The flickering stopped instantly, the moment I checked the box. No noticeable impact on typing latency or output. Been running like this all day, and I haven’t seen a single flicker since.

Just wanted to share this tip in case it helps anyone else. It’s been really bad lately and incredibly annoying. It's a stretch, but I wouldn't be surprised if this flickering can literally kill somebody with epillepsy by triggering a seizure.

Curious if anyone