From 5cb39265bfd133927a22e4501e12a89dd1d2d5f5 Mon Sep 17 00:00:00 2001 From: Simon Klee Date: Sat, 7 Nov 2026 00:32:36 +0100 Subject: [PATCH] docs(cli-rs): note the console toggle in the G02 deviation --- packages/cli-rs/parity/deviations/G02-print-logs-tui.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/packages/cli-rs/parity/deviations/G02-print-logs-tui.md b/packages/cli-rs/parity/deviations/G02-print-logs-tui.md index 6cf207761b9..f92d8e7f552 100644 --- a/packages/cli-rs/parity/deviations/G02-print-logs-tui.md +++ b/packages/cli-rs/parity/deviations/G02-print-logs-tui.md @@ -8,7 +8,8 @@ and none after it. They stay on the screen until the next redraw of those cells Rust: `opencode_tui::run` sets `AppOptions::capture_stderr`. While the TUI runs, whatever the process writes to stderr (log records, stray `eprintln!`) goes to the opentui console, and is written to the real stderr after -the terminal is restored. The same PTY run, with a record written to the process's stderr during the TUI, shows +the terminal is restored. "Toggle console" in the palette (`app.console`, unbound by default, as in TS) shows +the console while the TUI runs. The same PTY run, with a record written to the process's stderr during the TUI, shows no record on the screen and the record after the alternate screen is left: ```