Codex Desktop / Automations local execution environment bug

Open 💬 1 comment Opened Apr 30, 2026 by KeeganEad

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

26.429.20946

What subscription do you have?

Pro

What platform is your computer?

macOS Darwin 23.4.0 arm64 arm

What issue are you seeing?

Codex Desktop local automation cannot launch Playwright browsers on macOS, while foreground Codex shell can

A Codex Desktop cron automation with execution_environment = "local" fails before app/test execution when trying to launch any Playwright browser. The same repo, same user, same Node version, same cwd, and same Playwright install work from a foreground Codex/manual shell.

This appears to be a difference in the automation process environment rather than an application or Playwright test issue.

What steps can reproduce the bug?

A diagnostics script run inside the automation shows process inspection failing:

psSelf: spawnSync ps EPERM
psParent: spawnSync ps EPERM
psList: spawnSync ps EPERM
pgrep: sysmon request failed with error: sysmond service not found
pgrep: Cannot get process list

The same diagnostics script run from a foreground Codex/manual shell succeeds and can inspect its parent process and process table normally.

What is the expected behavior?

Expected Behavior

A local Codex automation should be able to launch Playwright browsers the same way a foreground Codex shell can.

Actual Behavior

Inside the automation, all Playwright browser preflight attempts fail before any page opens:

Additional information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗