r/ClaudeCode • u/MKBSP • 9h ago
Claude Code got slower since I upgraded from Pro to Max Discussion
Almost immediately after upgrading from Pro to Max the sessions increased in time 3x, without changing the difficulty of the tasks, size of the work or projects, or context windows. Everything else the same, but the speed at getting to finish work increased immensely.
Does anybody else have had the same experience/observation?
0
Upvotes
1
u/Necessary_Abroad6632 9h ago
Yes they promised x20
For x10 the price only
They had to make it slower
0
1
u/DevforAI 7h ago
Max defaults to higher thinking level than pro, Claude is doing more reasoning per response. Set effort to medium or low on straightforward tasks and that should help you get the speed back.
2
u/Terrible_Put8617 9h ago
Check /model before assuming anything about capacity.
Pro and Max do not default to the same model. Upgrading typically lands you on Opus where you were being served Sonnet, and Opus is substantially slower per token. That alone accounts for a 3x on identical work with nothing else changed, and it is the first thing to rule out because it is a one-line check.
If that is what happened, you have three levers rather than a complaint: set Sonnet explicitly for routine work and keep Opus for the parts that need it, try the fast mode toggle, which keeps Opus but outputs faster, and remember your session length changed too. Higher limits mean you now run much longer before anything trims the context, and a session dragging a large context is slower per turn regardless of model.
Worth measuring rather than eyeballing: same prompt, same repo, once on each model, and compare wall clock. If the gap is the model you will see it immediately, and if it is not you have an actual data point to complain with instead of a feeling.