User says DeepSeek V4 Pro got worse in OpenCode
A Reddit user says DeepSeek V4 Pro suddenly became worse at following instructions and writing code. This is a community report, not an official notice or measured test. Still, it is useful for people who rely on AI coding tools every day.
The post comes from Reddit’s r/opencodeCLI community. The user says DeepSeek V4 Pro felt much less helpful than before, including weaker instruction following and poorer code output. The item does not include an official explanation, outage notice, or hard performance numbers.
For practical use, treat this as a warning sign rather than proof that the model changed. AI coding quality can vary because of model updates, heavy traffic, settings, long chats, context issues, or the service that sits between the user and the model. For important work, keep tasks small, review every diff, run tests, and switch models or start a fresh session when answers start looking unreliable.
Key points
- This is a Reddit user report about DeepSeek V4 Pro feeling worse in OpenCode.
- It is not an official statement or a benchmark result.
- The reported problems are weaker instruction following and lower code quality.
- If an AI coding tool acts oddly, try a fresh session, a smaller task, or another model.
- For real projects, check the diff and run tests before accepting AI-made code.
Quick term guide
- AI coding tool
- Software that uses AI to help write, edit, or explain code.
- OpenCode
- A coding tool that connects AI models to help write and edit code.
- outage
- When an online service stops working temporarily and users cannot access it.
- context
- The information an AI uses to understand your request, such as files, notes, and past messages.
- tests
- Automatic checks that help confirm code works as expected.
- models
- Different AI engines that can power answers or code suggestions inside a tool.
- session
- A continuous period of interaction between a user and a computer program.
- benchmark
- A test used to compare speed, quality, or cost.