DeepSeek V4.1 Flash Fixing Legacy Code in OpenCode: Community Experience and False-Positive Boundaries

One-sentence takeaway

danilofs says that, after using DeepSeek V4.1 Flash in OpenCode continuously since Saturday, it cleaned up the mess left by Muse Code, Claude Code, and Codex over the course of a month; comments caution that it may report design choices as bugs, so constraints and human review are still required. This is a community field report, not a controlled test.

Use cases

• Tasks it can help assess: Understanding an existing codebase, locating problems, identifying repair candidates, and the hands-on feel of rapid iteration.

• Tasks it cannot support extrapolating to: Production repair accuracy, or strict cost/quality comparisons with Astra or other models.

• Applicable model version: The original post explicitly calls it DeepSeek v4.1 Flash; the API ID, build version, and inference parameters are unspecified.

• Test environment or client: OpenCode; project size, repository, tool configuration, and harness are unspecified.

• Reasoning level and parameters: Unspecified.

Evaluation method

There was no standardized method. The main post describes ongoing use, while the comments add further experiences; no task set, baseline, success criteria, number of repetitions, or independent review was defined. At collection time, the page showed 176 upvotes and 70 comments; this is only a snapshot.

Key results

TSltd_dev reported spending $140 over roughly a dozen rounds in Astra the previous night without meeting the acceptance criteria. The next day, after switching to DeepSeek 4.1 Flash and entering only “familiarize yourself with the project.”, the model found multiple issues and asked which one to fix first; the author said “Hasn't spent $1 yet.” This is a single-project experience and cannot be converted into a per-task price or success rate.

Counterevidence on false positives came from the comments: Dualyeti said that asking an LLM to fix bugs almost always results in it finding a bug, and that even 4.1 auditing 4.1 will find issues; Yes_but_I_think said design decisions are frequently mistaken for bugs. I_RIDE_SHORTSKOOLBUS suggested writing rules and deviations into design.md, with only items that violate the rules and are not on the deviation list counting as findings, indicating that some “discoveries” may stem from missing specifications.

Raw data

Conclusions and limitations

1. The post provides an on-the-ground signal that V4.1 Flash can understand legacy projects, trace issues, and propose fixes in OpenCode, but it provides no pass rate or net improvement.

2. $140, roughly a dozen rounds, and not having spent $1 are all self-reported; the Astra configuration, project, and acceptance criteria are unspecified, so the costs cannot be compared fairly.

3. First define the rules, exceptions, and acceptance criteria, then verify the changes, tests, and regression testing; a model saying it “found an issue” does not mean that a defect has been confirmed.

4. The comments also report hallucinations, missed changes, and cases where the model “claimed to have made the change but had not actually made it.” The views conflict, and none can be extrapolated.

Reproduction notes

To reproduce this, fix the OpenCode configuration and project constraints, enter the short prompt from the original post, record the findings, changes, tests, and bill, and then classify each item as “real defect / design decision / unverified.”