Windows 11 WSL Issue

Resolved 💬 2 comments Opened Jul 20, 2025 by PavelAgurov Closed Aug 18, 2025

What version of Codex is running?

v1.7.15

Which model were you using?

_No response_

What platform is your computer?

Windows 11 WSL (Linux)

What steps can reproduce the bug?

Codex is always frozen under Windows 11 WSL:

2025-07-20 21:37:57 +04 INFO    Starting Codex v1.7.15
2025-07-20 21:37:57 +04 INFO    Ensuring database is correct and up to date...
2025-07-20 21:37:57 +04 INFO    Database up to date.
2025-07-20 21:37:57 +04 INFO    Database ready.
2025-07-20 21:37:58 +04 INFO    Deleted 44 orphan LibrarianStatuses.
2025-07-20 21:38:01 +04 INFO    root_path:
2025-07-20 21:38:01 +04 INFO    Running Codex v1.7.15
[2025-07-20 21:38:01 +0400] [206140] [INFO] Running on http://0.0.0.0:9810 (CTRL + C to quit)
2025-07-20 21:38:01 +04 INFO    BroadcastListener started.
2025-07-20 21:38:01 +04 INFO    LibrarianDaemon started all threads.
2025-07-20 21:38:01 +04 INFO    LibrarianDaemon ready for tasks.
2025-07-20 21:38:01 +04 INFO    Started watching library /mnt/c/DiskD/GptPOCs/MigrationTest/MigrationTest7-codex/config/custom-covers with poll
2025-07-20 21:38:01 +04 INFO    Library /mnt/c/DiskD/GptPOCs/MigrationTest/MigrationTest7-codex/config/custom-covers waiting for manual poll.
2025-07-20 21:38:01 +04 INFO    Looking for search entries to update since the fracturing of the multiverse...
2025-07-20 21:38:01 +04 INFO    No search entries to update.
2025-07-20 21:38:01 +04 INFO    Looking for missing search entries to create...
2025-07-20 21:38:01 +04 INFO    No search entries to create.
2025-07-20 21:38:01 +04 INFO    Search index updated in a moment.

After it nothing happened.

What is the expected behavior?

_No response_

What do you see instead?

_No response_

Additional information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗