`tmp` foder in .codex
Resolved 💬 1 comment Opened Feb 12, 2026 by sator-imaging Closed Feb 12, 2026
What version of Codex CLI is running?
codex-cli 0.99.0
What subscription do you have?
Plus
Which model were you using?
gpt-5.3-codex
What platform is your computer?
WSL
What terminal emulator and version are you using (if applicable)?
WSL
What issue are you seeing?
I have set these values in config.toml.
[sandbox_workspace_write]
exclude_tmpdir_env_var = false # Allow $TMPDIR
exclude_slash_tmp = false # Allow /tmp
But codex cli still creates tmp folder in my .codex folder. It is very problematic on Windows + WSL environment because some cloud backup tools doesn't recognize the files created by WSL.
Please don't say "Setup your backup tool". As describe above, I have set enough settings so the codex can create files in tmp folder.
Thanks
What steps can reproduce the bug?
- Setup config.toml
- Launch codex
path(may be wrong) is not created butarg0is still created in.codex/tmpfolder (files: .lock, apply_patch, applypatch, codex-linux-sandbox)
What is the expected behavior?
Use the /tmp or $TMPDIR instead.
Additional information
_No response_
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗