Root Cause of Claude Code VS Code Extension Session Title Corruption Identified
Session Title Corruption Bug in Claude Code Extension
A persistent bug in the Claude Code VS Code extension causes session titles in Past Conversations to become corrupted—showing wrong titles, reverting to last-prompt text, or disappearing entirely. A developer has identified the architectural root cause and collected 20+ related GitHub issues that all stem from the same underlying problem.
Root Cause Analysis
The extension's session list reads titles by performing a raw string search for "customTitle" in the last 64KB of each .jsonl session file. This approach creates three specific failure modes:
- 64KB eviction — In long sessions (common with agentic workflows), the custom-title entry gets pushed outside the 64KB tail window, causing the title to be lost.
- Cross-session content contamination — The scanner doesn't distinguish between real custom-title JSONL entries and the string "customTitle" appearing inside tool results or conversation content, causing one session's title to appear on a completely different session.
- Overwrite on resume — When a session is resumed and new content is appended, any custom-title from /rename gets buried. The extension then falls back to lastPrompt or picks up a stale match from tool output.
Affected Issues
The developer has collected 20+ GitHub issues related to this problem:
- Title lost: #33165, #32150, #25090, #23610, #26240, #29194
- Wrong title: #29801, #9668, #29342, #27751
- Sessions invisible: #9898, #31813, #29088, #22215, #18619, #11232
- Feature requests (workarounds): #11956, #9198, #11694, #7441
Many of these issues were auto-closed as duplicates by the bot without a fix landing. Partial fixes in v2.1.47 and v2.1.71 addressed specific symptoms but not the underlying architecture.
Proposed Solution and Workaround
The developer proposes storing titles in a separate lightweight index (e.g., title-registry.json) rather than scanning conversation content. This approach would survive session growth, be immune to content contamination, and enable cross-client sync.
For a current workaround, the developer has been running a UserPromptSubmit hook + systemd timer + persistent title registry that re-asserts the correct title on every prompt and every 2 minutes. Implementation details are available in issue #32150.
This bug affects anyone using Claude Code for task-based workflows where matching sessions to work items matters. The full root cause analysis with all 20 issues linked is available in the GitHub discussion.
📖 Read the full source: r/ClaudeAI
👀 See Also
Bodega Inference Engine: Optimizing LLM Inference for Apple Silicon's Unified Memory
Bodega is an inference engine built specifically for Apple Silicon's unified memory architecture, addressing throughput limitations by redesigning continuous batching and KV cache management for MLX. The developer reports working on it for 2.5 years with optimizations close to the Metal layer.
Stagent: Open-source ops layer for Claude Agent SDK with local governance and workflow orchestration
Stagent is an open-source, local-first coordination workspace built on top of Claude Agent SDK and Claude API that provides workflow orchestration, budget guardrails, and human-in-the-loop governance for AI agents. It includes 15 product surfaces, 6 workflow patterns, 52+ reusable agent profiles, and runs entirely locally with SQLite.
Cowork Chrome Extension Automates Personal Data Removal from Data Brokers
A Reddit user reports that using the Cowork Chrome extension with a Gmail connection automated filling forms, writing emails, and verifying removal requests to delete personal data from major data providers in just a few hours.
FOMOE Enables 397B Qwen3.5 Model Inference on $2,100 Desktop Hardware
FOMOE (Fast Opportunistic Mixture of Experts) allows running Qwen3.5's 397 billion parameter flagship model at 5-9 tokens/second on consumer hardware using two $500 GPUs, 32GB RAM, and an NVMe drive with Q4_K_M quantization.