Files

eddy-win 050b9baeb6 Bridge command generation to powershell when on Windows (#2319 )

## What? Why? How?
- When running on Windows, codex often tries to invoke bash commands,
which commonly fail (unless WSL is installed)
- Fix: Detect if powershell is available and, if so, route commands to
it
- Also add a shell_name property to environmental context for codex to
default to powershell commands when running in that environment

## Testing
- Tested within WSL and powershell (e.g. get top 5 largest files within
a folder and validated that commands generated were powershell commands)
- Tested within Zsh
- Updated unit tests

---------

Co-authored-by: Eddy Escardo <eddy@openai.com>

2025-08-20 16:30:34 -07:00

src

Bridge command generation to powershell when on Windows (#2319 )

2025-08-20 16:30:34 -07:00

tests

Bridge command generation to powershell when on Windows (#2319 )

2025-08-20 16:30:34 -07:00

Cargo.toml

Bridge command generation to powershell when on Windows (#2319 )

2025-08-20 16:30:34 -07:00

prompt.md

fix: remove behavioral prompting from update_plan tool def (#2261 )

2025-08-13 19:05:13 +00:00

README.md

fix: support special --codex-run-as-apply-patch arg (#1702 )

2025-07-28 09:26:44 -07:00

README.md

codex-core

This crate implements the business logic for Codex. It is designed to be used by the various Codex UIs written in Rust.

Dependencies

Note that codex-core makes some assumptions about certain helper utilities being available in the environment. Currently, this

macOS

Expects /usr/bin/sandbox-exec to be present.

Linux

Expects the binary containing codex-core to run the equivalent of codex debug landlock when arg0 is codex-linux-sandbox. See the codex-arg0 crate for details.

All Platforms

Expects the binary containing codex-core to simulate the virtual apply_patch CLI when arg1 is --codex-run-as-apply-patch. See the codex-arg0 crate for details.