claude-code - 💡(How to fix) Fix [BUG] /rename replaces the ultracode effort indicator with the session name (effort level stays active)

Preflight: On the latest version (2.1.158). Searched existing issues — no duplicate. The same effort-indicator element appears in #56836 / #54641, and a different effort/statusline bug in #63468, but none report /rename hiding the indicator. Single bug. Before/after screenshots available (happy to drag-drop them into this issue).

After selecting the ultracode effort level with /effort ultracode, the input box shows a colored "ultracode" effort indicator at the right end of its top border. Running /rename to give the session a custom name replaces that effort indicator with the session name in the same slot — so the effort level is no longer visible anywhere, even though it is still active.

Terminology: per the CLI's own confirmation message, ultracode is an effort level — "Set effort level to ultracode (this session only): xhigh + dynamic workflow orchestration." I describe the indicator by what's visible (a colored ultracode label at the right end of the input-box border); exact styling/color may be terminal-dependent.

What's Wrong?

The right end of the input-box border is a single slot shared between the effort-level indicator and the custom session-name label, and the name wins:

• Before rename (no custom name): the slot shows the colored ultracode effort indicator. (screenshot 1)
• After /rename <name>: the slot shows the session name instead. The ultracode effort indicator disappears and is shown nowhere else. (screenshot 2)

This is a display-only bug — the effort level itself is not reset. Immediately after the rename, the thinking footer still reads "still thinking with xhigh effort," confirming ultracode is still active; only its on-screen indicator is gone.

What Should Happen?

Renaming a session and showing its effort level are orthogonal concerns. A user should be able to both give a session a memorable name and still see its effort level at a glance. /rename should not hide the ultracode indicator — the effort badge and the custom name should coexist (e.g., name on one side, effort badge on the other), rather than the name evicting the badge.

Real use case (reporter): "I rename my sessions so I can find them because I have many, but I also want to see whether a session is at ultracode effort or not." Today, the moment you rename, you lose that signal.

Steps to Reproduce

1. Start a Claude Code session and run /effort ultracode.
2. Observe the colored ultracode indicator at the right end of the input-box border. (screenshot 1)
3. Run /rename my-session-name.
4. Observe the right-border slot now shows my-session-name; the ultracode indicator is gone. (screenshot 2)
5. Confirm the effort level is unchanged — the footer still reads "still thinking with xhigh effort."

Expected: after step 3 the ultracode indicator stays visible alongside the new name. Actual: the name replaces the indicator; effort level remains active but is no longer surfaced.

Proposed Change

• Give the effort-level indicator its own persistent position so it coexists with the custom session-name label instead of sharing one slot — e.g., render the session name and the effort badge as two separate segments (opposite ends of the border, or distinct chips).
• At minimum, never let /rename remove the effort indicator: after a rename, keep rendering the effort badge derived from the active per-session effort state.
• Regression test: enable ultracode → /rename → assert the effort indicator is still rendered and the effort level is still ultracode. Assert against the status/border model state (not raw ANSI/pixel output) so the test is robust across terminals.

Related Issues

• #63468 — Statusline effort.level reports "xhigh" instead of "ultra" for ultracode — same effort/statusline surface, different bug (the value reported to statusline scripts, not the indicator vanishing on /rename).
• #56836 / #54641 — requests about this same right-side effort indicator element (hide toggle / surface it in the input toolbar); they confirm the element this bug concerns.
• #59562, #62450, #63765, #30377 — other reports that /rename has unintended side effects (session reload, title persistence, history loss). Possibly an adjacent pattern; this report is specifically about the shared-slot display behavior.

Environment