viyatb-oai 9f6c29e281 Launch managed network proxies on remote executors (#33906) ...

## Why

Remote executions need managed-network proxy listeners in the executor so their
loopback proxy addresses are reachable by the launched process.

## What changed

- Add a capability-gated exec-server protocol field for executor-local proxy
  launch configuration, including network policy, audit metadata, and execution
  attribution.
- Start the proxy while preparing a remote process, replace inherited proxy
  environment variables with its local addresses, and derive the sandbox
  context from its listeners.
- Keep the proxy alive until inherited output streams close, then shut it down.
- Reject unsupported remote settings such as MITM and credential injection.

## Testing

- Cover configuration round trips and rejection of unsupported settings.
- Verify executor-local startup, blocked-domain enforcement, protocol
  compatibility, and proxy lifetime through process closure.

GitOrigin-RevId: c984f54e3e600aa9ebcbf8cf4574046e2c199d11

2026-07-17 21:20:14 +00:00

..

src

Launch managed network proxies on remote executors (#33906)

2026-07-17 21:20:14 +00:00

tests

Resolve and pin MCP OAuth credential stores (#30293)

2026-07-09 18:46:29 -04:00

BUILD.bazel

[3/4] Add executor-backed RMCP HTTP client (#18583)

2026-04-22 17:38:04 -07:00

Cargo.toml

Serialize MCP OAuth credential refreshes (#32229)

2026-07-10 17:59:41 +00:00