We ran into issues with Codex on Windows + PowerShell, so we decided to work around it.
标题备选（数字钩子，需带上查询语句与日期）： 「4,269 条 issue 标题里带 Windows：Codex 在 PowerShell 下的问题是结构性的」 「Codex CLI 有 203 条标题含 PowerShell 的 issue，我们不再指望修好它」 先说结论：Codex 在 Windows 上不是不能用，而是 你把任务规模化之后，被 PowerShell 打断的次数会变成一种固定成本 。我们试过的方向里，性价比最高的不是写更长的提示词教模型写 PowerShell，而是把执行面换到 Linux 用户态。 这篇先把网上能查到的真实问题摊开（都带链接，可以自己核），再讲我们在 TaskHandoff 里选的那条路，以及这条路的代价。 一、先看真实问题：四类，且不是同一类 A 类：PowerShell 不是 Bash，模型的命令会持续撞墙 Codex CLI 在…
The Codex AI model has issues with PowerShell on Windows, with 4,269 issues reported on GitHub related to Windows and 203 related to PowerShell. The problems are categorized into four types: shell semantic differences, Windows security models and sandbox implementations, cross-filesystem mappings, and third-party security software.
To address these issues, TaskHandoff has decided to run tasks on Linux containers, using Windows only as an entry point. This approach solves problems related to PowerShell and Windows sandbox policies, but requires Docker to be installed on Windows and users to adapt to Linux tools.
Written by urgent.news from Dev.to's report — not a translation of it. Machine-written — may contain errors; check the original before relying on it.
