Increase exec-server environment transport timeouts#21825
Merged
Conversation
f27351a to
bd9d772
Compare
starr-openai
added a commit
that referenced
this pull request
May 8, 2026
Scope the new stdio transport helper to tests so Bazel clippy does not flag it as dead code on production targets. Co-authored-by: Codex <noreply@openai.com>
7792a66 to
b35596b
Compare
Add connect/initialize timeout settings to environment transports, raise the default environment transport timeouts from 5s to 10s, and make the values configurable through CODEX_HOME/environments.toml. Co-authored-by: Codex <noreply@openai.com>
Scope the new stdio transport helper to tests so Bazel clippy does not flag it as dead code on production targets. Co-authored-by: Codex <noreply@openai.com>
b82e2e4 to
388ed85
Compare
Co-authored-by: Codex <noreply@openai.com>
euroelessar
approved these changes
May 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The environment-backed exec-server transport currently hardcodes 5 second connect and initialize timeouts in
client_transport.rs. That is short for SSH-backed stdio environments and remote websocket environments, and there is currently no way to raise those values fromCODEX_HOME/environments.toml.This stacked follow-up raises the default environment transport timeouts and lets each configured environment override them in
environments.toml.What Changed
ExecServerTransportParamsinstead of hardcoding them inconnect_for_transport(...)connect_timeout_secandinitialize_timeout_secto[[environments]]entries inenvironments.tomlconnect_timeout_secon stdio environments because it only applies to websocket transportsStack
Validation
cd /Users/starr/code/codex-worktrees/exec-env-timeouts-config-20260508/codex-rs && just fmt