Trying to make local Qwen work more like Claude Code
has been running locally on an RTX 3090 and has been useful for fixing software problems. Opus 4.8 used with the Zed editor and the feels better at producing code. The bigger difference is the working method.
The does not jump straight into edits: it breaks the job into clear steps, checks the context first, makes backups, and runs several checks after changes. It also tests whether the feature still works and warns about likely bugs, , or s. The main question is how to make local Qwen follow a similarly careful process through a or workflow.
The visible text asks for examples that force step-by-step checking.
Key points
- is being used locally on an RTX 3090 for software issue fixing.
- Opus 4.8 with Zed and the appears to produce better code.
- Claude Code works in steps, checks context, makes backups, and verifies changes.
- It also looks for likely bugs, , and s.
- The goal is to make local Qwen behave in a similarly careful way through a or workflow.