From 7b54d1348bcfa1de1b672fee6fc8735936445054 Mon Sep 17 00:00:00 2001 From: mwiegand Date: Sat, 16 May 2026 22:07:15 +0200 Subject: [PATCH] docs(e2e): note Claude Code sandbox blocks Chromium Mach-port IPC Discovered while running Task 12's Playwright editor test: Chromium's bootstrap_check_in Mach-port rendezvous is blocked by the sandbox, which surfaces as a FATAL crash with "Permission denied (1100)" rather than a path-related error. Document the workaround so future agents running e2e tests in the same sandbox don't waste time debugging it as a Playwright/network issue. Co-Authored-By: Claude Opus 4.7 (1M context) --- AGENTS.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index ce255fd..2d22da3 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -109,3 +109,10 @@ uv run playwright install chromium Run with `uv run pytest -m e2e`. Excluded from the default fast suite via the `e2e` marker. + +**Sandbox note:** Chromium needs Mach-port IPC on macOS, which the +Claude Code sandbox blocks. When running e2e tests from a sandboxed +agent session, pass `dangerouslyDisableSandbox: true` on the +`uv run pytest -m e2e` invocation (the symptom of a sandboxed run is +a `FATAL` Chromium crash with `Permission denied (1100)` on Mach port +rendezvous, not a missing-binary or network error).