[Bug] Incorrect Session Summaries with Cross-Contaminated Metadata

Bug Description

Bug Report + Feature Request: Session Summarization Issues & Custom Session Naming

Bug Report: Incorrect Auto-Generated Session Summaries

The /resume command shows factually incorrect auto-generated session descriptions that misrepresent the actual work performed.

Critical Bug Examples:

• Multiple sessions showing "Debugging Python Web Scraper with Selenium and BeautifulSoup"
• Reality: No Python development has ever been done in this environment - this is a DevOps/Infrastructure project focused on Spring Boot + React + AWS
• Sessions show "Debugging Python Web Scraper with Selenium and Requests", "...with Proxy", etc.
• Actual work: Jenkins pipelines, Kubernetes, Terraform, SonarQube integration, authentication systems

Additional Summarization Issues:

• Generic descriptions like "testing status", "bootstrap", "This session is being continued from a previo..."
• Truncated summaries that provide no useful context
• No correlation between summary content and actual conversation topics

Impact of Bug

This bug has serious implications for:

1. Session Management: Cannot identify or resume relevant work sessions
2. Project Tracking: Misleading summaries make it impossible to track actual progress
3. Professional Use: Incorrect summaries undermine confidence in Claude Code for enterprise work
4. Data Integrity: Session metadata becomes unreliable for any workflow automation

Root Cause Analysis

The auto-summarization appears to be:

• Cross-contaminating between different users' sessions or projects
• Using incorrect context or training data for summary generation
• Not properly analyzing the actual conversation content
• Possibly using cached or stale summary templates

Immediate Fix Needed

1. Fix the summarization algorithm to accurately reflect conversation content
2. Audit existing summaries - many may be incorrectly categorized
3. Prevent cross-contamination between different projects/users

Long-term Solution: Custom Session Naming

While fixing the bug is critical, also add the ability to name/label Claude Code sessions with custom, user-defined descriptions to prevent future issues.

Implementation Options:

Option 1: Session Start Command

claude --session-name "Spring Boot RDS IAM Integration"
# or
claude /name "Spring Boot RDS IAM Integration"

Option 2: In-Session Naming

/session-name "Cypress E2E Testing Setup"
# or
/name "SonarQube Quality Gates Implementation"

Option 3: Session Marker Integration
Leverage the existing pattern some users already use:

/session-marker "authentication-breakthrough-20250824"

Benefits

1. Improved Productivity: Quickly identify and resume specific work contexts
2. Better Organization: Group related sessions by project, feature, or bug
3. Enhanced Collaboration: Share meaningful session references with team members
4. Project Management: Track progress across multiple focused sessions

User Experience

Current Experience:

1. 23s ago     13m ago    139 -    testing status
2. 13m ago     16m ago     17 -    testing status line
3. 16m ago     21m ago     16 -    Statusline Setup: Minimal Git Branch Display
4. 37m ago     8h ago     216 -    This session is being continued from a previo...

Proposed Experience:

1. 23s ago     13m ago    139 -    [MYPROJECT] Status Line Implementation
2. 13m ago     16m ago     17 -    [MYPROJECT] Status Line Git Integration
3. 16m ago     21m ago     16 -    [MYPROJECT] Statusline Setup: Git Branch Display
4. 37m ago     8h ago     216 -    [MYPROJECT] Spring Boot Authentication Integration

Technical Implementation Notes

• Session metadata is stored in JSONL files at ~/.claude/projects/*/[uuid].jsonl
• Each entry has a summary field that could be user-controllable
• Custom names should fallback to auto-generation if not provided
• Consider validation (length limits, character restrictions)

Use Cases

1. Multi-project work: [ProjectA] Feature Implementation, [ProjectB] Bug Investigation
2. Feature development: Authentication System - Phase 1, Authentication System - Testing
3. Bug tracking: BUG-123: Pipeline Failure Investigation, BUG-123: Fix Implementation
4. Learning sessions: Learning Kubernetes, Docker Exploration
5. Team collaboration: Code Review: PR-456, Pair Programming: Payment System

Priority Justification

This feature would significantly improve the developer experience for users who work on multiple projects or complex features across many sessions. The current auto-generated descriptions often provide little context for session identification and resumption.

Summary

This bug significantly impacts the usability of Claude Code for professional development work. The combination of fixing the summarization algorithm and adding user-controlled session naming would restore confidence in session management and enable proper project workflow organization.

Environment Info

• Platform: darwin
• Terminal: vscode
• Version: 1.0.89
• Feedback ID: 7dea5776-4586-408a-9fd3-6dea2a59093a

Errors

Note: Error logs were truncated.