Preflight Checklist
What's Wrong?
Title: Conversation titles inconsistent between Claude for Windows and VS Code extension
Description:
The same conversation displays with different titles in Claude for Windows vs. the Claude Code VS Code extension, making it hard to identify chats across the two apps.
Behavior:
VS Code extension shows the raw first user message as the title (e.g., "i've been trying to figure out...")
Claude for Windows shows an AI-generated summary title (e.g., "Fix Claude app chat sync...")
Both apps are reading the same .jsonl file from ~/.claude/projects/, but each generates/displays the title independently.
Expected behavior:
The generated summary title should be written back to the .jsonl file so both apps read from the same source and display the same name.
Environment:
Claude for Windows v1.1.4498
VS Code with Claude Code extension: Claude Code VS Code extension v2.1.63
Windows 10
Here is the chat in vscode:
same chat in win10 desktop app:
What Should Happen?
When either app generates a summary title for a conversation, it should be saved back to the shared .jsonl file so both Claude for Windows and the VS Code extension display the same title for the same session.
Error Messages/Logs
Steps to Reproduce
Steps to reproduce:
Open Claude for Windows with a working directory set (e.g. C:\Users...\OneDrive\CLaude Cowork)
Start a new conversation in the VS Code Claude Code extension with the same working directory open as the workspace
Send a few messages
Check the conversation title in the VS Code extension sidebar — it shows the beginning of your first message
Check the same conversation in Claude for Windows sidebar — it shows an AI-generated summary title
The two titles do not match, making it difficult to identify the same session across both apps
Claude Model
Sonnet (default)
Is this a regression?
I don't know
Last Working Version
No response
Claude Code Version
2.1.47
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
VS Code integrated terminal
Additional Information
No response
Preflight Checklist
What's Wrong?
Title: Conversation titles inconsistent between Claude for Windows and VS Code extension
Description:
The same conversation displays with different titles in Claude for Windows vs. the Claude Code VS Code extension, making it hard to identify chats across the two apps.
Behavior:
VS Code extension shows the raw first user message as the title (e.g., "i've been trying to figure out...")
Claude for Windows shows an AI-generated summary title (e.g., "Fix Claude app chat sync...")
Both apps are reading the same .jsonl file from ~/.claude/projects/, but each generates/displays the title independently.
Expected behavior:
The generated summary title should be written back to the .jsonl file so both apps read from the same source and display the same name.
Environment:
Claude for Windows v1.1.4498
VS Code with Claude Code extension: Claude Code VS Code extension v2.1.63
Windows 10
Here is the chat in vscode:
same chat in win10 desktop app:
What Should Happen?
When either app generates a summary title for a conversation, it should be saved back to the shared .jsonl file so both Claude for Windows and the VS Code extension display the same title for the same session.
Error Messages/Logs
Steps to Reproduce
Steps to reproduce:
Open Claude for Windows with a working directory set (e.g. C:\Users...\OneDrive\CLaude Cowork)
Start a new conversation in the VS Code Claude Code extension with the same working directory open as the workspace
Send a few messages
Check the conversation title in the VS Code extension sidebar — it shows the beginning of your first message
Check the same conversation in Claude for Windows sidebar — it shows an AI-generated summary title
The two titles do not match, making it difficult to identify the same session across both apps
Claude Model
Sonnet (default)
Is this a regression?
I don't know
Last Working Version
No response
Claude Code Version
2.1.47
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
VS Code integrated terminal
Additional Information
No response