Qwen Code Rejects Findings File Due to Path Collision
wenshao · ghdev · 2026-08-15
A GitHub issue reveals a bug in Qwen Code's CLI where the /review --new-findings flag rejects valid input because the skill's own example writes to a path identical to the canonical findings artifact (qwen-review-{target}-findings.).
This triggers a spurious findingsFileInvalid error and a false downgradeApprove state, forcing users to manually construct a minimal JSON file. The suggestion is to accept the standard findings shape directly or use a distinct filename in examples.
More from coding & agent
- Coding agents keep opening 3 stacked PRs per chat, and merging them is a nightmare — holdenmatt · 2026-10-16
- Google-led paper uses sequential auctions to organize decentralized LLM agent workflows — _onionesque · 2026-10-16
- Since OpenAI's math release, GitHub contributors keep driving down the integer-multiplication kappa — xennygrimmato_ · 2026-10-16
- Pattern MCP makes coding agents check existing components before writing new code — DonR954 · 2026-10-16
- Zero-keyframe procedural spider walks walls and ceilings using pure raycasts — yshan2u · 2026-10-16
- OpenCode v1.19.2 keeps 1.x installs off the 2.x update path — opencode-agent[bot] · 2026-10-16