[Lstarsky0]

What and why

Pressing r in /sessions shows the rename prompt twice. The header row turns into the input (New title: …_), and the key handler also sets the status row under it to the same New title: string. At 60×24, before:

   New title: A much longer session title that will ... █
   New title:                                           █
   1. 4bf1eef0 | show default please | 2 msgs | curr... │

After:

   New title: A much longer session title that will n...
   1. 190a6040 | show default please | 2 msgs | curre...

Entering rename mode now clears the status instead. The header still carries the prompt, and the status row still shows Title must be 1–100 characters for an empty title and Renamed to "…" afterwards. Search keeps its own status line, since Search: type, Enter to apply says something the /… header doesn't.

Issue

No-Issue: the /sessions rename prompt is shown twice; I searched and found no issue for it

How I tested it

• Ran a debug build in a pseudo-terminal with an empty HOME against a local OpenAI-compatible mock, sent one message so a session exists, then /sessions, r, typed a title and pressed Enter, with this change and with a build of main from before it. The prompt rows above are from 60×24; the Renamed to receipt is the same in both. Pressing Enter on an empty title still shows the length error.
• cargo check -p codewhale-tui --all-targets and cargo +1.89.0 check -p codewhale-tui: clean. Merged onto current main (48fad09), cargo fmt --all -- --check and CI's clippy for codewhale-tui are clean too.
• cargo nextest run -p codewhale-tui --lib on that merge: 15361 passed, 1 failed, with the session_picker tests among the passes. The failure is computer_use_autonomous_postures_block_before_the_plugin, which fails on main without this change as well.

Checklist

• One focused change, on 3cb4cd2; it merges cleanly into current main
• cargo fmt --all passes, and tests cover new or changed behavior
• If this adds or changes a user-facing feature, I updated its docs and its row in docs/features.toml (cargo test -p codewhale-tui --test feature_registry checks it) — n/a

[claude]

Claude Code Review

This pull request is from a fork — automated review is disabled. A repository maintainer can comment @claude review to run a one-time review.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-22T22:52:14.096758Z	f36ca36	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[Hmbown]

Thanks @Lstarsky0 for finding the duplicated rename prompt and reducing it to the status line that repeated the header. Your PR is merged as 57e726bf3c, with your authorship and source branch preserved. I verified the exact patch in the fresh CLI at 60×24 and 140×40: one prompt, empty-title validation, and saved-title confirmation all behaved correctly; 37 existing session-picker tests passed. The unrelated Computer Use fixture failure you reported is corrected separately: Ask and Full Access both require the real human card, forged decisions remain rejected, and all 19 focused checks passed. This is in the 0.10.2 candidate; it is not published yet.