Skip to content

fix(test): preserve Node in E2E sandbox - #963

Draft
alexsoyes wants to merge 1 commit into
nextfrom
codex/e2e-sandbox-node-isolation
Draft

alexsoyes wants to merge 1 commit into
nextfrom
codex/e2e-sandbox-node-isolation

Conversation

@alexsoyes

@alexsoyes alexsoyes commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor

🎯 What & why

The E2E sandbox excludes directories containing AI tools. When node and codex share a directory, this also removes Node. On this machine, the existing Node availability test fails with expected '' not to be '', blocking the pre-push gate for unrelated changes. This fix was extracted from #747.

🛠️ How it works

The sandbox helper puts Node in a temporary, Node-only directory when its original directory must be filtered: a symlink on Unix or a copy on Windows, cleaned up after the tests. It also excludes opencode. The regression test verifies that Node runs while Codex remains unavailable. Production CLI behavior is unchanged.

🧪 How to verify

From cli/, run pnpm exec vitest run --project=e2e tests/e2e/sandbox-reaches-no-tool-binary.e2e.test.ts. The file passes 4/4 tests on this branch; its existing Node availability test fails on next when Node and Codex are installed together. GitHub checks passed.

✅ I certify

  • I DO CERTIFY I READ EACH LINE OF THE PULL REQUEST BECAUSE I AM A SOFTWARE ENGINEER, NOT A AI PUPPY.

@alexsoyes alexsoyes self-assigned this Oct 6, 2026
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