2025-07-31 00:43:21 -07:00
|
|
|
use std::collections::HashMap;
|
2025-08-07 18:26:47 -07:00
|
|
|
use std::collections::VecDeque;
|
2025-05-04 11:12:40 -07:00
|
|
|
use std::path::PathBuf;
|
2025-05-07 08:37:48 -07:00
|
|
|
use std::sync::Arc;
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
|
2025-07-27 20:01:35 -07:00
|
|
|
use codex_core::codex_wrapper::CodexConversation;
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
use codex_core::codex_wrapper::init_codex;
|
2025-04-27 21:47:50 -07:00
|
|
|
use codex_core::config::Config;
|
2025-07-16 15:11:18 -07:00
|
|
|
use codex_core::protocol::AgentMessageDeltaEvent;
|
2025-05-13 20:44:42 -07:00
|
|
|
use codex_core::protocol::AgentMessageEvent;
|
2025-07-16 15:11:18 -07:00
|
|
|
use codex_core::protocol::AgentReasoningDeltaEvent;
|
2025-05-13 20:44:42 -07:00
|
|
|
use codex_core::protocol::AgentReasoningEvent;
|
2025-08-05 01:56:13 -07:00
|
|
|
use codex_core::protocol::AgentReasoningRawContentDeltaEvent;
|
|
|
|
|
use codex_core::protocol::AgentReasoningRawContentEvent;
|
2025-05-13 20:44:42 -07:00
|
|
|
use codex_core::protocol::ApplyPatchApprovalRequestEvent;
|
2025-08-05 22:44:27 -07:00
|
|
|
use codex_core::protocol::BackgroundEventEvent;
|
2025-05-13 20:44:42 -07:00
|
|
|
use codex_core::protocol::ErrorEvent;
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
use codex_core::protocol::Event;
|
|
|
|
|
use codex_core::protocol::EventMsg;
|
2025-05-13 20:44:42 -07:00
|
|
|
use codex_core::protocol::ExecApprovalRequestEvent;
|
|
|
|
|
use codex_core::protocol::ExecCommandBeginEvent;
|
|
|
|
|
use codex_core::protocol::ExecCommandEndEvent;
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
use codex_core::protocol::InputItem;
|
2025-05-13 20:44:42 -07:00
|
|
|
use codex_core::protocol::McpToolCallBeginEvent;
|
|
|
|
|
use codex_core::protocol::McpToolCallEndEvent;
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
use codex_core::protocol::Op;
|
2025-05-13 20:44:42 -07:00
|
|
|
use codex_core::protocol::PatchApplyBeginEvent;
|
2025-05-19 16:08:18 -07:00
|
|
|
use codex_core::protocol::TaskCompleteEvent;
|
feat: show number of tokens remaining in UI (#1388)
When using the OpenAI Responses API, we now record the `usage` field for
a `"response.completed"` event, which includes metrics about the number
of tokens consumed. We also introduce `openai_model_info.rs`, which
includes current data about the most common OpenAI models available via
the API (specifically `context_window` and `max_output_tokens`). If
Codex does not recognize the model, you can set `model_context_window`
and `model_max_output_tokens` explicitly in `config.toml`.
When then introduce a new event type to `protocol.rs`, `TokenCount`,
which includes the `TokenUsage` for the most recent turn.
Finally, we update the TUI to record the running sum of tokens used so
the percentage of available context window remaining can be reported via
the placeholder text for the composer:

We could certainly get much fancier with this (such as reporting the
estimated cost of the conversation), but for now, we are just trying to
achieve feature parity with the TypeScript CLI.
Though arguably this improves upon the TypeScript CLI, as the TypeScript
CLI uses heuristics to estimate the number of tokens used rather than
using the `usage` information directly:
https://github.com/openai/codex/blob/296996d74e345b1b05d8c3451a06ace21c5ada96/codex-cli/src/utils/approximate-tokens-used.ts#L3-L16
Fixes https://github.com/openai/codex/issues/1242
2025-06-25 23:31:11 -07:00
|
|
|
use codex_core::protocol::TokenUsage;
|
2025-08-05 22:44:27 -07:00
|
|
|
use codex_core::protocol::TurnDiffEvent;
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
use crossterm::event::KeyEvent;
|
2025-07-31 17:10:52 -07:00
|
|
|
use crossterm::event::KeyEventKind;
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
use ratatui::buffer::Buffer;
|
2025-08-06 12:03:45 -07:00
|
|
|
use ratatui::layout::Constraint;
|
|
|
|
|
use ratatui::layout::Layout;
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
use ratatui::layout::Rect;
|
|
|
|
|
use ratatui::widgets::Widget;
|
|
|
|
|
use ratatui::widgets::WidgetRef;
|
|
|
|
|
use tokio::sync::mpsc::UnboundedSender;
|
2025-05-07 08:37:48 -07:00
|
|
|
use tokio::sync::mpsc::unbounded_channel;
|
2025-08-05 22:44:27 -07:00
|
|
|
use tracing::info;
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
|
|
|
|
|
use crate::app_event::AppEvent;
|
2025-05-15 14:50:30 -07:00
|
|
|
use crate::app_event_sender::AppEventSender;
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
use crate::bottom_pane::BottomPane;
|
|
|
|
|
use crate::bottom_pane::BottomPaneParams;
|
2025-07-28 12:00:06 -07:00
|
|
|
use crate::bottom_pane::CancellationEvent;
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
use crate::bottom_pane::InputResult;
|
2025-08-07 18:26:47 -07:00
|
|
|
use crate::exec_command::strip_bash_lc_and_escape;
|
2025-07-30 10:05:40 -07:00
|
|
|
use crate::history_cell::CommandOutput;
|
|
|
|
|
use crate::history_cell::HistoryCell;
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
use crate::history_cell::PatchEventType;
|
2025-08-07 18:26:47 -07:00
|
|
|
use crate::markdown_stream::MarkdownNewlineCollector;
|
|
|
|
|
use crate::markdown_stream::RenderedLineStreamer;
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
use crate::user_approval_widget::ApprovalRequest;
|
2025-06-28 15:04:23 -07:00
|
|
|
use codex_file_search::FileMatch;
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
|
2025-07-31 00:43:21 -07:00
|
|
|
struct RunningCommand {
|
|
|
|
|
command: Vec<String>,
|
|
|
|
|
#[allow(dead_code)]
|
|
|
|
|
cwd: PathBuf,
|
|
|
|
|
}
|
|
|
|
|
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
pub(crate) struct ChatWidget<'a> {
|
2025-05-15 14:50:30 -07:00
|
|
|
app_event_tx: AppEventSender,
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
codex_op_tx: UnboundedSender<Op>,
|
|
|
|
|
bottom_pane: BottomPane<'a>,
|
2025-08-06 12:03:45 -07:00
|
|
|
active_history_cell: Option<HistoryCell>,
|
2025-04-27 21:47:50 -07:00
|
|
|
config: Config,
|
2025-05-17 09:00:23 -07:00
|
|
|
initial_user_message: Option<UserMessage>,
|
2025-08-07 05:17:18 -07:00
|
|
|
total_token_usage: TokenUsage,
|
|
|
|
|
last_token_usage: TokenUsage,
|
2025-08-07 18:26:47 -07:00
|
|
|
// Newline-gated markdown streaming state
|
|
|
|
|
reasoning_collector: MarkdownNewlineCollector,
|
|
|
|
|
answer_collector: MarkdownNewlineCollector,
|
|
|
|
|
reasoning_streamer: RenderedLineStreamer,
|
|
|
|
|
answer_streamer: RenderedLineStreamer,
|
2025-07-31 00:43:21 -07:00
|
|
|
running_commands: HashMap<String, RunningCommand>,
|
2025-08-04 21:23:22 -07:00
|
|
|
current_stream: Option<StreamKind>,
|
2025-08-07 18:26:47 -07:00
|
|
|
// Track header emission per stream kind to avoid cross-stream duplication
|
|
|
|
|
answer_header_emitted: bool,
|
|
|
|
|
reasoning_header_emitted: bool,
|
2025-08-04 21:23:22 -07:00
|
|
|
live_max_rows: u16,
|
2025-08-07 18:26:47 -07:00
|
|
|
task_complete_pending: bool,
|
|
|
|
|
finishing_after_drain: bool,
|
|
|
|
|
// Queue of interruptive UI events deferred during an active write cycle
|
|
|
|
|
interrupt_queue: VecDeque<QueuedInterrupt>,
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
}
|
|
|
|
|
|
2025-05-17 09:00:23 -07:00
|
|
|
struct UserMessage {
|
|
|
|
|
text: String,
|
|
|
|
|
image_paths: Vec<PathBuf>,
|
|
|
|
|
}
|
|
|
|
|
|
2025-08-04 21:23:22 -07:00
|
|
|
#[derive(Debug, Clone, Copy, PartialEq, Eq)]
|
|
|
|
|
enum StreamKind {
|
|
|
|
|
Answer,
|
|
|
|
|
Reasoning,
|
|
|
|
|
}
|
|
|
|
|
|
2025-08-07 18:26:47 -07:00
|
|
|
#[derive(Debug)]
|
|
|
|
|
enum QueuedInterrupt {
|
|
|
|
|
ExecApproval(String, ExecApprovalRequestEvent),
|
|
|
|
|
ApplyPatchApproval(String, ApplyPatchApprovalRequestEvent),
|
|
|
|
|
ExecBegin(ExecCommandBeginEvent),
|
|
|
|
|
McpBegin(McpToolCallBeginEvent),
|
|
|
|
|
McpEnd(McpToolCallEndEvent),
|
|
|
|
|
}
|
|
|
|
|
|
2025-05-17 09:00:23 -07:00
|
|
|
impl From<String> for UserMessage {
|
|
|
|
|
fn from(text: String) -> Self {
|
|
|
|
|
Self {
|
|
|
|
|
text,
|
|
|
|
|
image_paths: Vec::new(),
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
fn create_initial_user_message(text: String, image_paths: Vec<PathBuf>) -> Option<UserMessage> {
|
|
|
|
|
if text.is_empty() && image_paths.is_empty() {
|
|
|
|
|
None
|
|
|
|
|
} else {
|
|
|
|
|
Some(UserMessage { text, image_paths })
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
impl ChatWidget<'_> {
|
2025-08-07 18:26:47 -07:00
|
|
|
fn header_line(kind: StreamKind) -> ratatui::text::Line<'static> {
|
|
|
|
|
use ratatui::style::Stylize;
|
|
|
|
|
match kind {
|
|
|
|
|
StreamKind::Reasoning => ratatui::text::Line::from("thinking".magenta().italic()),
|
|
|
|
|
StreamKind::Answer => ratatui::text::Line::from("codex".magenta().bold()),
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
fn line_is_blank(line: &ratatui::text::Line<'_>) -> bool {
|
|
|
|
|
if line.spans.is_empty() {
|
|
|
|
|
return true;
|
|
|
|
|
}
|
|
|
|
|
line.spans.iter().all(|s| s.content.trim().is_empty())
|
|
|
|
|
}
|
|
|
|
|
/// Periodic tick to commit at most one queued line to history with a small delay,
|
|
|
|
|
/// animating the output.
|
|
|
|
|
pub(crate) fn on_commit_tick(&mut self) {
|
|
|
|
|
// Choose the active streamer
|
|
|
|
|
let (streamer, kind_opt) = match self.current_stream {
|
|
|
|
|
Some(StreamKind::Reasoning) => {
|
|
|
|
|
(&mut self.reasoning_streamer, Some(StreamKind::Reasoning))
|
|
|
|
|
}
|
|
|
|
|
Some(StreamKind::Answer) => (&mut self.answer_streamer, Some(StreamKind::Answer)),
|
|
|
|
|
None => {
|
|
|
|
|
// No active stream. Nothing to animate.
|
|
|
|
|
return;
|
|
|
|
|
}
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
// Prepare header if needed
|
|
|
|
|
let mut lines: Vec<ratatui::text::Line<'static>> = Vec::new();
|
|
|
|
|
if let Some(k) = kind_opt {
|
|
|
|
|
let header_needed = match k {
|
|
|
|
|
StreamKind::Reasoning => !self.reasoning_header_emitted,
|
|
|
|
|
StreamKind::Answer => !self.answer_header_emitted,
|
|
|
|
|
};
|
|
|
|
|
if header_needed {
|
|
|
|
|
lines.push(Self::header_line(k));
|
|
|
|
|
match k {
|
|
|
|
|
StreamKind::Reasoning => self.reasoning_header_emitted = true,
|
|
|
|
|
StreamKind::Answer => self.answer_header_emitted = true,
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
let step = streamer.step(self.live_max_rows as usize);
|
|
|
|
|
if !step.history.is_empty() || !lines.is_empty() {
|
|
|
|
|
lines.extend(step.history);
|
|
|
|
|
self.app_event_tx.send(AppEvent::InsertHistory(lines));
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
// If streamer is now idle and there is no more active stream data, finalize state.
|
|
|
|
|
let is_idle = streamer.is_idle();
|
|
|
|
|
if is_idle {
|
|
|
|
|
// Stop animation ticks between bursts.
|
|
|
|
|
self.app_event_tx.send(AppEvent::StopCommitAnimation);
|
|
|
|
|
if self.finishing_after_drain {
|
|
|
|
|
// Final cleanup once fully drained at end-of-stream.
|
|
|
|
|
self.current_stream = None;
|
|
|
|
|
self.finishing_after_drain = false;
|
|
|
|
|
if self.task_complete_pending {
|
|
|
|
|
self.bottom_pane.set_task_running(false);
|
|
|
|
|
self.task_complete_pending = false;
|
|
|
|
|
}
|
|
|
|
|
// After the write cycle completes, release any queued interrupts.
|
|
|
|
|
self.flush_interrupt_queue();
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
fn is_write_cycle_active(&self) -> bool {
|
|
|
|
|
self.current_stream.is_some()
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
fn flush_interrupt_queue(&mut self) {
|
|
|
|
|
while let Some(q) = self.interrupt_queue.pop_front() {
|
|
|
|
|
match q {
|
|
|
|
|
QueuedInterrupt::ExecApproval(id, ev) => self.handle_exec_approval_now(id, ev),
|
|
|
|
|
QueuedInterrupt::ApplyPatchApproval(id, ev) => {
|
|
|
|
|
self.handle_apply_patch_approval_now(id, ev)
|
|
|
|
|
}
|
|
|
|
|
QueuedInterrupt::ExecBegin(ev) => self.handle_exec_begin_now(ev),
|
|
|
|
|
QueuedInterrupt::McpBegin(ev) => self.handle_mcp_begin_now(ev),
|
|
|
|
|
QueuedInterrupt::McpEnd(ev) => self.handle_mcp_end_now(ev),
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
fn handle_exec_approval_now(&mut self, id: String, ev: ExecApprovalRequestEvent) {
|
|
|
|
|
// Log a background summary immediately so the history is chronological.
|
|
|
|
|
let cmdline = strip_bash_lc_and_escape(&ev.command);
|
|
|
|
|
let text = format!(
|
|
|
|
|
"command requires approval:\n$ {cmdline}{reason}",
|
|
|
|
|
reason = ev
|
|
|
|
|
.reason
|
|
|
|
|
.as_ref()
|
|
|
|
|
.map(|r| format!("\n{r}"))
|
|
|
|
|
.unwrap_or_default()
|
|
|
|
|
);
|
|
|
|
|
self.add_to_history(HistoryCell::new_background_event(text));
|
|
|
|
|
|
|
|
|
|
let request = ApprovalRequest::Exec {
|
|
|
|
|
id,
|
|
|
|
|
command: ev.command,
|
|
|
|
|
cwd: ev.cwd,
|
|
|
|
|
reason: ev.reason,
|
|
|
|
|
};
|
|
|
|
|
self.bottom_pane.push_approval_request(request);
|
|
|
|
|
self.request_redraw();
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
fn handle_apply_patch_approval_now(&mut self, id: String, ev: ApplyPatchApprovalRequestEvent) {
|
|
|
|
|
self.add_to_history(HistoryCell::new_patch_event(
|
|
|
|
|
PatchEventType::ApprovalRequest,
|
|
|
|
|
ev.changes.clone(),
|
|
|
|
|
));
|
|
|
|
|
|
|
|
|
|
let request = ApprovalRequest::ApplyPatch {
|
|
|
|
|
id,
|
|
|
|
|
reason: ev.reason,
|
|
|
|
|
grant_root: ev.grant_root,
|
|
|
|
|
};
|
|
|
|
|
self.bottom_pane.push_approval_request(request);
|
|
|
|
|
self.request_redraw();
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
fn handle_exec_begin_now(&mut self, ev: ExecCommandBeginEvent) {
|
|
|
|
|
// Ensure the status indicator is visible while the command runs.
|
|
|
|
|
self.bottom_pane
|
|
|
|
|
.update_status_text("running command".to_string());
|
|
|
|
|
self.running_commands.insert(
|
|
|
|
|
ev.call_id.clone(),
|
|
|
|
|
RunningCommand {
|
|
|
|
|
command: ev.command.clone(),
|
|
|
|
|
cwd: ev.cwd.clone(),
|
|
|
|
|
},
|
|
|
|
|
);
|
|
|
|
|
self.active_history_cell = Some(HistoryCell::new_active_exec_command(ev.command));
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
fn handle_mcp_begin_now(&mut self, ev: McpToolCallBeginEvent) {
|
|
|
|
|
self.add_to_history(HistoryCell::new_active_mcp_tool_call(ev.invocation));
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
fn handle_mcp_end_now(&mut self, ev: McpToolCallEndEvent) {
|
|
|
|
|
self.add_to_history(HistoryCell::new_completed_mcp_tool_call(
|
|
|
|
|
80,
|
|
|
|
|
ev.invocation,
|
|
|
|
|
ev.duration,
|
|
|
|
|
ev.result
|
|
|
|
|
.as_ref()
|
|
|
|
|
.map(|r| r.is_error.unwrap_or(false))
|
|
|
|
|
.unwrap_or(false),
|
|
|
|
|
ev.result,
|
|
|
|
|
));
|
|
|
|
|
}
|
2025-08-06 14:56:34 -07:00
|
|
|
fn interrupt_running_task(&mut self) {
|
|
|
|
|
if self.bottom_pane.is_task_running() {
|
|
|
|
|
self.active_history_cell = None;
|
|
|
|
|
self.bottom_pane.clear_ctrl_c_quit_hint();
|
|
|
|
|
self.submit_op(Op::Interrupt);
|
|
|
|
|
self.bottom_pane.set_task_running(false);
|
2025-08-07 18:26:47 -07:00
|
|
|
self.reasoning_collector.clear();
|
|
|
|
|
self.answer_collector.clear();
|
|
|
|
|
self.reasoning_streamer.clear();
|
|
|
|
|
self.answer_streamer.clear();
|
2025-08-06 14:56:34 -07:00
|
|
|
self.current_stream = None;
|
2025-08-07 18:26:47 -07:00
|
|
|
self.answer_header_emitted = false;
|
|
|
|
|
self.reasoning_header_emitted = false;
|
2025-08-06 14:56:34 -07:00
|
|
|
self.request_redraw();
|
|
|
|
|
}
|
|
|
|
|
}
|
2025-08-06 12:03:45 -07:00
|
|
|
fn layout_areas(&self, area: Rect) -> [Rect; 2] {
|
|
|
|
|
Layout::vertical([
|
|
|
|
|
Constraint::Max(
|
|
|
|
|
self.active_history_cell
|
|
|
|
|
.as_ref()
|
|
|
|
|
.map_or(0, |c| c.desired_height(area.width)),
|
|
|
|
|
),
|
|
|
|
|
Constraint::Min(self.bottom_pane.desired_height(area.width)),
|
|
|
|
|
])
|
|
|
|
|
.areas(area)
|
|
|
|
|
}
|
2025-08-07 18:26:47 -07:00
|
|
|
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
pub(crate) fn new(
|
2025-04-27 21:47:50 -07:00
|
|
|
config: Config,
|
2025-05-15 14:50:30 -07:00
|
|
|
app_event_tx: AppEventSender,
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
initial_prompt: Option<String>,
|
2025-05-04 11:12:40 -07:00
|
|
|
initial_images: Vec<PathBuf>,
|
2025-07-31 17:30:44 -07:00
|
|
|
enhanced_keys_supported: bool,
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
) -> Self {
|
|
|
|
|
let (codex_op_tx, mut codex_op_rx) = unbounded_channel::<Op>();
|
|
|
|
|
|
|
|
|
|
let app_event_tx_clone = app_event_tx.clone();
|
|
|
|
|
// Create the Codex asynchronously so the UI loads as quickly as possible.
|
2025-04-27 21:47:50 -07:00
|
|
|
let config_for_agent_loop = config.clone();
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
tokio::spawn(async move {
|
2025-07-27 20:01:35 -07:00
|
|
|
let CodexConversation {
|
|
|
|
|
codex,
|
|
|
|
|
session_configured,
|
|
|
|
|
..
|
|
|
|
|
} = match init_codex(config_for_agent_loop).await {
|
|
|
|
|
Ok(vals) => vals,
|
|
|
|
|
Err(e) => {
|
|
|
|
|
// TODO: surface this error to the user.
|
|
|
|
|
tracing::error!("failed to initialize codex: {e}");
|
|
|
|
|
return;
|
|
|
|
|
}
|
|
|
|
|
};
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
|
|
|
|
|
// Forward the captured `SessionInitialized` event that was consumed
|
|
|
|
|
// inside `init_codex()` so it can be rendered in the UI.
|
2025-07-27 20:01:35 -07:00
|
|
|
app_event_tx_clone.send(AppEvent::CodexEvent(session_configured.clone()));
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
let codex = Arc::new(codex);
|
|
|
|
|
let codex_clone = codex.clone();
|
|
|
|
|
tokio::spawn(async move {
|
|
|
|
|
while let Some(op) = codex_op_rx.recv().await {
|
|
|
|
|
let id = codex_clone.submit(op).await;
|
|
|
|
|
if let Err(e) = id {
|
|
|
|
|
tracing::error!("failed to submit op: {e}");
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
});
|
|
|
|
|
|
|
|
|
|
while let Ok(event) = codex.next_event().await {
|
2025-05-15 14:50:30 -07:00
|
|
|
app_event_tx_clone.send(AppEvent::CodexEvent(event));
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
}
|
|
|
|
|
});
|
|
|
|
|
|
2025-05-17 09:00:23 -07:00
|
|
|
Self {
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
app_event_tx: app_event_tx.clone(),
|
|
|
|
|
codex_op_tx,
|
|
|
|
|
bottom_pane: BottomPane::new(BottomPaneParams {
|
|
|
|
|
app_event_tx,
|
|
|
|
|
has_input_focus: true,
|
2025-07-31 17:30:44 -07:00
|
|
|
enhanced_keys_supported,
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
}),
|
2025-08-06 12:03:45 -07:00
|
|
|
active_history_cell: None,
|
2025-04-27 21:47:50 -07:00
|
|
|
config,
|
2025-05-17 09:00:23 -07:00
|
|
|
initial_user_message: create_initial_user_message(
|
|
|
|
|
initial_prompt.unwrap_or_default(),
|
|
|
|
|
initial_images,
|
|
|
|
|
),
|
2025-08-07 05:17:18 -07:00
|
|
|
total_token_usage: TokenUsage::default(),
|
|
|
|
|
last_token_usage: TokenUsage::default(),
|
2025-08-07 18:26:47 -07:00
|
|
|
reasoning_collector: MarkdownNewlineCollector::new(),
|
|
|
|
|
answer_collector: MarkdownNewlineCollector::new(),
|
|
|
|
|
reasoning_streamer: RenderedLineStreamer::new(),
|
|
|
|
|
answer_streamer: RenderedLineStreamer::new(),
|
2025-07-31 00:43:21 -07:00
|
|
|
running_commands: HashMap::new(),
|
2025-08-04 21:23:22 -07:00
|
|
|
current_stream: None,
|
2025-08-07 18:26:47 -07:00
|
|
|
answer_header_emitted: false,
|
|
|
|
|
reasoning_header_emitted: false,
|
2025-08-04 21:23:22 -07:00
|
|
|
live_max_rows: 3,
|
2025-08-07 18:26:47 -07:00
|
|
|
task_complete_pending: false,
|
|
|
|
|
finishing_after_drain: false,
|
|
|
|
|
interrupt_queue: VecDeque::new(),
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2025-07-31 00:43:21 -07:00
|
|
|
pub fn desired_height(&self, width: u16) -> u16 {
|
|
|
|
|
self.bottom_pane.desired_height(width)
|
2025-08-06 12:03:45 -07:00
|
|
|
+ self
|
|
|
|
|
.active_history_cell
|
|
|
|
|
.as_ref()
|
|
|
|
|
.map_or(0, |c| c.desired_height(width))
|
2025-07-30 17:06:55 -07:00
|
|
|
}
|
|
|
|
|
|
2025-05-15 14:50:30 -07:00
|
|
|
pub(crate) fn handle_key_event(&mut self, key_event: KeyEvent) {
|
2025-07-31 17:10:52 -07:00
|
|
|
if key_event.kind == KeyEventKind::Press {
|
|
|
|
|
self.bottom_pane.clear_ctrl_c_quit_hint();
|
|
|
|
|
}
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
|
2025-07-27 11:04:09 -07:00
|
|
|
match self.bottom_pane.handle_key_event(key_event) {
|
|
|
|
|
InputResult::Submitted(text) => {
|
|
|
|
|
self.submit_user_message(text.into());
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
}
|
2025-07-27 11:04:09 -07:00
|
|
|
InputResult::None => {}
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2025-07-12 15:32:00 -07:00
|
|
|
pub(crate) fn handle_paste(&mut self, text: String) {
|
2025-07-27 11:04:09 -07:00
|
|
|
self.bottom_pane.handle_paste(text);
|
2025-07-12 15:32:00 -07:00
|
|
|
}
|
|
|
|
|
|
2025-07-30 10:05:40 -07:00
|
|
|
fn add_to_history(&mut self, cell: HistoryCell) {
|
|
|
|
|
self.app_event_tx
|
|
|
|
|
.send(AppEvent::InsertHistory(cell.plain_lines()));
|
2025-07-25 01:56:40 -07:00
|
|
|
}
|
|
|
|
|
|
2025-05-17 09:00:23 -07:00
|
|
|
fn submit_user_message(&mut self, user_message: UserMessage) {
|
|
|
|
|
let UserMessage { text, image_paths } = user_message;
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
let mut items: Vec<InputItem> = Vec::new();
|
|
|
|
|
|
|
|
|
|
if !text.is_empty() {
|
|
|
|
|
items.push(InputItem::Text { text: text.clone() });
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
for path in image_paths {
|
|
|
|
|
items.push(InputItem::LocalImage { path });
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
if items.is_empty() {
|
2025-05-15 14:50:30 -07:00
|
|
|
return;
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
self.codex_op_tx
|
|
|
|
|
.send(Op::UserInput { items })
|
|
|
|
|
.unwrap_or_else(|e| {
|
|
|
|
|
tracing::error!("failed to send message: {e}");
|
|
|
|
|
});
|
|
|
|
|
|
feat: record messages from user in ~/.codex/history.jsonl (#939)
This is a large change to support a "history" feature like you would
expect in a shell like Bash.
History events are recorded in `$CODEX_HOME/history.jsonl`. Because it
is a JSONL file, it is straightforward to append new entries (as opposed
to the TypeScript file that uses `$CODEX_HOME/history.json`, so to be
valid JSON, each new entry entails rewriting the entire file). Because
it is possible for there to be multiple instances of Codex CLI writing
to `history.jsonl` at once, we use advisory file locking when working
with `history.jsonl` in `codex-rs/core/src/message_history.rs`.
Because we believe history is a sufficiently useful feature, we enable
it by default. Though to provide some safety, we set the file
permissions of `history.jsonl` to be `o600` so that other users on the
system cannot read the user's history. We do not yet support a default
list of `SENSITIVE_PATTERNS` as the TypeScript CLI does:
https://github.com/openai/codex/blob/3fdf9df1335ac9501e3fb0e61715359145711e8b/codex-cli/src/utils/storage/command-history.ts#L10-L17
We are going to take a more conservative approach to this list in the
Rust CLI. For example, while `/\b[A-Za-z0-9-_]{20,}\b/` might exclude
sensitive information like API tokens, it would also exclude valuable
information such as references to Git commits.
As noted in the updated documentation, users can opt-out of history by
adding the following to `config.toml`:
```toml
[history]
persistence = "none"
```
Because `history.jsonl` could, in theory, be quite large, we take a[n
arguably overly pedantic] approach in reading history entries into
memory. Specifically, we start by telling the client the current number
of entries in the history file (`history_entry_count`) as well as the
inode (`history_log_id`) of `history.jsonl` (see the new fields on
`SessionConfiguredEvent`).
The client is responsible for keeping new entries in memory to create a
"local history," but if the user hits up enough times to go "past" the
end of local history, then the client should use the new
`GetHistoryEntryRequest` in the protocol to fetch older entries.
Specifically, it should pass the `history_log_id` it was given
originally and work backwards from `history_entry_count`. (It should
really fetch history in batches rather than one-at-a-time, but that is
something we can improve upon in subsequent PRs.)
The motivation behind this crazy scheme is that it is designed to defend
against:
* The `history.jsonl` being truncated during the session such that the
index into the history is no longer consistent with what had been read
up to that point. We do not yet have logic to enforce a `max_bytes` for
`history.jsonl`, but once we do, we will aspire to implement it in a way
that should result in a new inode for the file on most systems.
* New items from concurrent Codex CLI sessions amending to the history.
Because, in absence of truncation, `history.jsonl` is an append-only
log, so long as the client reads backwards from `history_entry_count`,
it should always get a consistent view of history. (That said, it will
not be able to read _new_ commands from concurrent sessions, but perhaps
we will introduce a `/` command to reload latest history or something
down the road.)
Admittedly, my testing of this feature thus far has been fairly light. I
expect we will find bugs and introduce enhancements/fixes going forward.
2025-05-15 16:26:23 -07:00
|
|
|
// Persist the text to cross-session message history.
|
|
|
|
|
if !text.is_empty() {
|
|
|
|
|
self.codex_op_tx
|
|
|
|
|
.send(Op::AddToHistory { text: text.clone() })
|
|
|
|
|
.unwrap_or_else(|e| {
|
|
|
|
|
tracing::error!("failed to send AddHistory op: {e}");
|
|
|
|
|
});
|
|
|
|
|
}
|
|
|
|
|
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
// Only show text portion in conversation history for now.
|
|
|
|
|
if !text.is_empty() {
|
2025-07-30 10:05:40 -07:00
|
|
|
self.add_to_history(HistoryCell::new_user_prompt(text.clone()));
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2025-05-15 14:50:30 -07:00
|
|
|
pub(crate) fn handle_codex_event(&mut self, event: Event) {
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
let Event { id, msg } = event;
|
|
|
|
|
match msg {
|
2025-05-13 19:22:16 -07:00
|
|
|
EventMsg::SessionConfigured(event) => {
|
feat: record messages from user in ~/.codex/history.jsonl (#939)
This is a large change to support a "history" feature like you would
expect in a shell like Bash.
History events are recorded in `$CODEX_HOME/history.jsonl`. Because it
is a JSONL file, it is straightforward to append new entries (as opposed
to the TypeScript file that uses `$CODEX_HOME/history.json`, so to be
valid JSON, each new entry entails rewriting the entire file). Because
it is possible for there to be multiple instances of Codex CLI writing
to `history.jsonl` at once, we use advisory file locking when working
with `history.jsonl` in `codex-rs/core/src/message_history.rs`.
Because we believe history is a sufficiently useful feature, we enable
it by default. Though to provide some safety, we set the file
permissions of `history.jsonl` to be `o600` so that other users on the
system cannot read the user's history. We do not yet support a default
list of `SENSITIVE_PATTERNS` as the TypeScript CLI does:
https://github.com/openai/codex/blob/3fdf9df1335ac9501e3fb0e61715359145711e8b/codex-cli/src/utils/storage/command-history.ts#L10-L17
We are going to take a more conservative approach to this list in the
Rust CLI. For example, while `/\b[A-Za-z0-9-_]{20,}\b/` might exclude
sensitive information like API tokens, it would also exclude valuable
information such as references to Git commits.
As noted in the updated documentation, users can opt-out of history by
adding the following to `config.toml`:
```toml
[history]
persistence = "none"
```
Because `history.jsonl` could, in theory, be quite large, we take a[n
arguably overly pedantic] approach in reading history entries into
memory. Specifically, we start by telling the client the current number
of entries in the history file (`history_entry_count`) as well as the
inode (`history_log_id`) of `history.jsonl` (see the new fields on
`SessionConfiguredEvent`).
The client is responsible for keeping new entries in memory to create a
"local history," but if the user hits up enough times to go "past" the
end of local history, then the client should use the new
`GetHistoryEntryRequest` in the protocol to fetch older entries.
Specifically, it should pass the `history_log_id` it was given
originally and work backwards from `history_entry_count`. (It should
really fetch history in batches rather than one-at-a-time, but that is
something we can improve upon in subsequent PRs.)
The motivation behind this crazy scheme is that it is designed to defend
against:
* The `history.jsonl` being truncated during the session such that the
index into the history is no longer consistent with what had been read
up to that point. We do not yet have logic to enforce a `max_bytes` for
`history.jsonl`, but once we do, we will aspire to implement it in a way
that should result in a new inode for the file on most systems.
* New items from concurrent Codex CLI sessions amending to the history.
Because, in absence of truncation, `history.jsonl` is an append-only
log, so long as the client reads backwards from `history_entry_count`,
it should always get a consistent view of history. (That said, it will
not be able to read _new_ commands from concurrent sessions, but perhaps
we will introduce a `/` command to reload latest history or something
down the road.)
Admittedly, my testing of this feature thus far has been fairly light. I
expect we will find bugs and introduce enhancements/fixes going forward.
2025-05-15 16:26:23 -07:00
|
|
|
self.bottom_pane
|
|
|
|
|
.set_history_metadata(event.history_log_id, event.history_entry_count);
|
2025-07-30 10:05:40 -07:00
|
|
|
// Record session information at the top of the conversation.
|
|
|
|
|
self.add_to_history(HistoryCell::new_session_info(&self.config, event, true));
|
2025-05-17 09:00:23 -07:00
|
|
|
|
|
|
|
|
if let Some(user_message) = self.initial_user_message.take() {
|
|
|
|
|
// If the user provided an initial message, add it to the
|
|
|
|
|
// conversation history.
|
|
|
|
|
self.submit_user_message(user_message);
|
|
|
|
|
}
|
|
|
|
|
|
2025-05-15 14:50:30 -07:00
|
|
|
self.request_redraw();
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
}
|
2025-08-04 21:23:22 -07:00
|
|
|
EventMsg::AgentMessage(AgentMessageEvent { message: _ }) => {
|
|
|
|
|
// Final assistant answer: commit all remaining rows and close with
|
|
|
|
|
// a blank line. Use the final text if provided, otherwise rely on
|
|
|
|
|
// streamed deltas already in the builder.
|
|
|
|
|
self.finalize_stream(StreamKind::Answer);
|
2025-07-16 22:26:31 -07:00
|
|
|
self.request_redraw();
|
|
|
|
|
}
|
|
|
|
|
EventMsg::AgentMessageDelta(AgentMessageDeltaEvent { delta }) => {
|
2025-08-04 21:23:22 -07:00
|
|
|
self.begin_stream(StreamKind::Answer);
|
|
|
|
|
self.stream_push_and_maybe_commit(&delta);
|
|
|
|
|
self.request_redraw();
|
2025-07-16 22:26:31 -07:00
|
|
|
}
|
|
|
|
|
EventMsg::AgentReasoningDelta(AgentReasoningDeltaEvent { delta }) => {
|
2025-08-04 21:23:22 -07:00
|
|
|
// Stream CoT into the live pane; keep input visible and commit
|
|
|
|
|
// overflow rows incrementally to scrollback.
|
|
|
|
|
self.begin_stream(StreamKind::Reasoning);
|
|
|
|
|
self.stream_push_and_maybe_commit(&delta);
|
|
|
|
|
self.request_redraw();
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
}
|
2025-08-04 21:23:22 -07:00
|
|
|
EventMsg::AgentReasoning(AgentReasoningEvent { text: _ }) => {
|
|
|
|
|
// Final reasoning: commit remaining rows and close with a blank.
|
|
|
|
|
self.finalize_stream(StreamKind::Reasoning);
|
2025-07-16 22:26:31 -07:00
|
|
|
self.request_redraw();
|
2025-05-10 21:43:27 -07:00
|
|
|
}
|
2025-08-05 01:56:13 -07:00
|
|
|
EventMsg::AgentReasoningRawContentDelta(AgentReasoningRawContentDeltaEvent {
|
|
|
|
|
delta,
|
|
|
|
|
}) => {
|
|
|
|
|
// Treat raw reasoning content the same as summarized reasoning for UI flow.
|
|
|
|
|
self.begin_stream(StreamKind::Reasoning);
|
|
|
|
|
self.stream_push_and_maybe_commit(&delta);
|
|
|
|
|
self.request_redraw();
|
|
|
|
|
}
|
|
|
|
|
EventMsg::AgentReasoningRawContent(AgentReasoningRawContentEvent { text: _ }) => {
|
|
|
|
|
// Finalize the raw reasoning stream just like the summarized reasoning event.
|
|
|
|
|
self.finalize_stream(StreamKind::Reasoning);
|
|
|
|
|
self.request_redraw();
|
|
|
|
|
}
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
EventMsg::TaskStarted => {
|
2025-06-27 13:37:11 -04:00
|
|
|
self.bottom_pane.clear_ctrl_c_quit_hint();
|
2025-05-15 14:50:30 -07:00
|
|
|
self.bottom_pane.set_task_running(true);
|
2025-08-04 21:23:22 -07:00
|
|
|
// Replace composer with single-line spinner while waiting.
|
|
|
|
|
self.bottom_pane
|
|
|
|
|
.update_status_text("waiting for model".to_string());
|
2025-05-15 14:50:30 -07:00
|
|
|
self.request_redraw();
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
}
|
2025-05-19 16:08:18 -07:00
|
|
|
EventMsg::TaskComplete(TaskCompleteEvent {
|
|
|
|
|
last_agent_message: _,
|
|
|
|
|
}) => {
|
2025-08-07 18:26:47 -07:00
|
|
|
// Defer clearing status/live ring until streaming fully completes.
|
|
|
|
|
let streaming_active = match self.current_stream {
|
|
|
|
|
Some(StreamKind::Reasoning) => !self.reasoning_streamer.is_idle(),
|
|
|
|
|
Some(StreamKind::Answer) => !self.answer_streamer.is_idle(),
|
|
|
|
|
None => false,
|
|
|
|
|
};
|
|
|
|
|
if streaming_active {
|
|
|
|
|
self.task_complete_pending = true;
|
|
|
|
|
} else {
|
|
|
|
|
self.bottom_pane.set_task_running(false);
|
|
|
|
|
self.request_redraw();
|
|
|
|
|
}
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
}
|
feat: show number of tokens remaining in UI (#1388)
When using the OpenAI Responses API, we now record the `usage` field for
a `"response.completed"` event, which includes metrics about the number
of tokens consumed. We also introduce `openai_model_info.rs`, which
includes current data about the most common OpenAI models available via
the API (specifically `context_window` and `max_output_tokens`). If
Codex does not recognize the model, you can set `model_context_window`
and `model_max_output_tokens` explicitly in `config.toml`.
When then introduce a new event type to `protocol.rs`, `TokenCount`,
which includes the `TokenUsage` for the most recent turn.
Finally, we update the TUI to record the running sum of tokens used so
the percentage of available context window remaining can be reported via
the placeholder text for the composer:

We could certainly get much fancier with this (such as reporting the
estimated cost of the conversation), but for now, we are just trying to
achieve feature parity with the TypeScript CLI.
Though arguably this improves upon the TypeScript CLI, as the TypeScript
CLI uses heuristics to estimate the number of tokens used rather than
using the `usage` information directly:
https://github.com/openai/codex/blob/296996d74e345b1b05d8c3451a06ace21c5ada96/codex-cli/src/utils/approximate-tokens-used.ts#L3-L16
Fixes https://github.com/openai/codex/issues/1242
2025-06-25 23:31:11 -07:00
|
|
|
EventMsg::TokenCount(token_usage) => {
|
2025-08-07 05:17:18 -07:00
|
|
|
self.total_token_usage = add_token_usage(&self.total_token_usage, &token_usage);
|
|
|
|
|
self.last_token_usage = token_usage;
|
|
|
|
|
self.bottom_pane.set_token_usage(
|
|
|
|
|
self.total_token_usage.clone(),
|
|
|
|
|
self.last_token_usage.clone(),
|
|
|
|
|
self.config.model_context_window,
|
|
|
|
|
);
|
feat: show number of tokens remaining in UI (#1388)
When using the OpenAI Responses API, we now record the `usage` field for
a `"response.completed"` event, which includes metrics about the number
of tokens consumed. We also introduce `openai_model_info.rs`, which
includes current data about the most common OpenAI models available via
the API (specifically `context_window` and `max_output_tokens`). If
Codex does not recognize the model, you can set `model_context_window`
and `model_max_output_tokens` explicitly in `config.toml`.
When then introduce a new event type to `protocol.rs`, `TokenCount`,
which includes the `TokenUsage` for the most recent turn.
Finally, we update the TUI to record the running sum of tokens used so
the percentage of available context window remaining can be reported via
the placeholder text for the composer:

We could certainly get much fancier with this (such as reporting the
estimated cost of the conversation), but for now, we are just trying to
achieve feature parity with the TypeScript CLI.
Though arguably this improves upon the TypeScript CLI, as the TypeScript
CLI uses heuristics to estimate the number of tokens used rather than
using the `usage` information directly:
https://github.com/openai/codex/blob/296996d74e345b1b05d8c3451a06ace21c5ada96/codex-cli/src/utils/approximate-tokens-used.ts#L3-L16
Fixes https://github.com/openai/codex/issues/1242
2025-06-25 23:31:11 -07:00
|
|
|
}
|
2025-05-13 20:44:42 -07:00
|
|
|
EventMsg::Error(ErrorEvent { message }) => {
|
2025-07-30 10:05:40 -07:00
|
|
|
self.add_to_history(HistoryCell::new_error_event(message.clone()));
|
2025-05-15 14:50:30 -07:00
|
|
|
self.bottom_pane.set_task_running(false);
|
2025-08-07 18:26:47 -07:00
|
|
|
self.reasoning_collector.clear();
|
|
|
|
|
self.answer_collector.clear();
|
|
|
|
|
self.reasoning_streamer.clear();
|
|
|
|
|
self.answer_streamer.clear();
|
2025-08-05 01:56:13 -07:00
|
|
|
self.current_stream = None;
|
2025-08-07 18:26:47 -07:00
|
|
|
self.answer_header_emitted = false;
|
|
|
|
|
self.reasoning_header_emitted = false;
|
2025-08-05 01:56:13 -07:00
|
|
|
self.request_redraw();
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
}
|
2025-07-31 13:45:52 -07:00
|
|
|
EventMsg::PlanUpdate(update) => {
|
2025-08-04 21:23:22 -07:00
|
|
|
// Commit plan updates directly to history (no status-line preview).
|
2025-07-31 13:45:52 -07:00
|
|
|
self.add_to_history(HistoryCell::new_plan_update(update));
|
|
|
|
|
}
|
2025-08-07 18:26:47 -07:00
|
|
|
EventMsg::ExecApprovalRequest(ev) => {
|
|
|
|
|
if self.is_write_cycle_active() {
|
|
|
|
|
self.interrupt_queue
|
|
|
|
|
.push_back(QueuedInterrupt::ExecApproval(id, ev));
|
|
|
|
|
} else {
|
|
|
|
|
self.handle_exec_approval_now(id, ev);
|
|
|
|
|
}
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
}
|
2025-08-07 18:26:47 -07:00
|
|
|
EventMsg::ApplyPatchApprovalRequest(ev) => {
|
|
|
|
|
if self.is_write_cycle_active() {
|
|
|
|
|
self.interrupt_queue
|
|
|
|
|
.push_back(QueuedInterrupt::ApplyPatchApproval(id, ev));
|
|
|
|
|
} else {
|
|
|
|
|
self.handle_apply_patch_approval_now(id, ev);
|
|
|
|
|
}
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
}
|
2025-08-07 18:26:47 -07:00
|
|
|
EventMsg::ExecCommandBegin(ev) => {
|
|
|
|
|
if self.is_write_cycle_active() {
|
|
|
|
|
self.interrupt_queue
|
|
|
|
|
.push_back(QueuedInterrupt::ExecBegin(ev));
|
|
|
|
|
} else {
|
|
|
|
|
self.handle_exec_begin_now(ev);
|
|
|
|
|
}
|
2025-08-06 12:03:45 -07:00
|
|
|
}
|
|
|
|
|
EventMsg::ExecCommandOutputDelta(_) => {
|
|
|
|
|
// TODO
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
}
|
2025-05-13 20:44:42 -07:00
|
|
|
EventMsg::PatchApplyBegin(PatchApplyBeginEvent {
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
call_id: _,
|
|
|
|
|
auto_approved,
|
|
|
|
|
changes,
|
2025-05-13 20:44:42 -07:00
|
|
|
}) => {
|
2025-07-30 10:05:40 -07:00
|
|
|
self.add_to_history(HistoryCell::new_patch_event(
|
|
|
|
|
PatchEventType::ApplyBegin { auto_approved },
|
|
|
|
|
changes,
|
|
|
|
|
));
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
}
|
2025-08-06 12:03:45 -07:00
|
|
|
EventMsg::PatchApplyEnd(event) => {
|
2025-08-06 22:25:41 -07:00
|
|
|
if !event.success {
|
|
|
|
|
self.add_to_history(HistoryCell::new_patch_apply_failure(event.stderr));
|
|
|
|
|
}
|
2025-08-05 22:44:27 -07:00
|
|
|
}
|
2025-05-13 20:44:42 -07:00
|
|
|
EventMsg::ExecCommandEnd(ExecCommandEndEvent {
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
call_id,
|
|
|
|
|
exit_code,
|
2025-08-06 17:10:59 -07:00
|
|
|
duration: _,
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
stdout,
|
|
|
|
|
stderr,
|
2025-05-13 20:44:42 -07:00
|
|
|
}) => {
|
2025-08-04 21:23:22 -07:00
|
|
|
// Compute summary before moving stdout into the history cell.
|
2025-07-31 00:43:21 -07:00
|
|
|
let cmd = self.running_commands.remove(&call_id);
|
2025-08-06 12:03:45 -07:00
|
|
|
self.active_history_cell = None;
|
2025-07-30 10:05:40 -07:00
|
|
|
self.add_to_history(HistoryCell::new_completed_exec_command(
|
2025-07-31 00:43:21 -07:00
|
|
|
cmd.map(|cmd| cmd.command).unwrap_or_else(|| vec![call_id]),
|
2025-07-30 10:05:40 -07:00
|
|
|
CommandOutput {
|
|
|
|
|
exit_code,
|
|
|
|
|
stdout,
|
|
|
|
|
stderr,
|
|
|
|
|
},
|
|
|
|
|
));
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
}
|
2025-08-07 18:26:47 -07:00
|
|
|
EventMsg::McpToolCallBegin(ev) => {
|
|
|
|
|
if self.is_write_cycle_active() {
|
|
|
|
|
self.interrupt_queue
|
|
|
|
|
.push_back(QueuedInterrupt::McpBegin(ev));
|
|
|
|
|
} else {
|
|
|
|
|
self.handle_mcp_begin_now(ev);
|
|
|
|
|
}
|
2025-05-06 16:12:15 -07:00
|
|
|
}
|
2025-08-07 18:26:47 -07:00
|
|
|
EventMsg::McpToolCallEnd(ev) => {
|
|
|
|
|
if self.is_write_cycle_active() {
|
|
|
|
|
self.interrupt_queue.push_back(QueuedInterrupt::McpEnd(ev));
|
|
|
|
|
} else {
|
|
|
|
|
self.handle_mcp_end_now(ev);
|
|
|
|
|
}
|
2025-05-06 16:12:15 -07:00
|
|
|
}
|
feat: record messages from user in ~/.codex/history.jsonl (#939)
This is a large change to support a "history" feature like you would
expect in a shell like Bash.
History events are recorded in `$CODEX_HOME/history.jsonl`. Because it
is a JSONL file, it is straightforward to append new entries (as opposed
to the TypeScript file that uses `$CODEX_HOME/history.json`, so to be
valid JSON, each new entry entails rewriting the entire file). Because
it is possible for there to be multiple instances of Codex CLI writing
to `history.jsonl` at once, we use advisory file locking when working
with `history.jsonl` in `codex-rs/core/src/message_history.rs`.
Because we believe history is a sufficiently useful feature, we enable
it by default. Though to provide some safety, we set the file
permissions of `history.jsonl` to be `o600` so that other users on the
system cannot read the user's history. We do not yet support a default
list of `SENSITIVE_PATTERNS` as the TypeScript CLI does:
https://github.com/openai/codex/blob/3fdf9df1335ac9501e3fb0e61715359145711e8b/codex-cli/src/utils/storage/command-history.ts#L10-L17
We are going to take a more conservative approach to this list in the
Rust CLI. For example, while `/\b[A-Za-z0-9-_]{20,}\b/` might exclude
sensitive information like API tokens, it would also exclude valuable
information such as references to Git commits.
As noted in the updated documentation, users can opt-out of history by
adding the following to `config.toml`:
```toml
[history]
persistence = "none"
```
Because `history.jsonl` could, in theory, be quite large, we take a[n
arguably overly pedantic] approach in reading history entries into
memory. Specifically, we start by telling the client the current number
of entries in the history file (`history_entry_count`) as well as the
inode (`history_log_id`) of `history.jsonl` (see the new fields on
`SessionConfiguredEvent`).
The client is responsible for keeping new entries in memory to create a
"local history," but if the user hits up enough times to go "past" the
end of local history, then the client should use the new
`GetHistoryEntryRequest` in the protocol to fetch older entries.
Specifically, it should pass the `history_log_id` it was given
originally and work backwards from `history_entry_count`. (It should
really fetch history in batches rather than one-at-a-time, but that is
something we can improve upon in subsequent PRs.)
The motivation behind this crazy scheme is that it is designed to defend
against:
* The `history.jsonl` being truncated during the session such that the
index into the history is no longer consistent with what had been read
up to that point. We do not yet have logic to enforce a `max_bytes` for
`history.jsonl`, but once we do, we will aspire to implement it in a way
that should result in a new inode for the file on most systems.
* New items from concurrent Codex CLI sessions amending to the history.
Because, in absence of truncation, `history.jsonl` is an append-only
log, so long as the client reads backwards from `history_entry_count`,
it should always get a consistent view of history. (That said, it will
not be able to read _new_ commands from concurrent sessions, but perhaps
we will introduce a `/` command to reload latest history or something
down the road.)
Admittedly, my testing of this feature thus far has been fairly light. I
expect we will find bugs and introduce enhancements/fixes going forward.
2025-05-15 16:26:23 -07:00
|
|
|
EventMsg::GetHistoryEntryResponse(event) => {
|
|
|
|
|
let codex_core::protocol::GetHistoryEntryResponseEvent {
|
|
|
|
|
offset,
|
|
|
|
|
log_id,
|
|
|
|
|
entry,
|
|
|
|
|
} = event;
|
|
|
|
|
|
|
|
|
|
// Inform bottom pane / composer.
|
|
|
|
|
self.bottom_pane
|
|
|
|
|
.on_history_entry_response(log_id, offset, entry.map(|e| e.text));
|
|
|
|
|
}
|
2025-07-23 15:03:26 -07:00
|
|
|
EventMsg::ShutdownComplete => {
|
|
|
|
|
self.app_event_tx.send(AppEvent::ExitRequest);
|
|
|
|
|
}
|
2025-08-05 22:44:27 -07:00
|
|
|
EventMsg::TurnDiff(TurnDiffEvent { unified_diff }) => {
|
|
|
|
|
info!("TurnDiffEvent: {unified_diff}");
|
|
|
|
|
}
|
|
|
|
|
EventMsg::BackgroundEvent(BackgroundEventEvent { message }) => {
|
|
|
|
|
info!("BackgroundEvent: {message}");
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/// Update the live log preview while a task is running.
|
2025-05-15 14:50:30 -07:00
|
|
|
pub(crate) fn update_latest_log(&mut self, line: String) {
|
2025-08-05 01:56:13 -07:00
|
|
|
if self.bottom_pane.is_task_running() {
|
|
|
|
|
self.bottom_pane.update_status_text(line);
|
|
|
|
|
}
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
}
|
|
|
|
|
|
2025-05-15 14:50:30 -07:00
|
|
|
fn request_redraw(&mut self) {
|
2025-07-17 12:54:55 -07:00
|
|
|
self.app_event_tx.send(AppEvent::RequestRedraw);
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
}
|
|
|
|
|
|
2025-06-26 13:03:31 -07:00
|
|
|
pub(crate) fn add_diff_output(&mut self, diff_output: String) {
|
2025-07-30 10:05:40 -07:00
|
|
|
self.add_to_history(HistoryCell::new_diff_output(diff_output.clone()));
|
2025-04-25 12:01:52 -07:00
|
|
|
}
|
|
|
|
|
|
2025-08-05 23:57:52 -07:00
|
|
|
pub(crate) fn add_status_output(&mut self) {
|
|
|
|
|
self.add_to_history(HistoryCell::new_status_output(
|
|
|
|
|
&self.config,
|
2025-08-07 05:17:18 -07:00
|
|
|
&self.total_token_usage,
|
2025-08-05 23:57:52 -07:00
|
|
|
));
|
|
|
|
|
}
|
|
|
|
|
|
2025-08-07 03:55:59 -07:00
|
|
|
pub(crate) fn add_prompts_output(&mut self) {
|
|
|
|
|
self.add_to_history(HistoryCell::new_prompts_output());
|
|
|
|
|
}
|
|
|
|
|
|
feat: add support for @ to do file search (#1401)
Introduces support for `@` to trigger a fuzzy-filename search in the
composer. Under the hood, this leverages
https://crates.io/crates/nucleo-matcher to do the fuzzy matching and
https://crates.io/crates/ignore to build up the list of file candidates
(so that it respects `.gitignore`).
For simplicity (at least for now), we do not do any caching between
searches like VS Code does for its file search:
https://github.com/microsoft/vscode/blob/1d89ed699b2e924d418c856318a3e12bca67ff3a/src/vs/workbench/services/search/node/rawSearchService.ts#L212-L218
Because we do not do any caching, I saw queries take up to three seconds
on large repositories with hundreds of thousands of files. To that end,
we do not perform searches synchronously on each keystroke, but instead
dispatch an event to do the search on a background thread that
asynchronously reports back to the UI when the results are available.
This is largely handled by the `FileSearchManager` introduced in this
PR, which also has logic for debouncing requests so there is at most one
search in flight at a time.
While we could potentially polish and tune this feature further, it may
already be overengineered for how it will be used, in practice, so we
can improve things going forward if it turns out that this is not "good
enough" in the wild.
Note this feature does not work like `@` in the TypeScript CLI, which
was more like directory-based tab completion. In the Rust CLI, `@`
triggers a full-repo fuzzy-filename search.
Fixes https://github.com/openai/codex/issues/1261.
2025-06-28 13:47:42 -07:00
|
|
|
/// Forward file-search results to the bottom pane.
|
2025-06-28 15:04:23 -07:00
|
|
|
pub(crate) fn apply_file_search_result(&mut self, query: String, matches: Vec<FileMatch>) {
|
feat: add support for @ to do file search (#1401)
Introduces support for `@` to trigger a fuzzy-filename search in the
composer. Under the hood, this leverages
https://crates.io/crates/nucleo-matcher to do the fuzzy matching and
https://crates.io/crates/ignore to build up the list of file candidates
(so that it respects `.gitignore`).
For simplicity (at least for now), we do not do any caching between
searches like VS Code does for its file search:
https://github.com/microsoft/vscode/blob/1d89ed699b2e924d418c856318a3e12bca67ff3a/src/vs/workbench/services/search/node/rawSearchService.ts#L212-L218
Because we do not do any caching, I saw queries take up to three seconds
on large repositories with hundreds of thousands of files. To that end,
we do not perform searches synchronously on each keystroke, but instead
dispatch an event to do the search on a background thread that
asynchronously reports back to the UI when the results are available.
This is largely handled by the `FileSearchManager` introduced in this
PR, which also has logic for debouncing requests so there is at most one
search in flight at a time.
While we could potentially polish and tune this feature further, it may
already be overengineered for how it will be used, in practice, so we
can improve things going forward if it turns out that this is not "good
enough" in the wild.
Note this feature does not work like `@` in the TypeScript CLI, which
was more like directory-based tab completion. In the Rust CLI, `@`
triggers a full-repo fuzzy-filename search.
Fixes https://github.com/openai/codex/issues/1261.
2025-06-28 13:47:42 -07:00
|
|
|
self.bottom_pane.on_file_search_result(query, matches);
|
|
|
|
|
}
|
|
|
|
|
|
2025-06-27 13:37:11 -04:00
|
|
|
/// Handle Ctrl-C key press.
|
2025-07-28 12:00:06 -07:00
|
|
|
/// Returns CancellationEvent::Handled if the event was consumed by the UI, or
|
|
|
|
|
/// CancellationEvent::Ignored if the caller should handle it (e.g. exit).
|
|
|
|
|
pub(crate) fn on_ctrl_c(&mut self) -> CancellationEvent {
|
|
|
|
|
match self.bottom_pane.on_ctrl_c() {
|
|
|
|
|
CancellationEvent::Handled => return CancellationEvent::Handled,
|
|
|
|
|
CancellationEvent::Ignored => {}
|
|
|
|
|
}
|
2025-06-27 13:37:11 -04:00
|
|
|
if self.bottom_pane.is_task_running() {
|
2025-08-06 14:56:34 -07:00
|
|
|
self.interrupt_running_task();
|
2025-07-28 12:00:06 -07:00
|
|
|
CancellationEvent::Ignored
|
2025-06-27 13:37:11 -04:00
|
|
|
} else if self.bottom_pane.ctrl_c_quit_hint_visible() {
|
2025-07-23 15:03:26 -07:00
|
|
|
self.submit_op(Op::Shutdown);
|
2025-07-28 12:00:06 -07:00
|
|
|
CancellationEvent::Handled
|
2025-06-27 13:37:11 -04:00
|
|
|
} else {
|
|
|
|
|
self.bottom_pane.show_ctrl_c_quit_hint();
|
2025-07-28 12:00:06 -07:00
|
|
|
CancellationEvent::Ignored
|
2025-06-27 13:37:11 -04:00
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2025-08-06 14:56:34 -07:00
|
|
|
pub(crate) fn on_ctrl_z(&mut self) {
|
|
|
|
|
self.interrupt_running_task();
|
|
|
|
|
}
|
|
|
|
|
|
2025-07-16 08:59:26 -07:00
|
|
|
pub(crate) fn composer_is_empty(&self) -> bool {
|
|
|
|
|
self.bottom_pane.composer_is_empty()
|
|
|
|
|
}
|
|
|
|
|
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
/// Forward an `Op` directly to codex.
|
|
|
|
|
pub(crate) fn submit_op(&self, op: Op) {
|
|
|
|
|
if let Err(e) = self.codex_op_tx.send(op) {
|
|
|
|
|
tracing::error!("failed to submit op: {e}");
|
|
|
|
|
}
|
|
|
|
|
}
|
2025-07-25 01:56:40 -07:00
|
|
|
|
2025-08-06 09:10:23 -07:00
|
|
|
/// Programmatically submit a user text message as if typed in the
|
|
|
|
|
/// composer. The text will be added to conversation history and sent to
|
|
|
|
|
/// the agent.
|
|
|
|
|
pub(crate) fn submit_text_message(&mut self, text: String) {
|
|
|
|
|
if text.is_empty() {
|
|
|
|
|
return;
|
|
|
|
|
}
|
|
|
|
|
self.submit_user_message(text.into());
|
|
|
|
|
}
|
|
|
|
|
|
2025-07-25 01:56:40 -07:00
|
|
|
pub(crate) fn token_usage(&self) -> &TokenUsage {
|
2025-08-07 05:17:18 -07:00
|
|
|
&self.total_token_usage
|
2025-07-25 01:56:40 -07:00
|
|
|
}
|
2025-07-31 21:34:32 -07:00
|
|
|
|
|
|
|
|
pub(crate) fn clear_token_usage(&mut self) {
|
2025-08-07 05:17:18 -07:00
|
|
|
self.total_token_usage = TokenUsage::default();
|
|
|
|
|
self.bottom_pane.set_token_usage(
|
|
|
|
|
self.total_token_usage.clone(),
|
|
|
|
|
self.last_token_usage.clone(),
|
|
|
|
|
self.config.model_context_window,
|
|
|
|
|
);
|
2025-07-31 21:34:32 -07:00
|
|
|
}
|
2025-08-03 11:31:35 -07:00
|
|
|
|
|
|
|
|
pub fn cursor_pos(&self, area: Rect) -> Option<(u16, u16)> {
|
2025-08-06 12:03:45 -07:00
|
|
|
let [_, bottom_pane_area] = self.layout_areas(area);
|
|
|
|
|
self.bottom_pane.cursor_pos(bottom_pane_area)
|
2025-08-03 11:31:35 -07:00
|
|
|
}
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
}
|
|
|
|
|
|
2025-08-07 18:26:47 -07:00
|
|
|
#[cfg(test)]
|
|
|
|
|
impl ChatWidget<'_> {
|
|
|
|
|
/// Test-only control to tune the maximum rows shown in the live overlay.
|
|
|
|
|
/// Useful for verifying queue-head behavior without changing production defaults.
|
|
|
|
|
pub fn test_set_live_max_rows(&mut self, n: u16) {
|
|
|
|
|
self.live_max_rows = n;
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2025-08-04 21:23:22 -07:00
|
|
|
impl ChatWidget<'_> {
|
|
|
|
|
fn begin_stream(&mut self, kind: StreamKind) {
|
2025-08-05 01:56:13 -07:00
|
|
|
if let Some(current) = self.current_stream {
|
|
|
|
|
if current != kind {
|
2025-08-07 18:26:47 -07:00
|
|
|
// Synchronously flush the previous stream to keep ordering sane.
|
|
|
|
|
let (collector, streamer) = match current {
|
|
|
|
|
StreamKind::Reasoning => {
|
|
|
|
|
(&mut self.reasoning_collector, &mut self.reasoning_streamer)
|
|
|
|
|
}
|
|
|
|
|
StreamKind::Answer => (&mut self.answer_collector, &mut self.answer_streamer),
|
|
|
|
|
};
|
|
|
|
|
let remaining = collector.finalize_and_drain(&self.config);
|
|
|
|
|
if !remaining.is_empty() {
|
|
|
|
|
streamer.enqueue(remaining);
|
|
|
|
|
}
|
|
|
|
|
let step = streamer.drain_all(self.live_max_rows as usize);
|
|
|
|
|
let prev_header_emitted = match current {
|
|
|
|
|
StreamKind::Reasoning => self.reasoning_header_emitted,
|
|
|
|
|
StreamKind::Answer => self.answer_header_emitted,
|
|
|
|
|
};
|
|
|
|
|
if !step.history.is_empty() || !prev_header_emitted {
|
|
|
|
|
let mut lines: Vec<ratatui::text::Line<'static>> = Vec::new();
|
|
|
|
|
if !prev_header_emitted {
|
|
|
|
|
lines.push(Self::header_line(current));
|
|
|
|
|
match current {
|
|
|
|
|
StreamKind::Reasoning => self.reasoning_header_emitted = true,
|
|
|
|
|
StreamKind::Answer => self.answer_header_emitted = true,
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
lines.extend(step.history);
|
|
|
|
|
// Ensure at most one blank separator after the flushed block.
|
|
|
|
|
if let Some(last) = lines.last() {
|
|
|
|
|
if !Self::line_is_blank(last) {
|
|
|
|
|
lines.push(ratatui::text::Line::from(""));
|
|
|
|
|
}
|
|
|
|
|
} else {
|
|
|
|
|
lines.push(ratatui::text::Line::from(""));
|
|
|
|
|
}
|
|
|
|
|
self.app_event_tx.send(AppEvent::InsertHistory(lines));
|
|
|
|
|
}
|
|
|
|
|
// Reset for new stream
|
|
|
|
|
self.current_stream = None;
|
2025-08-05 01:56:13 -07:00
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2025-08-04 21:23:22 -07:00
|
|
|
if self.current_stream != Some(kind) {
|
2025-08-07 18:26:47 -07:00
|
|
|
// Only reset the header flag when switching FROM a different stream kind.
|
|
|
|
|
// If current_stream is None (e.g., transient idle), preserve header flags
|
|
|
|
|
// to avoid duplicate headers on re-entry into the same stream.
|
|
|
|
|
let prev = self.current_stream;
|
2025-08-04 21:23:22 -07:00
|
|
|
self.current_stream = Some(kind);
|
2025-08-07 18:26:47 -07:00
|
|
|
if prev.is_some() {
|
|
|
|
|
match kind {
|
|
|
|
|
StreamKind::Reasoning => self.reasoning_header_emitted = false,
|
|
|
|
|
StreamKind::Answer => self.answer_header_emitted = false,
|
|
|
|
|
}
|
|
|
|
|
}
|
2025-08-04 21:23:22 -07:00
|
|
|
// Ensure the waiting status is visible (composer replaced).
|
|
|
|
|
self.bottom_pane
|
|
|
|
|
.update_status_text("waiting for model".to_string());
|
2025-08-07 18:26:47 -07:00
|
|
|
// No live ring overlay; headers will be inserted with the first commit.
|
2025-08-04 21:23:22 -07:00
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
fn stream_push_and_maybe_commit(&mut self, delta: &str) {
|
2025-08-07 18:26:47 -07:00
|
|
|
// Newline-gated: only consider committing when a newline is present.
|
|
|
|
|
let (collector, streamer) = match self.current_stream {
|
|
|
|
|
Some(StreamKind::Reasoning) => {
|
|
|
|
|
(&mut self.reasoning_collector, &mut self.reasoning_streamer)
|
2025-08-04 21:23:22 -07:00
|
|
|
}
|
2025-08-07 18:26:47 -07:00
|
|
|
Some(StreamKind::Answer) => (&mut self.answer_collector, &mut self.answer_streamer),
|
|
|
|
|
None => return,
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
collector.push_delta(delta);
|
|
|
|
|
if delta.contains('\n') {
|
|
|
|
|
let newly_completed = collector.commit_complete_lines(&self.config);
|
|
|
|
|
if !newly_completed.is_empty() {
|
|
|
|
|
streamer.enqueue(newly_completed);
|
|
|
|
|
// Start or continue commit animation.
|
|
|
|
|
self.app_event_tx.send(AppEvent::StartCommitAnimation);
|
2025-08-04 21:23:22 -07:00
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
fn finalize_stream(&mut self, kind: StreamKind) {
|
|
|
|
|
if self.current_stream != Some(kind) {
|
|
|
|
|
// Nothing to do; either already finalized or not the active stream.
|
|
|
|
|
return;
|
|
|
|
|
}
|
2025-08-07 18:26:47 -07:00
|
|
|
let (collector, streamer) = match kind {
|
|
|
|
|
StreamKind::Reasoning => (&mut self.reasoning_collector, &mut self.reasoning_streamer),
|
|
|
|
|
StreamKind::Answer => (&mut self.answer_collector, &mut self.answer_streamer),
|
|
|
|
|
};
|
2025-08-04 21:23:22 -07:00
|
|
|
|
2025-08-07 18:26:47 -07:00
|
|
|
let remaining = collector.finalize_and_drain(&self.config);
|
|
|
|
|
if !remaining.is_empty() {
|
|
|
|
|
streamer.enqueue(remaining);
|
|
|
|
|
}
|
|
|
|
|
// Trailing blank spacer
|
|
|
|
|
streamer.enqueue(vec![ratatui::text::Line::from("")]);
|
|
|
|
|
// Mark that we should clear state after draining.
|
|
|
|
|
self.finishing_after_drain = true;
|
|
|
|
|
// Start animation to drain remaining lines. Final cleanup will occur when drained.
|
|
|
|
|
self.app_event_tx.send(AppEvent::StartCommitAnimation);
|
2025-08-04 21:23:22 -07:00
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
impl WidgetRef for &ChatWidget<'_> {
|
|
|
|
|
fn render_ref(&self, area: Rect, buf: &mut Buffer) {
|
2025-08-06 12:03:45 -07:00
|
|
|
let [active_cell_area, bottom_pane_area] = self.layout_areas(area);
|
|
|
|
|
(&self.bottom_pane).render(bottom_pane_area, buf);
|
|
|
|
|
if let Some(cell) = &self.active_history_cell {
|
|
|
|
|
cell.render_ref(active_cell_area, buf);
|
|
|
|
|
}
|
feat: initial import of Rust implementation of Codex CLI in codex-rs/ (#629)
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.
2025-04-24 13:31:40 -07:00
|
|
|
}
|
|
|
|
|
}
|
feat: show number of tokens remaining in UI (#1388)
When using the OpenAI Responses API, we now record the `usage` field for
a `"response.completed"` event, which includes metrics about the number
of tokens consumed. We also introduce `openai_model_info.rs`, which
includes current data about the most common OpenAI models available via
the API (specifically `context_window` and `max_output_tokens`). If
Codex does not recognize the model, you can set `model_context_window`
and `model_max_output_tokens` explicitly in `config.toml`.
When then introduce a new event type to `protocol.rs`, `TokenCount`,
which includes the `TokenUsage` for the most recent turn.
Finally, we update the TUI to record the running sum of tokens used so
the percentage of available context window remaining can be reported via
the placeholder text for the composer:

We could certainly get much fancier with this (such as reporting the
estimated cost of the conversation), but for now, we are just trying to
achieve feature parity with the TypeScript CLI.
Though arguably this improves upon the TypeScript CLI, as the TypeScript
CLI uses heuristics to estimate the number of tokens used rather than
using the `usage` information directly:
https://github.com/openai/codex/blob/296996d74e345b1b05d8c3451a06ace21c5ada96/codex-cli/src/utils/approximate-tokens-used.ts#L3-L16
Fixes https://github.com/openai/codex/issues/1242
2025-06-25 23:31:11 -07:00
|
|
|
|
|
|
|
|
fn add_token_usage(current_usage: &TokenUsage, new_usage: &TokenUsage) -> TokenUsage {
|
|
|
|
|
let cached_input_tokens = match (
|
|
|
|
|
current_usage.cached_input_tokens,
|
|
|
|
|
new_usage.cached_input_tokens,
|
|
|
|
|
) {
|
|
|
|
|
(Some(current), Some(new)) => Some(current + new),
|
|
|
|
|
(Some(current), None) => Some(current),
|
|
|
|
|
(None, Some(new)) => Some(new),
|
|
|
|
|
(None, None) => None,
|
|
|
|
|
};
|
|
|
|
|
let reasoning_output_tokens = match (
|
|
|
|
|
current_usage.reasoning_output_tokens,
|
|
|
|
|
new_usage.reasoning_output_tokens,
|
|
|
|
|
) {
|
|
|
|
|
(Some(current), Some(new)) => Some(current + new),
|
|
|
|
|
(Some(current), None) => Some(current),
|
|
|
|
|
(None, Some(new)) => Some(new),
|
|
|
|
|
(None, None) => None,
|
|
|
|
|
};
|
|
|
|
|
TokenUsage {
|
|
|
|
|
input_tokens: current_usage.input_tokens + new_usage.input_tokens,
|
|
|
|
|
cached_input_tokens,
|
|
|
|
|
output_tokens: current_usage.output_tokens + new_usage.output_tokens,
|
|
|
|
|
reasoning_output_tokens,
|
|
|
|
|
total_tokens: current_usage.total_tokens + new_usage.total_tokens,
|
|
|
|
|
}
|
|
|
|
|
}
|
2025-08-07 18:26:47 -07:00
|
|
|
|
|
|
|
|
#[cfg(test)]
|
|
|
|
|
mod chatwidget_helper_tests {
|
|
|
|
|
use super::*;
|
|
|
|
|
use crate::app_event::AppEvent;
|
|
|
|
|
use crate::app_event_sender::AppEventSender;
|
|
|
|
|
use codex_core::config::ConfigOverrides;
|
|
|
|
|
use std::sync::mpsc::channel;
|
|
|
|
|
|
|
|
|
|
fn test_config() -> Config {
|
|
|
|
|
let overrides = ConfigOverrides {
|
|
|
|
|
cwd: std::env::current_dir().ok(),
|
|
|
|
|
..Default::default()
|
|
|
|
|
};
|
|
|
|
|
match Config::load_with_cli_overrides(vec![], overrides) {
|
|
|
|
|
Ok(c) => c,
|
|
|
|
|
Err(e) => panic!("load test config: {e}"),
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
#[tokio::test(flavor = "current_thread")]
|
|
|
|
|
async fn helpers_are_available_and_do_not_panic() {
|
|
|
|
|
let (tx_raw, _rx) = channel::<AppEvent>();
|
|
|
|
|
let tx = AppEventSender::new(tx_raw);
|
|
|
|
|
let cfg = test_config();
|
|
|
|
|
let mut w = ChatWidget::new(cfg, tx, None, Vec::new(), false);
|
|
|
|
|
|
|
|
|
|
// Adjust the live ring capacity (no-op for rendering) and ensure no panic.
|
|
|
|
|
w.test_set_live_max_rows(4);
|
|
|
|
|
}
|
|
|
|
|
}
|