{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreif55zli7jehamqtoxunnpfelgppjoqb3rullpykkxlppn5dhtk4na",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3miisxpan77o2"
  },
  "path": "/t/codex-hosted-browser-startup-fails-with-enoent-mkdir-playwright-mcp/1378357#post_1",
  "publishedAt": "2026-04-02T07:54:35.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "@playwright"
  ],
  "textContent": "i’m seeing a codex-hosted browser startup failure before any trivial smoke test can begin.\n\nwhen using the codex-hosted browser tool, startup fails immediately with:\n\nError: ENOENT: no such file or directory, mkdir ‘/.playwright-mcp’\n\nexpected: a trivial smoke test on https:// example com should start successfully and write artifacts to repo-local browser directories.\n\nactual: browser startup fails before the smoke test begins, so the browser lane is blocked.\n\nminimal repro:\n\n  * fresh codex session in the repo\n  * trivial browser smoke test against https:// example com\n  * startup fails immediately with the error above\n\n\n\neffective env:\nHOME=/Users/dmitrymatskevich\nXDG_CACHE_HOME=\nTMPDIR=/var/folders/ns/98nq_gpj0nxf9sknqrsqd1qw0000gn/T/\nUSER=dmitrymatskevich\nPWD=/Users/dmitrymatskevich/cursor/personal/health\n\nwhy this looks codex-hosted, not upstream playwright-mcp:\n\n  * i compared codex-hosted launch vs direct fresh launch of @playwright/mcp@0.0.70\n  * direct fresh launch outside codex host works in both isolated mode and persistent mode when explicit writable dirs are provided\n  * in the inspected upstream package/source, i did not find a literal .playwright-mcp path\n\n\n\nthis makes the failure look more like a codex wrapper / env handoff issue than:\n\n  * a repo-local browser scaffold issue\n  * or an upstream @playwright/mcp package bug\n\n\n\nis this a known codex-hosted browser integration bug, and is there a recommended workaround?",
  "title": "Codex-hosted browser startup fails with ENOENT mkdir '/.playwright-mcp'"
}