Conversation history titles should be descriptive summaries of the conversation

Status Fixed / completed

Maintainer reply None cached

Activity 4 comments · opened Mar 18, 2026 · closed Apr 10, 2026

Problem

Conversation titles in the session history are not meaningful. They appear to pull from recent messages (e.g., "yes please", "push directly", "Untitled") rather than summarizing what the conversation was actually about. This makes it very difficult to find past conversations.

Additionally, the search box only searches session titles, not session content, so unhelpful titles make the problem worse.

Requested Improvement

Auto-generate conversation titles that summarize the topic/purpose of the conversation (e.g., "Add role-based testing to knowledge base suite" instead of "yes please")
Ideally, use an AI-generated summary as the title
Bonus: allow searching session content, not just titles

Why This Matters

Power users who have many sessions need to be able to find past conversations quickly. Without descriptive titles or content search, the conversation history becomes effectively unusable.

View original on GitHub ↗

4 Comments

yurukusa · 5 months ago

Workaround: auto-generate descriptive titles with a Stop hook

SESSION_ID="${CLAUDE_SESSION_ID:-}"
[ -z "$SESSION_ID" ] && exit 0
SESSION_FILE=$(find ~/.claude/projects -name "${SESSION_ID}.jsonl" 2>/dev/null | head -1)
[ -z "$SESSION_FILE" ] && exit 0
FIRST_MSG=$(jq -r 'select(.message.role == "user") | .message.content' "$SESSION_FILE" | head -1 | head -c 100)
if [ -n "$FIRST_MSG" ]; then
  echo "📝 Session topic: $FIRST_MSG" >&2
fi
exit 0

You can rename sessions at any time:

/rename add-auth-middleware

This makes them searchable later with /resume.

JimTaft · 4 months ago

You can also use /rename to rename your conversation in Claude Code. You just type "/rename Meaningful Title - Short Description", and this is how it will show up in /resume.

martine-balcaen · 4 months ago

my problem has been solved. thank you

github-actions[bot] · 4 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.