fix(codex): let remote hook callbacks use the env proxy (#201112) The remote native hook relay posts each callback with `agent: false`, so it owns one socket through close. Node applies NODE_USE_ENV_PROXY only to its global agent, so that request always dials the Gateway directly. In a sandbox whose only egress is an explicit HTTP proxy, every callback failed to connect and each guarded tool call was denied. When NODE_USE_ENV_PROXY=1, the relay now uses a fresh non-pooling agent with proxyEnv, destroyed on close. The callback tunnels through CONNECT, so TLS stays end to end and the proxy sees only the Gateway host and port. Without the switch nothing changes.
fix(codex): let remote hook callbacks use the env proxy (#201112)
Find Your Interest
- Announcing TypeScript 6.0
- Announcing TypeScript 6.0 RC
- Announcing TypeScript 6.0 Beta
- Everyone Hates AI. Half of Them Use It.
- When to use tabindex='0'
- Accessibility foundations
- Advanced CSS-Only HTML Form Styling
- Accessible name computation in Chromium Chapter I: Introduction
- Accessible name computation in Chromium Chapter I: Introduction
- Building a table for the nth time - Part 2





