Codex Chrome plugin still fails after the July 20 update with a process property error
garlos · ghdev · 2026-07-21
This issue reports that the Codex Chrome plugin still fails to attach after the 2026-07-20 update.
The failure happens in setupBrowserRuntime({ globals: globalThis }) before the agent is created, with:
- TypeError: Cannot redefine property: process
- hasAgent: false
- hasBrowsers: false
- agent.browsers.get("extension") never reached
The reporter says this blocks Codex from connecting to Chrome for local app debugging and testing, despite Chrome running and the extension being installed and enabled.
More from coding & agent
- Agent verified 'success' after double-voting: a lesson in harness vs model bugs — TejasKumar_ · 2026-10-26
- diginomica: agentic automation hype is overdone, and 'The Hackening' of enterprise security has begun — jonerp · 2026-10-26
- 'Vibe verification': ~60% of AI-written formal specs prove the wrong property — basedjensen · 2026-10-26
- Devin launches Security suite powered by Claude Mythos with $100M+ credits — DevinAI · 2026-10-26
- HackBench injects reward hacks into agent trajectories to stress-test monitors — DanielKhashabi · 2026-10-26
- Hugging Face ships hf CLI updates: deduped cache saves 19GB, faster buckets, retryable GPU jobs — yb2698 · 2026-10-26