CLI Execution Flow & Failure Modes
Anatomy of run.rs pipeline: prompt intake, persistence, auth resolution, & history replay
PIPELINE EXECUTION BUS args session persist config authed payload stream TRAP DOOR 1: EARLY PERSISTENCE Message is written to storage BEFORE provider resolves. If auth or discovery fails downstream, orphan user prompts remain permanently stored in session state history. TRAP DOOR 2: UNBOUNDED REPLAY Full stored history replayed with zero windowing/trimming. Long sessions trigger context limit crashes, severe latency, and exponential API token overhead costs. 01 PROMPT RECV run.rs entry point CLI flags parsed 02 SESSION SELECT explicit | continue or create new session 03 PERSIST MSG write to DB early ⚡ TRAP DOOR 1 04 PROVIDER DISCOV storage ➔ env initialize provider 05 AUTH CHECK validate credentials inline login fallback 06 HISTORY REPLAY send every stored msg ⚡ TRAP DOOR 2 07 MODEL CALL temp: 0.7 max_tokens: 4096 08 OUTPUT SPLIT stdout: answer stderr: metadata STDOUT User Answer STDERR Telemetry/Meta
STAGE 01 PROMPT RECEIVED
Hover or click any stage box to inspect internal execution logic and potential failure modes.