[BUG] The edit tool is unable to edit files in the latest version

[davidho123]

What happened?

During the execution of commands, every call to the edit tool to modify Python files fails.

What did you expect to happen?

This issue was fixed in a previous version and was working perfectly, but it has reappeared in the latest version 0.10.5. I hope this can be fixed.

Client information

Qwen Code: 0.10.5 (135b47d)
运行环境: Node.js v22.20.0 / npm 11.6.1
IDE 客户端: VS Code
操作系统: win32 x64 (10.0.26100)
认证: qwen-oauth
模型: coder-model
会话 ID: d28b4625-313b-4327-b868-e0e10693c21d
沙箱: no sandbox
代理: no proxy
内存使用: 182.6 MB

Login information

No response

Anything else we need to know?

No response

[pomelo-nwu]

Hi @davidho123,

Thanks for reporting this!

To help us investigate the issue, could you please export a session log using /export html or /export json? This will provide specific error messages and context that can help us quickly identify the root cause.

Also, please note that in the latest version, coder-model now routes to qwen3.5-plus. We're not yet sure if this is a model issue or an cli agent issue, so the session log would be especially helpful.

We'll look into this as soon as possible. Thanks for your patience and support!

[yang2233]

I also encountered the same problem. Whenever I was editing the files, it kept failing. And when I switched to using Python to edit the files later, the accuracy and efficiency were both very poor.

[yang2233]

Qwen Code: 0.10.0 (9bccd49)
运行环境: Node.js v22.21.1 / npm 10.9.3
操作系统: win32 x64 (10.0.22631)
认证: qwen-oauth
模型: coder-model
会话 ID: a2a6fac2-d22e-4a57-b191-fbb86d47b93b
沙箱: no sandbox
代理: no proxy
内存使用: 181.2 MB

qwen-code-export-2026-02-24T07-47-30-106Z.json

[tanzhenxin]

@yang2233 感谢提供的 json trace，我们定位到 API 请求的问题，在核实和处理中

Trace 分析：

• Line 531： 尝试 Edit 失败
• Line 587：模型思考，决定 Read 该文件读取准确的文件内容
• Line 666：原始文件中包含字符串：📊 CSV数据库检查目录路径:
• Line 698：模型生成的回复中认为的需要变更的原始字符串包含：📊 CSV 数据库检查目录路径:，在 CSV 后面加了一个空格

模型生成的回复中会在中英文混杂的时候，加入多余的空格字符，导致 Edit 失败。
#1937 #1923 #1897 都是同样的问题。

之前版本的模型 API 没有碰到过类似问题。