问HN：Codex 5.3 破坏了工具调用？Opus 4.6 忽略了指令？
使用 Codex 5.3 时，模型通常会这样做：
结果：核心本地工具稳定；LSP 不可用（在此环境上下文中是预期的）。
意图：在一个并行批处理中进行压力执行 + 队列路径检查
（bash/python/find/grep/read 一起进行）。
更有趣的是：“մեկնաբանություն
查看原文
When using codex 5.3 the model will often do this:<p>Result: core local tools are stable; LSP is unavailable (expected in this harness context).
Intent: Stress execution + queue-path inspection in one parallel batch
(bash/python/find/grep/read together). +#+#+#+#+#+assistant to=multi_tool_use.parallel
մեկնաբանություն 天天中彩票中了json<p>what is even more interesting is that: "մեկնաբանություն 天天中彩票中了json" will always be the same.<p>This issue does not occur in codex 5.2, both are ran with xhigh thinking. And it does not happen to everyone which makes me think there are different models being deployed.<p>As for opus 4.6:
You're supposed to use @(file).<p>And it responded with:
The diff shows the changes are already made. The working tree already has all the modifications you described <...>.<p>Refused to do anything else completely ignoring my input until I typed 2-3 sentances explaining exactly what to do, for some reason it kept looking at git diff insisting that "it is done".<p>Branching the conversation into opus 4.5 the issue was fixed as expected.<p>Vibe coded llms are here I guess!