31d0d7a305
As stated in `codex-rs/README.md`: Today, Codex CLI is written in TypeScript and requires Node.js 22+ to run it. For a number of users, this runtime requirement inhibits adoption: they would be better served by a standalone executable. As maintainers, we want Codex to run efficiently in a wide range of environments with minimal overhead. We also want to take advantage of operating system-specific APIs to provide better sandboxing, where possible. To that end, we are moving forward with a Rust implementation of Codex CLI contained in this folder, which has the following benefits: - The CLI compiles to small, standalone, platform-specific binaries. - Can make direct, native calls to [seccomp](https://man7.org/linux/man-pages/man2/seccomp.2.html) and [landlock](https://man7.org/linux/man-pages/man7/landlock.7.html) in order to support sandboxing on Linux. - No runtime garbage collection, resulting in lower memory consumption and better, more predictable performance. Currently, the Rust implementation is materially behind the TypeScript implementation in functionality, so continue to use the TypeScript implmentation for the time being. We will publish native executables via GitHub Releases as soon as we feel the Rust version is usable.
16 lines
425 B
Markdown
16 lines
425 B
Markdown
# oai-codex-ansi-escape
|
|
|
|
Small helper functions that wrap functionality from
|
|
<https://crates.io/crates/ansi-to-tui>:
|
|
|
|
```rust
|
|
pub fn ansi_escape_line(s: &str) -> Line<'static>
|
|
pub fn ansi_escape<'a>(s: &'a str) -> Text<'a>
|
|
```
|
|
|
|
Advantages:
|
|
|
|
- `ansi_to_tui::IntoText` is not in scope for the entire TUI crate
|
|
- we `panic!()` and log if `IntoText` returns an `Err` and log it so that
|
|
the caller does not have to deal with it
|