[bayesnet]

This is a CC harness thing than a model thing but the "new" thinking messages ('hmm...', 'this one needs a moment...') are extraordinarily irritating. They're both entirely uninformative and strictly worse than a spinner. On my workflows CC often spends up to an hour thinking (which is fine if the result is good) and seeing these messages does not build confidence.

[yakattak]

There’s one that’s like “Considering 17 theories” that had me wondering what those 17 things would be, I wanted to see them! Turns out it’s just a static message. Very confusing.

[algoth1]

On the leaked codebase they show 100+ messages that are randomly cycled through

[bob1029]

"Reticulating Splines"

[pphysch]

Maybe there are literally 17 models in an initial MoE pass. Seems excessive though.

[sbinnee]

The comment section is already long, but I knew that I could found comments about "hmm" that I started noticing. Yes, it is so irritating to me too. Also, one additional thing I noticed was that verbose information has been more and more being obfuscated. I run CC with --verbose option for months, and I can see verbose mode is not verbose anymore. I wish I can do -vvv maximum verbose mode.

[MintPaw]

Sounds really minor, but was actually a big contributor to me canceling and switching. The VS Code extension has a morphing spinner thing that rapidly switches between these little catch phrases. It drives me crazy, and I end up covering it up with my right click menu so I can read the actual thinking tokens without that attention vampire distracting me.

And of course they recently turned off all third party harness support for the subscription, so you're just forced to watch it and any other stuff they randomly decide to add, or pay thousands of dollars.

[bayesnet]

I used Gemini CLI for a while because it was free to me. The primary reason I stopped was because it wasn't very good, but their "thinking summaries" didn't help matters. They were model generated and just said things to the effect of "I'm thinking very hard about how to solve this problem" and "I'm laser-focused on the user objective". So I feel you: small things like this make a big difference to usability.

[andai]

I'm not sure if this is official, but from what I gathered, they just bill 3rd party stuff as extra usage now:

https://news.ycombinator.com/item?id=47633568

(They were against ToS before (might still be?), and people were having their Anthropic accounts banned. Actually charging people money for the tokens they're using seems like a much more sensible move.)

[MintPaw]

Yes, but I got a subscription because I was tired of alt+tabbing to the Cursor spending dashboard between prompts to make sure I wasn't over spending. I'm ok if they slow me down for a few hours during peak usage. But getting cut off for 20+ days because I'm not thinking about the prompt cache for a bit makes a subscription feel pretty useless.

I was using it with Zed before, because I guess I'm one of the only programmers who doesn't just full vibe, which seem to mean I'm not the target customer for a lot of these companies who seem to be going all in on the terminal interfaces.

I've gone back to Cursor auto the last few weeks, it hasn't been too bad actually, I haven't managed to run out of the $20/mo plan yet.

[procinct]

Could you say more about your workflow? I don’t think I’ve ever gotten close to an hour of thinking before. Always curious to learn how to get more out of agents.

[bayesnet]

I don't think it's something special about my workflow and more the application area--I'm writing a lot of Lean lately and particularly knotty proofs can take quite a lot of time. Long thinking intervals are more of a bug than a feature IMO: Even if Claude can one-shot the proof in 40-60 minutes I'd rather have a partial proof in 15 and fill in the gaps myself.

[oefrha]

It wouldn't be so irritating if thinking didn't start to take a lot longer for tasks of similar complexity (or maybe it's taking longer to even start to think behind the scenes due to queueing).

[j_bum]

Agreed. I actually have thought those were “waiting to get a response from the API” rather than “the model is still thinking” messages

[cesarvarela]

It is the new "You are absolutely right!"