Windows: various symbols and escaping

Open 💬 2 comments Opened Aug 27, 2026 by drrrx5

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the Codex App are you using (From “About Codex” dialog)?

26.820.60940

What subscription do you have?

pro

What platform is your computer?

x64

What issue are you seeing?

能不能对windows好一点我一直感觉太受苦以下是三段gpt5.6 sol的原话

【第一次执行被 PowerShell 把 Maven 的逗号测试列表解析成参数分隔，尚未进入编译；这是命令转义问题，不是测试结果。我改为把 -Dtest=... 作为单个参数重新运行。

已运行 mvn -pl brain-api-app -am -DskipTests=false '-Dtest=GrowthInterfaceFeedbackContractTest,ParentGrowthRewardConsumerTest,ChildGrowthRewardClaimsConsumerTest' -Dsurefire.failIfNoSpecifiedTests=false test】

【第二次仍未编译：PowerShell 把带点号的 -Dsurefire.failIfNoSpecifiedTests=false 也拆坏了。所有 Maven -D 参数统一加引号后再跑；不会把这两次算进测试执行数。】

【历史对照已找到，结论很明确：

这不是今天的新客户端回归。至少从 2026-08-20、08-24、08-25、08-26 的用户消息开始，同一路径在会话 JSONL 中都显示为 20260819\_2.0...。
2026-08-24 同样是 gpt-5.6-sol：模型收到带转义的文本后，实际工具调用正确使用了 20260819_2.0...。所以以前不需要你提醒，也不需要额外规则。
本次是我的推理错误：第一次 Test-Path 失败后，我没有回到界面截图和父目录事实核对，反而把 Markdown 转义当成用户键入的 Windows 分隔符。
当前文本链路不是“精确字节通道”。对普通说明无碍，但复杂部署命令若从聊天正文手工复制，确实存在风险；高风险语法必须以仓库文件/附件等精确来源执行，不能靠我猜转义。】

What steps can reproduce the bug?

win11 随便写个电脑文件路径就行

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 1 day ago

English translation:

What version of the Codex App are you using (From “About Codex” dialog)?

26.820.60940

What subscription do you have?

pro

What platform is your computer?

x64

What issue are you seeing?

Could you please provide better support for Windows? I constantly feel like I'm suffering. Below are three verbatim quotes from gpt5.6 sol:

【On the first attempt, PowerShell parsed Maven's comma-separated test list as argument separators, so compilation had not started yet; this is a command-escaping issue, not a test result. I will rerun it with -Dtest=... passed as a single argument.

Ran mvn -pl brain-api-app -am -DskipTests=false '-Dtest=GrowthInterfaceFeedbackContractTest,ParentGrowthRewardConsumerTest,ChildGrowthRewardClaimsConsumerTest' -Dsurefire.failIfNoSpecifiedTests=false test】

【The second attempt still did not compile: PowerShell also mangled -Dsurefire.failIfNoSpecifiedTests=false, which contains periods. I will quote all Maven -D arguments consistently and run it again; these two attempts will not be counted toward the number of test runs.】

【The historical comparison has been found, and the conclusion is very clear:

This is not a new client regression introduced today. In user messages from at least 2026-08-20, 08-24, 08-25, and 08-26, the same path appears in the session JSONL as 20260819\_2.0....
On 2026-08-24, it was also gpt-5.6-sol: after the model received the escaped text, the actual tool call correctly used 20260819_2.0.... So previously, you did not need to remind it, nor were any additional rules needed.
This time, it was an error in my reasoning: after the first Test-Path failed, I did not go back to verify against the UI screenshot and the facts from the parent directory. Instead, I treated Markdown escaping as a Windows separator entered by the user.
The current text pipeline is not an “exact byte channel.” This does not affect ordinary descriptions, but there is indeed a risk when complex deployment commands are manually copied from the chat body; high-risk syntax must be executed from an exact source such as a repository file or attachment, rather than relying on me to guess the escaping.】

What steps can reproduce the bug?

On Windows 11, just write any computer file path.

What is the expected behavior?

_No response_

Additional information

_No response_

github-actions[bot] contributor · 1 day ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

#39902