mirror of
https://github.com/openai/codex.git
synced 2026-11-01 19:33:35 +00:00
## Why Shell execution refactoring in `exec-server` had become split between duplicated code paths, which blocked a clean introduction of the new reusable shell escalation flow. This commit creates a dedicated foundation crate so later shell tooling changes can share one implementation. ## What changed - Added the `codex-shell-escalation` crate and moved the core escalation pieces (`mcp` protocol/socket/session flow, policy glue) that were previously in `exec-server` into it. - Normalized `exec-server` Unix structure under a dedicated `unix` module layout and kept non-Unix builds narrow. - Wired crate/build metadata so `shell-escalation` is a first-class workspace dependency for follow-on integration work. ## Verification - Built and linted the stack at this commit point with `just clippy`. [//]: # (BEGIN SAPLING FOOTER) Stack created with [Sapling](https://sapling-scm.com). Best reviewed with [ReviewStack](https://reviewstack.dev/openai/codex/pull/12556). * #12584 * #12583 * __->__ #12556
22 lines
595 B
Rust
22 lines
595 B
Rust
#[cfg(unix)]
|
|
mod unix {
|
|
mod escalate_client;
|
|
mod escalate_protocol;
|
|
mod escalate_server;
|
|
mod escalation_policy;
|
|
mod socket;
|
|
mod stopwatch;
|
|
|
|
pub use self::escalate_client::run;
|
|
pub use self::escalate_protocol::EscalateAction;
|
|
pub use self::escalate_server::EscalationPolicyFactory;
|
|
pub use self::escalate_server::ExecParams;
|
|
pub use self::escalate_server::ExecResult;
|
|
pub use self::escalate_server::run_escalate_server;
|
|
pub use self::escalation_policy::EscalationPolicy;
|
|
pub use self::stopwatch::Stopwatch;
|
|
}
|
|
|
|
#[cfg(unix)]
|
|
pub use unix::*;
|