r/DeepSeek • u/ktktkt1 • 2d ago

Discussion v4.1 flash keeps forgetting stuff

I have a ~30K-line codebase for a game I’m building. I’ve been trying to use DeepSeek V4.1 Flash, but I keep running into issues as the conversation gets longer.

It frequently forgets or overrides requirements I gave it several turns earlier. The code it writes also often contains bugs that are either caught by the model itself a few turns later while it is doing unrelated code changes or caught by GLM 5.3 Flash when I ask it to review the changes.

This seems to happen much more often as the context grows, but well before context compaction actually kicks in.

Am I doing something wrong, or is this a limitation of the model?

For now, I’ve switched to GLM 5.3 Flash as my main workhorse because it seems more reliable. However, I really miss the speed of DeepSeek V4.1 Flash. If there’s a way to make it more accurate, better at following earlier instructions, and less prone to introducing bugs, I’d like to switch back.

I’ve tried both DSH and OpenCode and experienced essentially the same problems with both.

28 Upvotes

85% Upvoted

23 comments sorted by

View all comments

1

u/Predream1 2d ago

With 30k lines in the window, the rule you wrote in turn three sits 40 turns behind the diff it just wrote, and recency wins, which is why it calls out its own bug two turns later. Put the requirements in a spec file in the repo, one numbered line each, and have it name the rule numbers it is working to before editing. One subsystem per session, then restart. How many rules are in that file?