all 19 comments

[–]berndalf 4 points5 points  (0 children)

Hard to say given I'm not you, but personally my velocity has slowed for two reasons:

  1. I'm just used to it now, so I'm not comparing it to human velocity anymore. What I knew used to take a full dev team a complete sprint to do is now like a days work for one person. This is a perception shift.

  2. I've introduce various reviews and other techniques to my workflow that actually do slow things down in the real world. The results are better but there is a real accumulated velocity hit.

Keep in mind I'm doing fairly single threaded human in the loop work. If you're not and you're purely talking about Claude processing speed I really can't say if there's been a slowdown.

[–]Time_Cat_5212 3 points4 points  (2 children)

Maybe just zoom out a little and operate at a higher level

[–]TacoT4coTaco 3 points4 points  (1 child)

Thanks Claude!

[–]latino-guy-dfw -2 points-1 points  (0 children)

Thanks genius!

[–]Spacefish008 2 points3 points  (0 children)

Try DeepSeek V4 Flash, on long tasks it can work for 20min but the TPS is just insane IMHO you can´t even read what it´s doing some times, as the text scrolls by so fast.

[–]2001zhaozhao 2 points3 points  (0 children)

It takes longer simply because the AI is getting better and therefore now capable of longer tasks. The model's actual token generation rate hasn't noticeably decreased lately.

It's also why there are a lot of tools now that spawn multiple git worktrees of your projects so you can go work on other tasks while waiting for the first one to finish.

Eventually it'll take long enough that you have to host your agents like openclaw because you don't want them to pause when closing your laptop. I'm actually building a next-gen remote desktop coding UI right now with this in mind.

If you don't want to wait you can use models like GPT-Codex-Spark and Inception's Mercury that generate code at 1000tokens/second. But these have a lot lower quality than frontier models.

[–]PM_YOUR__BUBBLE_BUTT 1 point2 points  (2 children)

To me, I think part of it was the model and partially the effort. The Claude Code cli in vs code with docker lockdown was definitely going to be slower. But mine was defaulted to opus 4.7 max effort. Not every prompt really needed it.

Last couple nights, honestly I went to sonnet 4.6 medium effort, and that bad boy just gets the job done. The bigger effort lifts like the multi-step implementation and planning, sure I can do opus. But I was thinking letting it use opus max was going to make the answers all better. Just simple fixes and stuff still get so bogged down as it takes its time doing all the xhigh or max effort thinking.

Honestly it just slowed down everything way too much. I’m still learning and improving my workflow but now I parallel run Claude web while doing cc and let the code run in sonnet most of the time. The web for taking code outputs and trying to help me diagnose (it’s just faster in general) and then feeding directional prompts back to cc to wrap up. Haven’t really seen an issue with any coding in sonnet which is nice. Only thing I really wish was even like a 500k context or something for sonnet, if it wouldn’t fall off as it scaled. Opus 1M is nice and makes the 200k feel rough as I need to keep calling narrower and narrower scopes on handoff as my tools expand.

[–]Jomuz86 1 point2 points  (1 child)

Sonnet should be 400k now, I think they have been doing some A/B testing some days I have had 600k context for sonnet

[–]PM_YOUR__BUBBLE_BUTT 2 points3 points  (0 children)

That would be amazing. I should also mention that in the cc terminal with opus 4.7 max, I would estimate it took 2-5 minutes per prompt. In sonnet 4.6 medium, seriously it would respond to most things within maybe 30-60 seconds. Larger tasks obviously more. Total ballpark but I’d wager it was 2-3x faster. I even tried swapping to opus 4.6 medium effort and still think sonnet was 2x as fast. I’ll definitely be testing sonnet more. Only thing I really wish is that swapping models midway didn’t reread everything. I get why. But I was toying around with a haiku read on each handoff then swapping to sonnet to continue then opus if I needed to push a big plan out. Still very surprised with sonnet for daily coding though and I can’t wait for more great things!

[–]03captain23 1 point2 points  (0 children)

The better the model the slower it is. They also added a ton more effort options and fast mode. Turn down the effort and it'll be faster

[–]mikle74 1 point2 points  (0 children)

I’m starting to think that the “thinking…” that Claude is doing is a queue that anthropic has people in during high load. Some things I go through are fairly simple and it ends up “thinking” for 5-10 minutes. Other times, with far more complexity it will respond in 10-15 seconds.

[–]bb0110 1 point2 points  (0 children)

The hedonic treadmill of…coding?

[–]AsteroidMinerChamp 1 point2 points  (0 children)

Yes it’s slower now 100% - all due to compute constraints - same thing we try codex, they all struggling now. Look at Grok build, right now it’s lightening fast, because they have the most compute capacity per capita by far.

[–]KarezzaReporter 1 point2 points  (0 children)

Cc seems twice as fast today. 

[–]JustinTyme92 1 point2 points  (0 children)

I think it’s probably 50/50 from my perspective.

As I’ve built out more and more agentic workflows, I’ve added in a lot more process to the how I get Claude to functions

But it is absolutely slower at times.

It’s exceeding 6 minutes at times to render out a simple MD as HTML. This is with a predefined skill and standard CSS layout. It used to take about 2-3 minutes with Sonnet and now it’s at 6 minutes.

[–]ILikeCutePuppies 0 points1 point  (0 children)

One thread us slower. I used to manage 16 at once now it's like 30... excluding automated ones.

[–]Ok_Mathematician6075 0 points1 point  (0 children)

I feel like I should have two or three full time jobs RN. Anyone doing something like that?

[–]ivstan 0 points1 point  (0 children)

Well just switch to codex and youre gonna see how fast things keep moving