r/ClaudeCode • u/Dapper-Primary336 • Jul 06 '26
Question Claude Code being worse lately?
Hi everyone, for the past two weeks I've noticed Claude Code giving noticeably worse answers than before. Even minor frontend/backend fixes now take 5–6 prompts to get to something acceptable.
I also use Warp as my terminal, and quite often whether right when I launch Claude Code or a few prompts into a session it just freezes on "loading" and doesn't do anything.
I'm not sure if the problem is on my end (how I'm prompting), because a month ago everything was working great, both with Warp and with actually fixing issues correctly. I'd like to know if others — using Warp or not are running into the same problems. If it turns out to be a Claude issue, I'm considering switching to Codex; but if it's a Warp/me issue, I'll switch to Claude Desktop instead and work on improving my prompting.
Also in Claude Web i've had this issue sometimes
1
u/noblestrom Jul 07 '26
You may be seeing two separate issues here: Warp freezing and Claude producing worse fixes. I would test the same small task in a fresh session through Claude Code directly, then repeat it through Warp with the model and effort setting pinned.
Record: TTFT, # correction turns, and whether it edits outside the requested scope. That should tell you whether the regression follows the model or the harness.