Does the Codex App Work on Linux and WSL? Current Status and Workarounds

Mar 13, 2026

The Problem

I use Linux as my primary development environment. When OpenAI released the Codex desktop app, I wanted to try it. But there’s a problem: the Codex App doesn’t officially support Linux, and WSL users report significant issues.

Here’s what I found when I tried to make it work.

What Linux Users Face

The short answer: Codex App is not available for Linux.

I checked the official documentation and community discussions. There’s no Linux version of the desktop app. One Reddit user put it bluntly:

“I don’t use it, because it does not work on linux.”

This means Linux users have two options:

Continue using the Codex CLI (which works perfectly on Linux)
Find alternatives for session management

WSL Users Have It Worse

I thought Windows users with WSL might have better luck. The reality is worse. Here’s what one user reported:

“It is in unusable state on windows with WSL for me. Zombie processes leaking memory, not picking up existing threads created through cli, using wrong (windows side) configs, etc. Let it cook for a bit more”

The specific WSL issues include:

Zombie processes that leak memory over time
Thread sync problems - the App doesn’t recognize threads created via CLI
Config path confusion - Windows paths vs WSL paths
Git diff rejection - bugs that affect basic workflow

Another user tried setting up shared state between WSL and Windows:

“My repo is in WSL and I went to the effort of setting everything up with shared state so that I could use the app and the CLI interchangeably.”

This sounded promising. But then:

“It then started throwing up security issues as it kept wanting to access my Favorites folder which is protected through Windows.”

And finally:

“I did then moved back to CLI because of rejected git diffs. Seems bugged. I’ll switch back to app when they fix it.”

The message is clear: WSL support is experimental and buggy.

Why This Matters

Many developers use Linux as their primary OS or work in WSL for Windows. The lack of proper support means we miss out on App features like:

Visual interface for managing sessions
Easier multi-project workflows
GUI-based configuration

But the CLI remains fully functional. Let me show you how to work around the App limitations.

Workaround 1: Terminal Multiplexers for Session Persistence

The Codex CLI works fine on Linux. The main disadvantage compared to the App is session management. You can solve this with terminal multiplexers like screen or tmux.

Using Screen

# Start a persistent Codex session
screen -S codex-session
codex

# Detach with Ctrl-A, D
# Reattach later with:
screen -r codex-session

This keeps your Codex session running even when you close the terminal.

Using Tmux for Multiple Projects

Tmux is more powerful for managing multiple Codex sessions:

# Start a new session for project1
tmux new -s project1
codex --project project1

# Detach with Ctrl-B, D
# Create another session for project2
tmux new -s project2
codex --project project2

# List all sessions
tmux ls

# Attach to a specific session
tmux attach -t project1

This approach gives you multi-project management similar to the App, but in the terminal.

Workaround 2: Understanding the WSL Path Problem

If you’re determined to try the App with WSL, understand the root cause of the issues.

The App on Windows expects Windows-style paths:

C:\Users\YourName\.codex

But WSL uses Linux-style paths:

/home/yourname/.codex
# or mounted Windows path:
/mnt/c/Users/YourName/.codex

When you try to symlink these:

# Caution: This causes path confusion
ln -s /mnt/c/Users/YourName/.codex ~/.codex

The App may try to use the wrong config, leading to zombie processes and memory leaks.

Workaround 3: CLI-Only Workflow in WSL

For WSL users, the safest approach is to use the CLI directly within WSL:

# Stay in WSL entirely
# No symlink to Windows
# Use the CLI normally
codex

# For persistence, use tmux within WSL
sudo apt install tmux
tmux new -s codex-work

This avoids the Windows-WSL path confusion entirely.

Workaround 4: Hybrid Approach (With Caveats)

Some users try running the Windows App and CLI in WSL with shared state:

Keep repos in WSL filesystem
Configure both to use the same state directory
Accept that some features may break

But based on user reports, this approach has too many edge cases:

Security prompts for Windows folders
Git diff rejections
Memory leaks from zombie processes

I recommend waiting for official WSL support improvements.

What About Third-Party Tools?

There’s an emerging ecosystem of tools built around Codex. One option is “Agent Sessions” - a third-party tool for managing Codex transcripts:

# Concept: third-party transcript management
# Check GitHub for available tools
# Note: These are community projects, not official

These tools aim to fill the gap for Linux users, but they’re not official solutions.

Common Mistakes to Avoid

Based on the issues I’ve seen:

Forcing shared state without understanding paths - This leads to config conflicts and zombie processes.
Assuming App stability in WSL - The App has known bugs with WSL that haven’t been fixed.
Not filing bug reports - OpenAI won’t know about these issues without community feedback.
Giving up on CLI alternatives - Terminal tools like tmux can provide similar session management.

Current Status Summary

Platform	Codex App	Codex CLI	Recommendation
macOS	Supported	Supported	Use either
Windows (native)	Supported	Supported	Use either
Linux	Not available	Supported	Use CLI
WSL	Buggy	Supported	Use CLI in WSL

Summary

In this post, I explained the current state of Codex App compatibility with Linux and WSL.

The key point is that Linux users should stick with the CLI, which works perfectly. WSL users can try the Windows App with shared state configuration, but expect zombie processes, memory leaks, and config path issues.

For session persistence on Linux or WSL, use terminal multiplexers like screen or tmux. These provide App-like session management without the compatibility problems.

The Codex App is still evolving. Check GitHub issues for WSL support progress, and file bug reports if you encounter problems. Community feedback will help prioritize these fixes.

Final Words + More Resources

My intention with this article was to help others share my knowledge and experience. If you want to contact me, you can contact by email: Email me

Here are also the most important links from this article along with some further resources that will help you in this scope:

Oh, and if you found these resources useful, don’t forget to support me by starring the repo on GitHub!