Anton Panasenko c274a83f8b feat(exec-server): add Noise rendezvous environment (#28774) ...

## Why

Codex can run a remote exec server through the Noise relay, but the
normal
environment-manager path could not establish an
environment-registry-backed
harness connection. Signed rendezvous URLs and harness authorizations
are
short-lived, so reconnects must fetch a fresh bundle instead of
retaining
stale connection credentials. A stalled registry request must also fail
within
the regular remote connection deadline, without exposing these
credentials in
debug logs.

Issue: N/A (internal environment-service integration).

## What Changed

- Add environment-manager configuration for a registry-backed Noise
rendezvous
  environment.
- Request a fresh bundle from
`/cloud/environment/{environment_id}/connect` for every physical harness
  connection, using the existing 10-second remote connection timeout.
- Share the Environment Registry register, connect, and validate wire
payloads
  through `codex-exec-server` and `codex-core-api`.
- Redact the signed rendezvous URL and harness authorization from the
public
  connect response's `Debug` output.
- Add focused coverage for registry bundle retrieval, stalled requests,
and
  credential redaction.

c274a83f8b · 2026-06-17 17:20:53 -07:00

History

..

src

feat(exec-server): add Noise rendezvous environment (#28774)

2026-06-17 17:20:53 -07:00

BUILD.bazel

Add codex-core public API listing (#20243)

2026-04-29 22:58:08 +00:00

Cargo.toml

[codex] Load user instructions through an injected provider (#27101)

2026-06-11 19:28:47 +00:00