Use session wording in /rename confirmation (#25035)

## Why

The TUI `/rename` confirmation should use the term "session" for
consistency.
This commit is contained in:
Eric Traut
2026-05-29 11:09:40 -07:00
committed by GitHub
parent 36cd36626d
commit 62039e8d35
2 changed files with 3 additions and 3 deletions

View File

@@ -1527,11 +1527,11 @@ impl ChatWidget {
fn rename_confirmation_cell(name: &str, thread_id: Option<ThreadId>) -> 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()])
}

View File

@@ -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)