[BUG] Auto-titling renames sessions incorrectly, but the agent cannot rename a session at the user's request

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Environment

• Claude Code via claude.ai/code (Remote Control session), agent running on

Windows Server 2022

• Model: Opus 5 (1M context) wrote this report, this occurrence happen with Fabel. (high)
• Date observed: 2026-08-06

Summary

Session display names are changed automatically by the product (topic-based
auto-titling), and in our case changed incorrectly — but when the user asks
the agent to set the name, no tool in the session exposes session metadata,
so the rename is impossible from within. Either the session name is writable
or it is not; today the product writes it and the user (via the agent) cannot.

Our concrete case

Our shop convention is that session names lead with the issue-tracker number
(5354-schemas-and-logging style) so that a session list sorts and searches
by issue months later. The project CLAUDE.md instructs the agent to maintain
this convention. What happens:

1. The product auto-titles the session from early conversation topic; the

generated name does not carry the issue number, so the convention is
broken by the tool itself.

1. The user asks the agent to rename the session correctly. The agent has no

tool for session metadata (verified: nothing in the session toolset, task
tools, or cron tools touches the display name; a subagent reached the
same conclusion independently).

1. The only fix is a manual rename in the claude.ai/code session-list UI —

which the auto-titler may later have overwritten again (see #84041,
"titles go stale after a mid-session pivot").

What Should Happen?

Expected

Any one of these would resolve the contradiction:

• A tool/capability by which the agent can set the session title on user

request (the natural fix — #84041 hints a set_session_title exists in
some surface but refuses the current session);

• Auto-titling honors a configurable naming convention (exactly #83455), so

the generated name is at least correct;

• Auto-titling defers to any manually-set or agent-set name instead of

overwriting it.

Error Messages/Logs

# Session-rename evidence excerpt

Curated from a real Claude Code session, 2026-08-06. Internal project
content (source, business notes, colleague names, customer data references)
is deliberately left out — only the rename-relevant exchanges are here.

- Claude Code CLI **2.1.223** (confirmed equal to npm `@anthropic-ai/claude-code` latest at the time)
- Model: Opus 5 (`claude-opus-5[1m]`), 1M context
- Surface: claude.ai/code **Remote Control** session; agent host is Windows Server 2022
- Session UUID: `ff48a724-58d5-4fd2-b7c0-5e394394bc38`

## Setup: a house naming convention encoded in CLAUDE.md

The project's `CLAUDE.md` mandates that a session name lead with the
issue-tracker number, e.g. `5354-schemas-and-logging`, because a session list
is later searched and sorted by issue number. It also states that a session's
`-n` name is fixed at launch, so if the name arrives without the number the
agent should say so once and use the numbered form in everything it writes.

The correct name for this session was `5354-schemas-and-logging`.

## What happened

1. The product's own auto-titling set/changed the session display name, and
   the resulting name did not follow the convention — i.e. the tool renames
   the session, incorrectly, without being asked.

2. The user asked the agent to fix it:

   > "Can you rename your self correctly please ."

3. The agent could not. No tool available in the session exposes session
   metadata or a title setter. This was checked directly and independently
   confirmed by a subagent spawned for the purpose, which reported:

   > "I can't do that from here — no tool in this session exposes the
   > claude.ai session name; it's fixed at launch and none of the available
   > tools (task, cron, messaging) touch session metadata. Renaming it to
   > `5354-schemas-and-logging` has to happen in the claude.ai UI itself."

4. The user's objection, which is the actual bug report:

   > "Claude code changes the name in the web UI incorrectly but will not
   > change it at my request this is wrong either you can change the name or
   > you can't."

## The defect, stated plainly

The capability is asymmetric. The product writes the session display name
automatically, but the user — acting through the agent, which is the only
interface a Remote Control session offers — cannot write it. A convention
the user encoded in `CLAUDE.md` is therefore broken by the tool and cannot be
repaired from within the session; the only remedy is a manual rename in the
claude.ai session-list UI, which auto-titling may later overwrite again.

## Side note: `!` prefix under Remote Control

While working around this, two in-session escapes proved unavailable over
Remote Control, which is worth a look independently:

- `/hooks` returned "isn't available over Remote Control".
- A `!`-prefixed shell command (`! gh auth login ...`) did not execute; it
  was passed through as plain text, with no output and no error. Verified
  afterward that the command had not run (`gh auth status` reported no
  login). A silent no-op is the wrong failure mode — `/hooks` at least says
  it is unavailable.

## Existing issues this relates to

- #84041 — session titles go stale after a mid-session pivot;
  `set_session_title` refuses to rename the current session from within (open)
- #75733 — expose a "rename session" tool to the agent (open)
- #72404 — expose a tool/hook to set the current session title (open, dup)
- #61479 — allow Claude to rename the current session programmatically (closed, dup)
- #51791 — allow renaming session titles after creation (closed, not planned)
- #55951 — desktop sidebar ignores `UserPromptSubmit` hook `sessionTitle` output (open)
- #83455 — configurable naming convention for auto-generated session names (open)

The prior reports ask for the *feature*. The point here is narrower and is a
defect rather than a wish: whatever the product's policy on programmatic
renaming, it should not be one-way. If the agent may not set the title, the
auto-titler should not overwrite a name the user is relying on.

Steps to Reproduce

Run a claude code session with a good default name, slightly change the topic, Claude code will change the name in the web Ui, with out obeying the rules, You ask Claude code to rename conversation at it refuses.

Claude Model

Other

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

Claude Code CLI: 2.1.223,

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

Related existing issues

• #84041 — Session titles go stale after a mid-session pivot;

set_session_title refuses to rename the current session from within

• #83455 — [FEATURE] Configurable naming convention for auto-generated

session names

This report is the intersection of the two: the asymmetry (product may
rename, user's agent may not) is the bug, independent of which fix lands.

Most of this text is generated but Claude-ai but I have confirmed the detail as entering it.

This is bug behavior and closing it and its duplicates reflects poorly on the quality of the product Anthropic is producing. this is a major code smell about want is going on. Unless there is some use case that name the user expects for chat should never be used. I understand it might be hard fix, but at some point it should be done.