›_ Codex Issues
Codex Issues / #29454

Codex app on Windows: WSL agent mode fails with: Error creating task Invalid request: AbsolutePathBuf deserialized without a base path , exactly the same as #16815

Open 💬 2 comments Opened Jun 22, 2026 by leonardofoderaro
💡 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.616.51431 • Released 21 giu 2026

What subscription do you have?

Enterprise

What platform is your computer?

Win 11 pro

What issue are you seeing?

exactly as https://github.com/openai/codex/issues/16815

trying a new simple chat I get this

<img width="528" height="60" alt="Image" src="https://github.com/user-attachments/assets/ec77f954-e6d9-487a-b631-1a08c66fcc90" />

What steps can reproduce the bug?

A simple new chat

What is the expected behavior?

it should work

Additional information

_No response_

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 2 months ago

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

  • #16815

Powered by Codex Action

Knoxmortis · 2 months ago

I’m seeing the same AbsolutePathBuf/base path failure on Windows Codex Desktop 26.623.5175.0.

My issue: #30373
Feedback ID: no-active-thread-019f0a14-dfd3-7742-8f7a-300942fcb7fb

Extra detail:

  • Old/existing chats still work.
  • Desktop-created new chats fail.
  • Remote/mobile-created chats work and then appear on desktop.
  • Codex CLI works.
  • Node/npm doctor passes.
  • Reset-AppxPackage did not fix it.
  • Renaming local app package state did not fix it.

So it may not be limited to WSL agent mode; it looks like desktop new-task creation is losing the workspace/base path before thread creation.