mirror of https://github.com/pchuan98/codex.git synced 2026-07-01 00:31:56 +08:00

Files

T

Adam Perry @ OpenAI f8850cab1d app-server: preserve target-native environment cwd (#28146 )

## Why

app-server may run on a different OS from the selected exec-server
environment. Parsing that environment’s cwd with the Codex host’s path
rules prevents thread startup.

## What

Carry environment cwd values as `LegacyAppPathString` at the app-server
boundary and `PathUri` internally. Existing tool-call schemas and
relative-path behavior stay host-native; remaining local-only consumers
convert explicitly and leave follow-up TODOs.

The Wine integration test verifies app-server can start a thread and
complete an ordinary turn with a Windows environment cwd from Linux.

## Validation

- `bazel test //codex-rs/core/tests/remote_env_windows:smoke-test
--test_output=errors`
- focused app-server environment-selection and protocol schema tests
- scoped Clippy for `codex-core` and `codex-app-server-protocol`

f8850cab1d · 2026-06-16 21:42:28 +00:00

History

BUILD.bazel

app-server: preserve target-native environment cwd (#28146 )

2026-06-16 21:42:28 +00:00

README.md

Run core integration tests against a Wine-backed Windows executor (#28401 )

2026-06-16 00:38:41 +00:00

remote_env_windows_test.rs

app-server: preserve target-native environment cwd (#28146 )

2026-06-16 21:42:28 +00:00

README.md

Windows remote-environment test

This Bazel-only test_codex integration test runs a Windows exec-server fixture under pinned Wine and exercises the normal model tool-call and remote-execution path.

Running the test

bazel test \
  //codex-rs/core/tests/remote_env_windows:smoke-test \
  --test_output=errors

No system Wine is required. Every process gets a fresh WINEPREFIX and isolated wineserver.

Current limitations

ConPTY/TTY behavior is not yet covered.
Wine loads shared objects and PE DLLs at runtime, so the host must still provide the declared compatible glibc version.
The target is intentionally limited to x86-64 for simplicity. It can expand if we find aarch64-specific behavior worth testing.