jif e476fc16ce Prepare managed network sandbox context (#29456) ...

## Why

Managed network configures commands to use local HTTP and SOCKS proxies.
For commands delegated to the exec server, the proxy environment and the
sandbox policy were prepared separately. On macOS, that meant a command
could receive `HTTPS_PROXY=http://127.0.0.1:43123` while Seatbelt still
denied access to port `43123`.

## What changed

`NetworkProxy` now prepares the command environment and sandbox context
together from the same runtime snapshot:

```text
Prepared managed network
├── command environment: HTTPS_PROXY=http://127.0.0.1:43123
└── sandbox context: allow outbound to 127.0.0.1:43123
```

That context travels with remote exec requests. The exec server
preserves the managed proxy and CA environment, and macOS Seatbelt
allows only the prepared loopback proxy ports without enabling broad
network access or local binding.

The protocol field is optional and the existing enforcement flag remains
in place, preserving compatibility with callers that do not send the new
context.

e476fc16ce · 2026-06-23 20:07:09 +01:00

History

..

src

Prepare managed network sandbox context (#29456)

2026-06-23 20:07:09 +01:00

tests

[codex] Initialize exec-server OpenTelemetry at startup (#25019)

2026-06-18 11:03:42 -07:00

BUILD.bazel

[codex] Move release platform rules into bazel package (#27321)

2026-06-10 19:45:29 +00:00

build.rs

Add WebRTC media transport to realtime TUI (#17058)

2026-04-08 10:26:55 -07:00

Cargo.toml

exec-server: default remote transport to Noise (#26245)

2026-06-15 17:39:00 -07:00