2 people reported

All time, since Oct 8.

Stale symlinked writable root

“A stale symlinked writable root prevents both shell execution and Computer Use from starting.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/codex/issues/9939/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Stale symlinked writable root blocks shell and Computer Use. After the project source folder is corrected to a canonical non-symlink path, chats still list the old symlinked root; restarting did not help.

Is this your bug?

File my report
Where
macOS desktop app
Error text
UnsupportedOperation("writable root /Users/<user>/Desktop/Workspace contains symlink component /Users/<user>/Desktop/Workspace; symlinked writable roots are not supported.")
Platforms
macOS
How bad
Stops work: a core feature can't be used.

Not quite your bug?

  1. Local Work chats fail6 people
  2. Projectless task folder ignored4 people
  3. Root read access sandbox error12 people

Original reports2, newest first

  1. macOS app: fresh chat inherits stale symlinked writable root, blocking shell and Computer UseOn GitHub#54290
  2. macOS: existing chat retains invalid symlinked writable root after project source-folder correctionOn GitHub#52154

Do you work on Codex?

Claim its RAP Sheet to see what your users report and answer them in one place.