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
- Agentic coding accessibility will reshape understanding of software complexity — pixlpa · 2026-08-24
- Devin Agent bypasses Slack block by finding emails in git logs — sandylikesfrogs · 2026-08-24
- Developer habits shift: Agents become collaborators from simple tools — latticecut · 2026-08-24
- Dev bottleneck shifts from writing to reading code: exe.dev co-founder — thursdai_pod · 2026-08-24
- The biggest AI mistake: trying to reinvent the wheel instead of using tools — Tired40s · 2026-08-24
- DeepPaperNote turns research papers into Obsidian notes — tom_doerr · 2026-08-24