codex - 💡(How to fix) Fix Codex Desktop / Automations local execution environment bug [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#20507Fetched 2026-05-01 05:42:20
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
Participants
Timeline (top)
labeled ×3

Error Message

pgrep: sysmon request failed with error: sysmond service not found

RAW_BUFFERClick to expand / collapse

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

extent analysis

TL;DR

The issue is likely due to differences in the environment between the Codex Desktop automation and the foreground Codex shell, causing Playwright browsers to fail to launch.

Guidance

  • Investigate the environment variables and permissions set in the Codex Desktop automation process to identify any differences with the foreground Codex shell.
  • Compare the output of the diagnostics script run in both environments to understand the specific errors and how they differ.
  • Check the system configuration and services (e.g., sysmond) that might be required for process inspection and Playwright browser launch.
  • Consider running the diagnostics script with elevated privileges or modifying the automation environment to match the foreground shell's environment.

Example

No code snippet is provided as the issue does not specify a particular code block that needs modification.

Notes

The issue seems to be related to the environment and system configuration rather than the Codex App or Playwright itself. The fact that the same setup works in a foreground shell suggests a difference in how the automation process is executed.

Recommendation

Apply workaround: Modify the automation environment to match the foreground shell's environment, focusing on permissions, environment variables, and required system services. This approach is chosen because the issue appears to be related to environmental differences rather than a version-specific bug that could be fixed by upgrading.

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

codex - 💡(How to fix) Fix Codex Desktop / Automations local execution environment bug [1 participants]