codex - 💡(How to fix) Fix Resume doesn't work on SLURM [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#17500Fetched 2026-04-12 13:27:34
View on GitHub
Comments
0
Participants
1
Timeline
6
Reactions
0
Author
Participants
Timeline (top)
labeled ×4unlabeled ×2

Root Cause

codex resume never works on slurm. it always shows 0 sessions. i assume this is because resume does not use local files in a directory but uses some files in home dir or something that is messed up with slurm.

RAW_BUFFERClick to expand / collapse

What version of the Codex App are you using (From “About Codex” dialog)?

v0.120.0

What subscription do you have?

Chatgpt PRO

What platform is your computer?

Linux 5.15.0-174-generic x86_64 x86_64

What issue are you seeing?

codex resume never works on slurm. it always shows 0 sessions. i assume this is because resume does not use local files in a directory but uses some files in home dir or something that is messed up with slurm.

What steps can reproduce the bug?

use codex in slurm server

What is the expected behavior?

No response

Additional information

No response

extent analysis

TL;DR

Investigate the file system and directory permissions on the Slurm server to ensure codex resume can access the necessary files.

Guidance

  • Verify the directory and file permissions in the home directory and the directory where codex is run to ensure they are readable and writable by the user running codex.
  • Check the Slurm server's configuration and job submission scripts to see if there are any restrictions on file access or directory usage.
  • Test running codex outside of Slurm to see if the issue is specific to the Slurm environment.
  • Investigate the codex documentation and configuration options to see if there are any settings related to file storage or directory usage that can be adjusted.

Notes

The issue seems to be related to file access or directory permissions, but more information about the Slurm server configuration and the codex application is needed to provide a more specific solution.

Recommendation

Apply workaround: Investigate and adjust the file system and directory permissions on the Slurm server to ensure compatibility with codex.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING