Skip to content

browser: Start Xvfb before launching headed Chrome - #15

Merged
yapishu merged 1 commit into
tlon/multi-sessionfrom
codex/headed-browser-startup
Oct 14, 2026
Merged

yapishu merged 1 commit into
tlon/multi-sessionfrom
codex/headed-browser-startup

Conversation

@yapishu

@yapishu yapishu commented Oct 14, 2026

Copy link
Copy Markdown
Collaborator

Setting CHROME_HEADLESS=false makes Chrome fail with “Missing X server or $DISPLAY” because the container entrypoint does not start its installed virtual display server. Start Xvfb and wait for display readiness before starting the API, honor the configured DISPLAY, and configure the test and production manifests to run headed Chrome. Startup fails clearly if the display cannot become ready.

Validation:

  • API build, shell syntax, deployment YAML checks, and diff checks pass.
  • A local smoke run using this branch’s entrypoint and CDP service launches Chrome on X11 without a headless flag and verifies trusted keyboard input.

Base: tlon/multi-session.

@yapishu
yapishu merged commit 9e4405c into tlon/multi-session Oct 14, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant