Renamed session titles don't persist + first user prompt ignored + panels reflow on new content

Resolved 💬 5 comments Opened May 29, 2026 by RainerNissler Closed Jul 9, 2026

Environment

  • Claude Code VS Code native extension
  • Windows 11 Enterprise (10.0.26200)
  • Model: Opus 4.7 (1M context)
  • Multiple long-running sessions (20+ titles in sidebar)

Bug 1 — Renames are not persisted

Renaming a session in the sidebar appears to work briefly, but the
custom name disappears on the next refresh / reload / new message.

Verified on disk: searching every session file under
~/.claude/projects/<project>/*.jsonl for any of
"title", "name", "customName", "userTitle", "displayName",
"summary" returns zero matches for a user-supplied name. The
only "name": fields present are tool names (Bash, Read, Edit...).

So the rename has nowhere to land — there's no persistence field for
it. Looks like either the rename UI is purely cosmetic in-memory state,
or it writes somewhere that's overwritten on every refresh.

Bug 2 — First user prompt is ignored, AI-generated summary used instead

When opening a new session I type my first request — that text would
be the obvious, stable, predictable title. Instead the sidebar shows
some AI-generated paraphrase ("introvertiert" was the user's word).
It changes as the conversation evolves, so the same session has a
different title every time I come back.

Expected behaviour

  • Default title = the first user message (truncated to ~60 chars). It

doesn't change as the conversation grows.

  • User rename is sticky — once I set a custom title, it is

persisted in the session file (e.g. a new userTitle field at the
top of the jsonl, or in sessions/<pid>.json) and never
overwritten by the auto-summarizer.

  • Rename UI: double-click the title in the sidebar → editable inline.

Impact

With 20+ active sessions per project, current behaviour makes it
impossible to find a specific past conversation — every title shifts
under me, and the one fix (rename) doesn't stick. Multi-session work
becomes unusable.

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗