[codex] fix browser session isolation defaults#225
Merged
skulidropek merged 8 commits intomainfrom Apr 16, 2026
Merged
Conversation
added 8 commits
April 16, 2026 09:03
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
MCP_PLAYWRIGHT_ISOLATED=1.POSTrequests after transport failures.Why
The MCP Playwright wrapper previously defaulted to isolated browser contexts, so the main agent could see only its own blank Playwright tab instead of the already-open VNC/VK browser tab. The new default shares the main browser session while preserving isolation for managed agent launches.
CI was failing on several independent infrastructure edges: Ubuntu apt mirror
Hash Sum mismatch, slow/cold Docker project builds, and a Bun/global fetch timeout around longPOST /projectscalls. The final patches add retry/by-hash apt refreshes, route Ubuntu security/archive sources to the Azure runner-local mirror, disable API server request timeouts for long-running project creation, use Node HTTP in the host CLI, and give Docker e2e jobs enough time to complete cold builds.Validation
Local checks run:
sudo docker build -f packages/api/Dockerfile --build-arg DOCKER_GIT_CONTROLLER_REV=ci-fix -t docker-git-api-ci-fix .bun run --cwd packages/lib test -- tests/core/templates.test.ts tests/usecases/prepare-files.test.ts tests/usecases/mcp-playwright.test.tsbun run --cwd packages/api test -- tests/agents.test.tsbun run --cwd packages/lib test -- tests/usecases/prepare-files.test.ts tests/usecases/mcp-playwright.test.tsbun run --cwd packages/app test -- tests/docker-git/api-http.test.tsbun run --cwd packages/lib typecheckbun run --cwd packages/api typecheckbun run --cwd packages/app typecheckbun run --cwd packages/app lint:effectbun run --cwd packages/app build:docker-gitbun run lintbun run --cwd packages/lib lintbun run --cwd packages/api lintbun run testbun run api:testbash -n scripts/e2e/clone-auto-open-ssh.shgit diff --checkGitHub checks on
cd883bbare green, including Docker e2e: Clone auto-open SSH, Clone cache, Login context, Runtime volumes + SSH, and OpenCode.Notes
Existing generated projects need env/template regeneration and container restart before the new browser-session defaults apply.