codex-rs/core/src/command_safety/mod.rs

pub mod is_dangerous_command;
pub mod is_safe_command;
#[cfg(target_os = "windows")]
pub mod windows_safe_commands;
core: add potentially dangerous command check (#4211) Certain shell commands are potentially dangerous, and we want to check for them. Unless the user has explicitly approved a command, we will always ask them for approval when one of these commands is encountered, regardless of whether they are in a sandbox, or what their approval policy is. The first (of probably many) such examples is `git reset --hard`. We will be conservative and check for any `git reset` 2025-09-25 19:46:20 -07:00			`pub mod is_dangerous_command;`
adds a windows-specific method to check if a command is safe (#4119) refactors command_safety files into its own package, so we can add platform-specific ones Also creates a windows-specific of `is_known_safe_command` that just returns false always, since that is what happens today. 2025-09-24 14:03:43 -07:00			`pub mod is_safe_command;`
			`#[cfg(target_os = "windows")]`
			`pub mod windows_safe_commands;`