The commit ed1e1cb, pushed to the amontlabs/lcu repository on November 2, 2026, fixed the problem where the Windows build failed at the temp folder cleanup stage. It is a repository intended to make the Codex computer use module, which is separated from the app, usable in any harness. The point that was stuck was the deletion of the temporary directory after the build artifacts had already all been produced.
The fix touches two scripts. scripts/build_bundle.py was changed to ignore errors that occur when deleting the temporary directory, and scripts/provision_agent_tools.py now moves the temporary scratch directory fetched by npm to the parent folder rather than inside the release folder. On Windows, when antivirus holds a file, directory deletion is refused and the build fails with error code 145 (WinError 145); with this approach, a cleanup failure no longer blocks the build, and the remaining residue does not end up in the distribution archive either.
The new test reproduces that situation directly. tests/test_build_windows.py intercepts os.rmdir calls to create a situation where directory deletion is refused, and checks whether the .zip.sha256 checksum file was generated after the build and whether there are no .agent-tools- entries inside the archive. However, what was fixed is the symptom. Because cleanup errors are ignored, files that remain are still left on disk, and the follow-up remedy is not included in this commit.
So within the extent that can be read, things are clear. The fact that the Windows build no longer breaks at the cleanup stage is confirmed by the test, but this commit contains no separate release version number or package composition changes. The repository description says only that the aim is to detach Codex computer use from the app and use it in a harness-agnostic way, so to see what changed in the distribution artifacts you have to follow the commit diff.