Headless Chrome now runs inside the sandbox
Commands that start Chrome, like a Remotion render or a page screenshot, used to crash in the sandbox. They now run there like any other command.
When Chrome starts, it registers a few named channels with macOS for its own processes and its crash reporter. The sandbox refused that, so the browser quit at launch and the agent could not render a video, take a screenshot of a page it built, or run browser tests.
The sandbox now lets a command register only names that begin with Chrome's and Chromium's own prefixes. Everything else stays as it was: writes stay in the project, temp folders and tool caches, private places stay unreadable, and the app's own socket stays out of reach.