Struct PtyExecutor 

pub struct PtyExecutor { /* private fields */ }

Executor for running prompts in a pseudo-terminal.

Implementations

impl PtyExecutor

pub fn new(backend: CliBackend, config: PtyConfig) -> Self

Creates a new PTY executor with the given backend and configuration.

pub fn handle(&mut self) -> PtyHandle

Returns a handle for TUI integration.

Can only be called once - panics if called multiple times.

pub async fn run_observe( &self, prompt: &str, interrupt_rx: Receiver<bool>, ) -> Result<PtyExecutionResult>

Runs in observe mode (output-only, no input forwarding).

This is an async function that listens for interrupt signals via the shared interrupt_rx watch channel from the event loop. Uses a separate thread for blocking PTY reads and tokio::select! for signal handling.

Returns when the process exits, idle timeout triggers, or interrupt is received.

Arguments

• prompt - The prompt to execute
• interrupt_rx - Watch channel receiver for interrupt signals from the event loop

Errors

Returns an error if PTY allocation fails, the command cannot be spawned, or an I/O error occurs during output handling.

pub async fn run_observe_streaming<H: StreamHandler>( &self, prompt: &str, interrupt_rx: Receiver<bool>, handler: &mut H, ) -> Result<PtyExecutionResult>

Runs in observe mode with streaming event handling for JSON output.

When the backend’s output format is StreamJson, this method parses NDJSON lines and dispatches events to the provided handler for real-time display. For Text format, behaves identically to run_observe.

Arguments

• prompt - The prompt to execute
• interrupt_rx - Watch channel receiver for interrupt signals
• handler - Handler to receive streaming events

Errors

Returns an error if PTY allocation fails, the command cannot be spawned, or an I/O error occurs during output handling.

pub async fn run_interactive( &mut self, prompt: &str, interrupt_rx: Receiver<bool>, ) -> Result<PtyExecutionResult>

Runs in interactive mode (bidirectional I/O).

Uses tokio::select! for non-blocking I/O multiplexing between:

1. PTY output (from blocking reader via channel)
2. User input (from stdin thread via channel)
3. Interrupt signal from event loop
4. Idle timeout

This design ensures Ctrl+C is always responsive, even when the PTY has no output (e.g., during long-running tool calls).

Arguments

• prompt - The prompt to execute
• interrupt_rx - Watch channel receiver for interrupt signals from the event loop

Errors

Returns an error if PTY allocation fails, the command cannot be spawned, or an I/O error occurs during bidirectional communication.