Skip to content

Add lazy environment resolution for remote environments#20075

Closed
starr-openai wants to merge 3 commits intostarr/environment-provider-snapshotfrom
starr/environment-provider-lazy-resolution
Closed

Add lazy environment resolution for remote environments#20075
starr-openai wants to merge 3 commits intostarr/environment-provider-snapshotfrom
starr/environment-provider-lazy-resolution

Conversation

@starr-openai
Copy link
Copy Markdown
Contributor

@starr-openai starr-openai commented Apr 28, 2026

Stacked on #20058.

Summary

  • Move EnvironmentConfiguration from a stored websocket URL to a resolver-backed descriptor
  • Add static and closure-backed resolver constructors for default and dynamic provider cases
  • Keep EnvironmentManager as the id -> Environment cache while LazyRemoteExecServerClient resolves the URL on first use

Validation

  • just fmt
  • git diff --check
  • bazel test --bes_backend= --bes_results_url= --test_output=errors //codex-rs/exec-server:all

Thread provider-owned environment resolvers through EnvironmentConfiguration so EnvironmentManager can cache stable Environment handles while remote clients resolve websocket URLs on first use.

Co-authored-by: Codex <noreply@openai.com>
@starr-openai starr-openai changed the title Demo lazy environment resolution Add lazy environment resolution for remote environments Apr 28, 2026
@starr-openai starr-openai marked this pull request as ready for review April 28, 2026 20:11
starr-openai and others added 2 commits April 28, 2026 13:14
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
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