From 62039e8d356a3e983c5a4af82e09458810fc3355 Mon Sep 17 00:00:00 2001 From: Eric Traut Date: Fri, 29 May 2026 11:09:40 -0700 Subject: [PATCH] Use session wording in `/rename` confirmation (#25035) ## Why The TUI `/rename` confirmation should use the term "session" for consistency. --- codex-rs/tui/src/chatwidget.rs | 4 ++-- ...ui__chatwidget__tests__thread_name_update_resume_hint.snap | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/codex-rs/tui/src/chatwidget.rs b/codex-rs/tui/src/chatwidget.rs index 32c68529d5..8604229552 100644 --- a/codex-rs/tui/src/chatwidget.rs +++ b/codex-rs/tui/src/chatwidget.rs @@ -1527,11 +1527,11 @@ impl ChatWidget { fn rename_confirmation_cell(name: &str, thread_id: Option) -> PlainHistoryCell { let mut line = vec![ "• ".into(), - "Thread renamed to ".into(), + "Session renamed to ".into(), name.to_string().cyan(), ]; if let Some(hint) = resume_hint(Some(name), thread_id) { - line.extend([". To resume this thread run ".into(), hint.cyan()]); + line.extend([". To resume this session run ".into(), hint.cyan()]); } PlainHistoryCell::new(vec![line.into()]) } diff --git a/codex-rs/tui/src/chatwidget/snapshots/codex_tui__chatwidget__tests__thread_name_update_resume_hint.snap b/codex-rs/tui/src/chatwidget/snapshots/codex_tui__chatwidget__tests__thread_name_update_resume_hint.snap index b3cdf89da3..f6f827fe53 100644 --- a/codex-rs/tui/src/chatwidget/snapshots/codex_tui__chatwidget__tests__thread_name_update_resume_hint.snap +++ b/codex-rs/tui/src/chatwidget/snapshots/codex_tui__chatwidget__tests__thread_name_update_resume_hint.snap @@ -2,4 +2,4 @@ source: tui/src/chatwidget/tests/app_server.rs expression: rendered --- -• Thread renamed to review-fix. To resume this thread run codex resume, then select review-fix (123e4567-e89b-12d3-a456-426614174000) +• Session renamed to review-fix. To resume this session run codex resume, then select review-fix (123e4567-e89b-12d3-a456-426614174000)