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

Files

T

Michael Bolin 9009490357 fix: use PowerShell to parse PowerShell (#7607 )

Previous to this PR, we used a hand-rolled PowerShell parser in
`windows_safe_commands.rs` to take a `&str` of PowerShell script see if
it is equivalent to a list of `execvp(3)` invocations, and if so, we
then test each using `is_safe_powershell_command()` to determine if the
overall command is safe:


https://github.com/openai/codex/blob/6e6338aa876bb4258abe25b02ac6417b8ea9dff0/codex-rs/core/src/command_safety/windows_safe_commands.rs#L89-L98

Unfortunately, our PowerShell parser did not recognize `@(...)` as a
special construct, so it was treated as an ordinary token. This meant
that the following would erroneously be considered "safe:"

```powershell
ls @(calc.exe)
```

The fix introduced in this PR is to do something comparable what we do
for Bash/Zsh, which is to use a "proper" parser to derive the list of
`execvp(3)` calls. For Bash/Zsh, we rely on
https://crates.io/crates/tree-sitter-bash, but there does not appear to
be a crate of comparable quality for parsing PowerShell statically
(https://github.com/airbus-cert/tree-sitter-powershell/ is the best
thing I found).

Instead, in this PR, we use a PowerShell script to parse the input
PowerShell program to produce the AST.

9009490357 · 2025-12-12 13:06:49 -08:00

History

src

fix: use PowerShell to parse PowerShell (#7607 )

2025-12-12 13:06:49 -08:00

templates

Removed experimental "command risk assessment" feature (#7799 )

2025-12-10 09:48:11 -08:00

tests

Remote compact for API-key users (#7835 )

2025-12-12 10:05:02 -08:00

Cargo.toml

Remove conversation_id and bring back request ID logging (#7830 )

2025-12-10 10:44:12 -08:00

gpt_5_1_prompt.md

chore(prompt) Remove truncation details (#7941 )

2025-12-12 20:21:53 +00:00

gpt_5_2_prompt.md

chore(prompt) Remove truncation details (#7941 )

2025-12-12 20:21:53 +00:00

gpt_5_codex_prompt.md

refactoring with_escalated_permissions to use SandboxPermissions instead (#7750 )

2025-12-10 17:18:48 +00:00

gpt-5.1-codex-max_prompt.md

refactoring with_escalated_permissions to use SandboxPermissions instead (#7750 )

2025-12-10 17:18:48 +00:00

prompt.md

chore(prompt) Update base prompt (#7943 )

2025-12-12 20:50:49 +00:00

README.md

docs: align sandbox defaults, dedupe sections and improve getting started guide (#5357 )

2025-10-19 16:41:10 -07:00

review_prompt.md

docs: Fix markdown list item spacing in codex-rs/core/review_prompt.md (#4144 )

2025-10-30 17:39:21 -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 support matrix is:

macOS

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

Linux

Expects the binary containing codex-core to run the equivalent of codex sandbox linux (legacy alias: 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.